# 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.

## 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.

## Related features

- [Internal notes: Leave the other agent a private note on the ticket instead of a second reply to the customer.](https://www.cayzu.com/internal-or-private-notes/)
- [Round robin: Give every new ticket one owner the moment it arrives, so nobody has to guess whose it is. On Enterprise.](https://www.cayzu.com/round-robin-automated-distribution/)
- [Merge tickets: When the same customer writes in twice, merge the two tickets so there's one place to answer.](https://www.cayzu.com/split-merge-helpdesk-support-tickets/)

## 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.

## 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.

## Collision detection on every plan, and its limits

Collision detection is on every plan. Plans and prices are on the [pricing page](https://www.cayzu.com/pricing/).

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](https://www.cayzu.com/split-merge-helpdesk-support-tickets/) the duplicates is the fix for that one.

Related: [internal notes](https://www.cayzu.com/internal-or-private-notes/), [assignment rules](https://www.cayzu.com/automation-through-assignment-rules/), and [the ticket queue](https://www.cayzu.com/helpdesk-ticketing-system/).

## Questions people ask

### What is agent collision detection?

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.

### Does it lock the ticket so only one person can reply?

No. It warns, it doesn't block. Both agents can still reply if they choose to, so the banner is a nudge to leave a note or step back, not a gate.

### How is this different from assigning tickets?

Assignment says who owns a ticket. Collision detection covers the moments ownership doesn't: a manager peeking in, a colleague helping out, a ticket nobody has claimed yet. The two work best together.

### What happens if two people do answer the same ticket?

Both replies go to the customer as separate emails. The fix is a quick follow-up from one agent, then an assignment rule or round robin so the ticket has one owner next time.

### Which plan has collision detection?

Every plan, Standard included, and the free trial too.

---

The web page: https://www.cayzu.com/agent-collision-detection/
