Zendesk Backlog by Assignee Report
Queue-level backlog tells you whether support is keeping up. It does not tell you where the backlog is actually sitting.
That matters because a queue can look manageable in aggregate while one person quietly holds too many open tickets, too many old tickets, or too many of the cases that are hardest to move. When that happens, the top-line backlog number hides the real operational issue: concentration.
This guide shows how to build a Zendesk backlog by assignee report, how to interpret the concentration patterns, and what to change when backlog is piling up around a few owners instead of reflecting a healthy distribution of work.
What this report should answer
A useful backlog by assignee report should answer:
- Which assignees hold the most open work right now?
- Which assignees hold the oldest work, not just the most tickets?
- Is backlog distributed reasonably across the team, or concentrated in a few people?
- Is the concentration stable, temporary, or getting worse over time?
For the metric definition, see backlog. For the broader team-capacity view, pair this report with Zendesk Tickets per Agent Report and Zendesk Agent Utilization Report. Keep it anchored in the support metrics dashboard.
Why assignee-level backlog reporting matters
Backlog is not only a demand problem. It is also a distribution problem.
If ten people each hold eight open tickets, the queue behaves differently from a case where two people each hold forty tickets and everyone else is mostly clear. The total backlog may be identical, but the operating risk is not. Concentrated backlog tends to produce:
- delayed follow-up on older tickets
- missed SLA windows
- more reassignment and escalation
- more context switching for overloaded agents
- uneven customer experience across similar issues
That is why backlog by assignee is a practical management view, not just a staffing curiosity. It shows whether ownership is balanced enough for the queue to stay healthy.
How to build the report in Zendesk
Use the Support: Tickets dataset in Zendesk Explore and focus on open work rather than solved history.
1. Define backlog consistently
Decide which statuses count as backlog for your workflow. Many teams include:
- new
- open
- pending
- on-hold, if it still reflects unresolved customer work
Be explicit about whether suspended or merged tickets are excluded. Consistency matters more than perfection.
2. Count open tickets by assignee
This is the simplest version of the report. It tells you who currently owns the largest share of unresolved work.
Do not stop there, though. Ticket count alone can make the load look balanced even when one agent holds the oldest or riskiest cases.
3. Add ticket age or aging buckets
Pair backlog count with age so you can see whether someone owns:
- many fresh tickets
- a normal load with a few very old tickets
- or both high volume and high age
For queue health, the age distribution is often more important than the raw count. Compare with Zendesk Backlog Aging Report to see whether concentration also shows up in stale work.
4. Trend it weekly
A snapshot is useful for today. A weekly trend tells you whether certain people repeatedly become the overflow point for the queue.
5. Add one explanatory cut if needed
Once you know where backlog sits, add one secondary cut such as:
- assignee plus priority
- assignee plus channel
- assignee plus group
- assignee plus tag
That helps explain whether the concentration comes from role specialization, bad routing, or uneven complexity.
The most useful report layouts
Open backlog by assignee
This is the core management view. It shows whether ticket ownership is reasonably spread across the team.
Backlog by assignee with aging buckets
This is often the most actionable layout because it separates “busy” from “stuck.” An agent with many fresh tickets may simply be on point for current intake. An agent with a small count of very old tickets may still carry the bigger customer risk.
Backlog by assignee and priority
Use this to see whether urgent or high-priority work is concentrated around a few owners. Pair it with Zendesk Ticket Priority Report.
Backlog by assignee and group
This helps when one person spans multiple queues or when leadership wants to know whether concentration is a team-level issue or a person-level issue.
How to interpret the patterns
One assignee holds far more open tickets than everyone else
This usually means routing or staffing has drifted. Either that person is deliberately handling a special class of work, or new assignments are not balancing correctly.
Several assignees have similar counts, but one holds the oldest tickets
That often indicates follow-up delay rather than intake overload. The issue may be attention management, handoff friction, or unclear next steps on complex cases.
Backlog concentration appears only in one group
That suggests a local queue problem. Review assignment rules and specialization inside that group before assuming the whole support team needs more headcount.
Total backlog looks stable, but one person keeps spiking
That is usually a workflow fragility signal. The queue may be healthy on average while one owner repeatedly becomes the place where unresolved work accumulates.
Common mistakes
- Treating ticket count as the whole story. Ticket age and priority matter just as much as the number of open items.
- Ignoring role differences. Some agents intentionally own escalations, VIP accounts, or specialist work. The report should trigger explanation, not shallow comparison.
- Using this as a productivity scoreboard. The point is to improve distribution and queue health, not to punish agents for the way work was assigned.
- Looking only at snapshots. One busy day is not the same as a structural pattern.
- Skipping aging context. A person with fewer but much older tickets may represent more risk than the person with the highest count.
What to do when backlog is concentrated
If backlog repeatedly sits with a few assignees:
- Review whether assignment rules are balancing new work the way you expect.
- Check whether specialists are absorbing too much work that should have stayed upstream.
- Compare open count and age together to separate overload from stuck follow-up.
- Look for rising group reassignment rate or replies per ticket if complex cases are bouncing.
- Decide whether the fix is routing, escalation design, queue ownership, or staffing.
The goal is not perfect equality. It is to avoid a queue where hidden concentration turns a manageable backlog into an uneven customer experience.
Where this report fits in your dashboard
This report works best beside:
- Zendesk Backlog Report
- Zendesk Backlog Aging Report
- Zendesk Tickets per Agent Report
- support metrics dashboard
Together, those views show whether backlog is growing, aging, and concentrating in ways the blended queue number cannot explain on its own.
FAQ
Is backlog by assignee the same as tickets per agent?
Not quite. Tickets per agent often describes overall workload or throughput context. Backlog by assignee focuses specifically on unresolved work that is still sitting in the queue.
Should pending tickets count as backlog?
Usually yes if they still represent unresolved customer work. If pending in your workflow mostly means “waiting on customer,” keep that choice consistent so trends stay comparable.
What if some agents intentionally carry more specialized backlog?
That can be completely normal. The report is still useful because it helps you separate intentional concentration from accidental overload.