Move a conversation between views when its status or assignment changes
When a conversation's status or responsible party changes, it relocates across the Inbox's fixed views — for every connected user in scope — without anyone needing to refresh.
When this happens: A conversation's status changes, or its responsible party changes (assignment, transfer, pick-up, or AI handover).
How it works
- Changes a conversation's status from In Progress to Resolved.
- Broadcasts the change to every connected client holding
EasyCrm.Conversationswithin the tenant. - Each connected Inbox client in scope refetches its current view, filter and sort page.
- The conversation leaves the In Progress status tab for every viewer; it stays reachable through search and the customer's history.
Other paths
Assignment change moves the conversation into "mine"
Assign the conversation to Operator B. Operator B's Mine view gains the conversation, and the Unassigned view — if it was there — loses it, both within one refresh cycle.
Ai handover removes a conversation from "unassigned" without assigning it
The AI Assistant becomes the responsible party for a new conversation in Auto Reply mode. The conversation never appears in any operator's Unassigned view, and shows the AI indicator wherever it is visible.
If something goes wrong
Refresh storm on a high-traffic status
Many conversations change status in a short window, e.g. A bulk reassignment. Client refetches are debounced so a burst of change events triggers one refetch, not one per event.
Good to know
- View membership is always computed from current conversation state, never cached beyond the current page.
- A responsible-party change to the AI Assistant never populates the Unassigned view. (BRD §3.9)