Skip to content
A red and white streetcar on a downtown street lined with glass office towers.

Agent collision detection: two agents, one ticket, one answer

The worst reply a customer can get is two of them, saying different things. Cayzu shows you who else has a ticket open, and whether they're typing, before you hit send.

Get started for freeWatch a demoNo credit card. No contract.

The collision banner: who else has this ticket open

Open a ticket and a strip at the top names every other agent who has it open. If one of them has started a reply, the strip says so. A glance tells you whether to write, to wait, or to leave a private note and move on to the next ticket.

Why collision detection matters on a shared queue

On a team of three, everyone watches the whole queue. A ticket with no owner yet is fair game, and two people grabbing it at once is the normal case, not the rare one. Collision detection warns people off the double reply with nothing to set up, and it doesn't slow anyone down. Nobody has to claim tickets by hand or ask in chat who's got it.

Larger teams tend to lean on assignment rules and round robin to give each ticket an owner first. The banner still catches the cases rules miss: an escalation, a manager stepping in, a reopened ticket.

See it with your own tickets.

Every feature for 15 days. No credit card. No contract.

Setting up collision detection

  1. There's nothing to turn on. Collision detection is part of the ticket screen for every agent.
  2. Decide what agents do when they see the banner, and agree on one simple habit, such as "leave an internal note, don't reply".
  3. Add an assignment rule or round robin for the queues where collisions keep happening, so tickets arrive with an owner.
"Also on this ticket" shows that a second agent has the same ticket open.
"Also on this ticket" shows that a second agent has the same ticket open. (Example workspace.)

Collision detection on every plan, and its limits

Collision detection is on every plan. Plans and prices are on the pricing page.

The banner has two limits. It warns; it doesn't lock the ticket, so a determined second reply still goes out. And it works per ticket, so if the same customer wrote in twice, two agents can answer the two tickets without ever seeing a banner. Merging the duplicates is the fix for that one.

Related: internal notes, assignment rules, and the ticket queue.

Questions people ask

It's a banner on the ticket that tells you another agent is looking at it right now, and a second one that says they've started typing a reply. You see it before you write, not after the customer has two answers.

Try it with your own tickets

Every feature for 15 days. No credit card. No contract.