The Hidden Cost of Ticket Reassignment
Ticket reassignment seems harmless—just moving work to the right person. But every reassignment has hidden costs that accumulate quickly.
Why reassignment is expensive
1. Time delay
Each reassignment adds queue time. The new agent doesn’t pick it up instantly; it sits in their queue. Multiple reassignments can add hours or days to resolution time.
2. Context loss
The first agent learned things about the issue. Unless they document perfectly (rare), that context is lost. The second agent starts over, asks the same questions, and frustrates the customer.
3. Customer friction
“Let me transfer you to someone else” is never what customers want to hear. It signals the first person couldn’t help. Do it twice, and trust erodes.
4. Agent overhead
Reassigning takes time: reading, deciding, documenting, routing. That’s time not spent resolving.
Measuring reassignment
Reassignment rate
Reassignment rate = Tickets reassigned / Total tickets
Track overall and by group. A 30% reassignment rate means nearly a third of tickets bounce at least once.
Group reassignment rate
Group reassignment rate focuses on cross-group moves (tier 1 → tier 2, support → billing). These are often costlier than within-group reassignments.
Time added by reassignment
Compare resolution time for tickets with 0 reassignments vs 1+ reassignments. The gap shows the time cost.
Why tickets get reassigned
| Reason | Fix |
|---|---|
| Wrong initial routing | Improve triggers and forms |
| Skills gap | Training or specialization |
| Ticket complexity | Escalation paths, not ping-pong |
| Policy (“not my job”) | Clear ownership rules |
| Cherry-picking easy tickets | Routing fairness, not choice |
Reducing reassignment
1. Better routing
Improve triggers, forms, and auto-assignment so tickets land in the right place first. See Zendesk triggers audit.
2. Train for breadth
If agents can handle more issue types, they don’t need to reassign as often. Invest in cross-training.
3. Clear escalation paths
Reassignment isn’t always bad—complex issues need specialists. But escalation should be intentional, not defaulting because “I don’t know.”
4. Internal notes
When reassignment is necessary, require internal notes summarizing the issue. Context transfer reduces rework.
5. Discourage cherry-picking
If agents can pick tickets from a pool, they’ll choose easy ones. Routing should assign, not offer a buffet.
When reassignment is OK
Not all reassignment is bad:
- Legitimate escalation — Tier 1 can’t handle; tier 2 has expertise.
- Coverage handoff — Shift ends; next shift takes over.
- Customer request — Customer asks for a specific agent.
The goal isn’t zero reassignment; it’s avoiding unnecessary reassignment.
Tracking in your dashboard
Add to your support ops metrics:
| Metric | Target |
|---|---|
| Reassignment rate | < 20% |
| Avg reassignments per ticket | < 0.5 |
| Resolution time (reassigned tickets) | Compare vs non-reassigned |
FAQ
What’s a good reassignment rate?
Depends on complexity, but under 20% is healthy for many teams. If you’re above 30%, investigate.
Should I penalize agents for reassigning?
No—but track and discuss. If one agent reassigns 50% of tickets, understand why. It might be training, routing, or scope clarity.
Does reassignment affect CSAT?
Usually yes. Multiple touches and “let me transfer you” lower satisfaction. Track CSAT by reassignment count.