One inbox. Exact origin. Safe reconciliation.
Unified feed first. Every event keeps provider, account, thread and source identity; duplicate ingestion collapses deterministically; unread state is provider-authoritative only after authenticated sync; contact merges require strong identifiers; attachment bodies stay quarantined until their provider path is validated; and reply drafts remain local unless the exact originating route has fresh authorization and health evidence.
Provider + account + thread + sourceDeterministic dedupe
Same origin never becomes two messagesState authority
Unread changes require authenticated syncIdentity safety
Merge only on strong identifiersAttachment quarantine
Metadata first; body retrieval stays gatedReply invariant
Never silently switch provider/account
Current truth: this checkpoint defines and exposes the provider contract but does not claim a new live provider. Gmail, Outlook, Slack, Teams, Telegram, WhatsApp Business and SMS remain blocked until secure authorization and provider-specific integration QA pass. No external message is sent by this wave.
Provider + account + thread + sourceFresh evidence
Authorization and health must be currentNo fallback send
Never switch provider or account silentlyHuman review
AI assistance may draft, never auto-send
Current truth: this WordPress checkpoint adds no new live provider. Gmail, Outlook, Slack, Teams, Telegram, WhatsApp Business and SMS remain blocked until their own authorization, secure token handling and integration QA pass. No external message is sent by this wave.
Account, route or health changedPreserve work
Keep the local draft intactRe-check gates
Identity, auth, route and healthResume safely
Only after fresh evidence
Recovery rule: retries never silently switch provider or account. Unknown, stale or failed evidence keeps the response local. This DEV preview still sends no real external messages.
Provider + account matchAuthorization
Usable permission evidenceRoute
Origin channel preservedHealth
Current runtime check
Fail closed: if any gate is unknown, stale or failed, RelayDesk stays in local-draft mode. This DEV preview does not send real external messages.
Local preview · no external send
People, not applications.
RelayDesk groups communication around the person while preserving every provider and account underneath.
Authorize deliberately. Reply only through verified routes.
RelayDesk now separates provider authorization evidence from connection status and send capability. A provider can be configured without being authorized to reply; no real message is sent from this DEV harness.
Evidence before reply-back
Four gates must agree before a production adapter may send: identity, authorization, route ownership and current health.
DEV · NO EXTERNAL SEND
Fail closed: missing or stale evidence keeps the action in local-draft mode.
Connection truth at a glance
Only verified runtime state is shown as connected. Preview and planned adapters stay clearly labelled.
VERIFY BEFORE SEND
Matrix
PLUGGABLE
Use a test Matrix account today. Production credentials will move behind protected server sessions.
Not connected.
WhatsApp Bridge
RECOMMENDED
Keep WhatsApp connected without keeping the full WhatsApp Web interface alive. RelayDesk reads the bridged conversation into the Unified Feed while the native web client stays closed.
Recommended: pair WhatsApp as a linked device through the bridge. No permanent WhatsApp Web tab.
- Connect the Matrix transport.
- Pair WhatsApp with the bridge by QR code or phone pairing code.
- RelayDesk consumes the resulting bridged rooms into the same Unified Feed.
Matrix must be configured before RelayDesk can use a WhatsApp bridge.
Health & resource policy
RD1 CORE
RelayDesk reports connector state without pretending the browser can measure every provider's exact operating-system RAM. This panel shows what the app can verify safely.
Exact per-tab RAM is browser/OS dependent; RelayDesk reports policy, connectivity, last activity and available browser diagnostics.
RelayDesk Test Lab
4 ACCOUNTS
Local test identities can send messages to each other inside this browser.
TEST ONLY · not external email accounts
Microsoft
PLANNED
Outlook and eligible Teams through Microsoft Graph and OAuth.
Slack
PLANNED
Slack Web API beside any reviewed Matrix bridge.
Gmail + IMAP
PLANNED
Gmail API and standard Internet Message Access Protocol behind the same feed contract.
Turn attention into safe action.
Tasks, follow-ups, meetings, contacts and drafts stay together and remain on this device.
Tasks
Follow-ups
Schedule
Contacts
Draft replies
Your communication data stays movable.
Import messages, tune local priority rules, and export a private backup. Connector passwords and access tokens are never included.
DEVICE LOCAL
Add existing communication
Import JSON, CSV or EML email files into the normalized RelayDesk feed. Everything stays in this browser.
No import running.
Keep control of your workspace
Export messages, attention state, tasks, drafts, contacts, events and preferences. Temporary connector tokens are excluded.
Ready.
Surface what matters
Rules are evaluated locally.
What is stored here
This WordPress developer preview uses browser storage. Cross-device account synchronization and production provider authorization are not claimed.
Private assistance, limits and interoperability
These controls are browser-local previews. They do not enable production billing, cloud AI, or provider authorization.
MOBILE-FIRST
Draft locally first
Add an Assist button to open conversations. The preview creates a local draft template and never sends message content to an external AI service.
Local-only by default
External AI blocked.
Plan simulator
No billing is active.
Connector truth
Create action
RelayDesk now treats connector readiness as an explicit fail-closed contract. A reply draft must retain provider, account, thread and source identity; deduplication uses the same immutable origin tuple; unread state becomes provider-authoritative only after authenticated synchronization; contact resolution may merge only on strong identifiers; attachment bodies remain quarantined until their provider retrieval path is validated.
Credential boundary: production OAuth access and refresh tokens must live server-side in protected storage, never localStorage, sessionStorage or page markup. The browser may retain only non-secret connector state such as provider/account labels, readiness state and last successful sync metadata.
Gmail / Outlook readiness: adapters remain disabled for receive and reply until OAuth callback handling, encrypted token storage, refresh/revocation, least-privilege scopes and sandbox accounts pass provider-specific QA. This wave does not claim either provider as connected.
Reply safety: local drafting is allowed; external send remains disabled. No provider API call, remote attachment fetch, external AI transmission or real user message is enabled by this checkpoint.
Mobile: responsive inbox behavior and the existing minimum touch-target policy remain the Android/iOS web baseline. Native binaries are not claimed.