When two agents work the same ticket at once. Collision detection shows who else is viewing or typing to prevent double-replies.
It’s a small mechanic with an outsized effect on a busy queue — see the ops that prevent double-replies.
Why it matters
In a shared inbox, nothing stops two people from opening the same conversation. Without a signal, both draft a reply, both hit send, and the customer gets two answers — sometimes contradictory. That wastes effort, looks disorganised, and erodes trust. The cost rises with queue volume: the busier the inbox, the more often two agents land on the same unassigned ticket at the same moment.
How it works
Collision detection relies on real-time presence. As soon as an agent opens a ticket, the system broadcasts that they are viewing it; when they start composing, it broadcasts that they are typing. Other agents see an avatar or banner on that conversation and can back off or coordinate. It is an advisory signal, not a hard lock — agents stay free to collaborate, but they do so with full awareness of who else is in the thread.
How to reduce it
- Assign on first touch so each ticket has a clear owner — see round-robin for automatic distribution.
- Use saved views so agents work distinct slices of the queue instead of all crowding the top.
- Keep presence indicators visible so a quick glance reveals whether a teammate is already replying.
For example, an e-commerce store running a flash sale might have five agents draining one queue. With collision detection, when one opens a refund request, the other four see the "viewing" marker and skip it — no duplicate refunds, no crossed wires.
How Cherryrise handles it
Cherryrise shows live presence and typing indicators inside every conversation, paired with assignment automation that gives each ticket an owner before two people race to it. Because the signal is real-time, an agent who opens a conversation a second after a teammate still sees that someone is already there. The result is a queue where coordination is the default, not an afterthought, and double-replies stop being a thing the team has to apologise for.