Zendesk Assignment Time Report
Time to first assignment is the time between ticket creation and when it gets assigned to an agent. Long assignment times mean tickets sit in queues while customers wait. This guide covers how to track and reduce assignment time in Zendesk.
Why assignment time matters
- Customer wait — Every minute in queue is a minute the customer waits.
- SLA risk — If assignment is slow, first reply time will be slow.
- Routing issues — High assignment time often indicates broken routing rules or understaffed queues.
For the definition, see time to first assignment in the glossary.
How to measure assignment time
Assignment time = First assignment timestamp − Ticket created timestamp
In Zendesk Explore:
- Dataset — Use Support: Tickets.
- Metric — Create a calculated metric or use “Assignee stations” data.
- Caveat — Zendesk doesn’t have a native “time to first assignment” metric. You may need to calculate from ticket events or use a third-party tool.
Workaround: Tag on assignment
If you can’t calculate directly:
- Create a trigger that adds a tag when a ticket is assigned for the first time.
- Track time between ticket creation and the tag timestamp.
What to look for
| Signal | What it means |
|---|---|
| High avg assignment time | Routing or capacity issue |
| Assignment time varies by group | Some groups are understaffed |
| Assignment time spikes | Event-driven (outage, campaign) |
Reducing assignment time
1. Review routing rules
- Are tickets being routed automatically or sitting in a pool?
- Do triggers assign based on form, tags, or customer attributes?
- See Zendesk triggers audit.
2. Use round-robin or load balancing
- Zendesk has limited native load balancing; consider apps or third-party tools.
- Distribute tickets evenly to avoid agents cherry-picking.
3. Staff high-volume queues
- If “Billing” tickets have long assignment times, add agents to that group.
4. Enable auto-assignment
- For some workflows, auto-assigning based on form or channel reduces queue time.
Assignment time vs first reply time
These are related but different:
- Assignment time — Ticket creation → first assignment.
- First reply time — Ticket creation → first agent response.
If assignment time is 3 hours and first reply time is 4 hours, the agent is responding quickly after getting the ticket. If assignment time is 10 minutes and first reply time is 4 hours, tickets are being assigned but agents aren’t responding fast enough.
Diagnose both to find the bottleneck.
Common mistakes
- Ignoring unassigned tickets — Tickets that never get assigned don’t show up in “assignment time” stats but are the worst offenders. Track unassigned ticket count.
- Averaging across groups — One slow group can be masked by fast groups. Segment by group.
- No business hours — If tickets created overnight aren’t assigned until morning, calendar hours inflate the metric. Use business hours.
Dashboard elements
Include in your routing dashboard:
- Avg/median time to first assignment (overall and by group)
- Unassigned ticket count (current)
- Assignment time trend (weekly)
For overall metrics, see support metrics dashboard.
FAQ
What’s a good time to first assignment?
Depends on your workflow. For support teams with real-time routing, under 10 minutes. For manual assignment, under 1 hour.
How do I track unassigned tickets?
Create a view: Assignee is None + Status is not Closed. Count daily.
Should assignment be automatic or manual?
Automatic reduces assignment time but may route incorrectly. Use triggers with good conditions for high-volume queues; manual for complex tickets.