RelayDesk Web 2.3.4 — Reply Router
The unified feed now exposes the routing identity needed to keep replies on the same provider, account and conversation instead of silently crossing channels.
What changed
- Added a canonical reply-routing panel to selected conversations.
- Preserves provider, account identity, conversation identity and a normalized thread key.
- Providers without a tested send adapter are explicitly marked Safe Draft; RelayDesk will not silently fall back to another channel.
- Matrix preview/test routes can preserve routing identity, while production external sending still requires a configured adapter and explicit user action.
- Mobile conversation view uses the same routing contract and remains touch-friendly.
- Portable workspace backup now identifies itself as RelayDesk Web 2.3.4.
Connector truth
Gmail, IMAP, Outlook, Teams, Slack, Telegram and production WhatsApp reply adapters are not claimed as live in this release. Their normalized route identities are preparation for real adapters; sending remains blocked or draft-only until each adapter is implemented and tested.
Mobile status
Android and iOS remain mobile-web/PWA-direction work in this release. No native Android APK/AAB or iOS IPA build is claimed yet. Windows and Vercel were not touched.
2.3.5 follow-up — Identity Guard
Web 2.3.5 tightens the Reply Router boundary: unsupported provider send attempts are actively intercepted and preserved as local drafts with provider/account/conversation identity and a route-not-live reason. Portable Workspace also adds a local Normalize & deduplicate imports control that fingerprints provider, account, conversation, sender, message body and minute-level time while keeping source provenance intact. The guard and deduplication controls are mobile-safe. No real external message was sent during validation.
Active paths
Open RelayDesk Web App · Updates & rollback · Documentation library