What changed

• Visible build marker is WEB 2.2.2 / RD1-222 – RETURN PATH ROUTER.
• A unified person thread can contain Outlook, Teams, WhatsApp, Matrix and future provider events while each event keeps its original provider/account provenance.
• The selected event now exposes Reply via provider · account as the default return path.
• RelayDesk Test Lab replies continue to work browser-locally.
• Demo/provider items now have a clearly labelled Route Test that records outbound routing intent locally without claiming an external send.
• Web 2.2.2 adds a first Holistic Services Hub: Create Task, Schedule, Save Contact and Summarize intents are captured above the provider layer.
• Unified Person Threads, WhatsApp Bridge Mode and connector telemetry remain active.

Architecture

Provider event -> normalization -> person/thread correlation -> selected event provenance -> Return Path Router -> connector capability check -> same-channel send by default. Service intents sit beside outbound communication and later resolve through replaceable calendar, task, contact, CRM or AI adapters.

Truth boundary

Web 2.2.2 does not claim that demo Outlook, Gmail, WhatsApp, Teams or Matrix sample items are externally writable. Route Test is local simulation unless a real connector with outbound capability is configured. The Services Hub records local service intents only in this preview.

Product direction

Web remains the primary RelayDesk product. iOS and Android are planned as first-class companion clients to the same RelayDesk Core. Windows, macOS and Linux clients stay secondary shells/wrappers around the same account, feed and routing model rather than separate architectures.