Alert when one customer contacts support three or more times about the same order or issue. Repeat contact is a reliable indicator that the process failed rather than that the customer is difficult, and the fix is almost always to change who handles it rather than to send a better version of the same reply.
Why this one is worth an interruption
Repeat contact usually means one of a small number of things: the first answer did not actually resolve it, the customer was passed between people and had to re-explain, or they were promised an update that never came.
All three are process failures with the same remedy: one named person takes it, contacts the customer directly, and owns it until it is closed. Continuing the ticket thread with a different agent reproduces the failure that caused the third message.
The threshold
Count contacts about the same subject, not total contacts from that person.
| Condition | Set it to | Why that number |
|---|---|---|
| Trigger | 3 contacts on one order or issue | By three, something has gone wrong |
| Window | within 14 days | Older contacts are usually a separate matter |
| Value flag | lower the threshold above a value floor | More at stake, less patience warranted |
| Agent-change flag | handled by 3 different people | Being passed around is its own failure |
| Exclude | ongoing normal correspondence | A long conversation is not repeat contact |
Who should receive it
A named person who takes it over, not the queue it has been sitting in.
- Whoever can resolve it outright, including spending money.
- A manager, above a value floor or where the tone has deteriorated.
- Not the same queue. Routing it back reproduces the failure.
What to do when it fires
- Read the whole history before replying. Making them explain again is the most common way this gets worse.
- Have one named person take it end to end and say so to the customer.
- Resolve it in one contact if at all possible, even if that costs slightly more than the strictly correct outcome.
- Record what caused the repeat contact, because it is usually a process gap that will produce more.
When not to set this alert
Do not set this where support conversations are naturally long and iterative, such as custom or made-to-order work. Message count is not a failure signal there.
Do not use it as an agent performance metric. It measures the process, and using it to judge individuals reliably produces premature ticket closing, which makes it worse.
Common questions
What does repeat contact indicate?
Usually that the first answer did not resolve the issue, the customer was passed between people and had to re-explain, or a promised update never arrived. All three are process failures rather than difficult customers.
What should change on the third contact?
Ownership. One named person should take it end to end and say so. Continuing the same thread with a different agent reproduces the failure that generated the third message.
Should this be used to measure support staff?
No. It measures the process, and using it to judge individuals encourages closing tickets prematurely, which increases repeat contact rather than reducing it.