RELAYDESK WEB RELEASE
Web 2.2.1 – Unified Person Threads
RelayDesk now combines communication around the person instead of making the provider the primary unit of work.
What changed
- Threads is the default feed mode.
- Messages from the same person can collapse into one RelayDesk thread even when they arrive through different providers.
- Provider names remain visible inside the combined thread so RelayDesk never hides where communication came from.
- Events mode exposes every individual message when troubleshooting or reviewing chronology.
- Unified Threads reuse the existing People view and selected-conversation history.
- WhatsApp Bridge Mode and the low-memory native-tab policy from 2.2.0 remain active.
- Visible build marker is WEB 2.2.1 / RD1-221 – UNIFIED PERSON THREADS.
Architecture
Provider events -> RelayDesk normalization -> person/thread correlation -> Combined Feed -> Attention Workflow -> Unified Thread workspace. Matrix remains a replaceable transport and direct provider APIs can coexist beside it.
Truth boundary
Person correlation in this developer preview is based on the information RelayDesk currently has in the normalized feed. Production identity resolution will need stronger account/contact correlation rules so two people with the same display name are never merged incorrectly.
