RELAYDESK WEB RELEASE
Web 2.1.6 – Unified Threads
This release turns the person-centric layer into a readable chronological thread across available RelayDesk sources while keeping every provider visible.
What changed
- Selected conversations now show a chronological Unified Thread instead of only one isolated card.
- The same current-preview identity can show Outlook and Teams events in one history.
- Every event keeps provider provenance, timestamp and subject/context.
- RelayDesk Test Lab uses stable peer IDs and remains writable for local replies.
- Mobile uses the same thread inside the full-screen conversation drawer.
- Visible app marker updated to WEB 2.1.6 / RD1-216 – UNIFIED THREADS.
Architecture
Provider/Test streams -> normalization -> Combined Feed -> person identity key -> Unified Thread -> Attention Workflow -> RelayDesk client.
Truth boundary
The developer preview still uses deterministic Test Lab IDs and simple demo sender names. Production identity resolution must use provider identifiers, user-controlled contact linking and the ability to split an incorrect merge. RelayDesk must never silently merge unrelated people because their display names happen to match.
