Make backlog actionable
A ticket backlog dashboard should show you how big your backlog is, how it’s aging, and where the risk is—then let you open the actual tickets so you can prioritize and act. This guide is about what to put on that dashboard and how to use it.
What is backlog (and why a dashboard helps)
Backlog is the set of open, unsolved tickets waiting for your team. A single number (“we have 47 open tickets”) is useful, but you need more: trend over time, aging (how long tickets have been waiting), and breakdown by group, tag, or priority so you know where to focus. A ticket backlog dashboard that shows size + aging + breakdown gives you that.
What to put on a backlog dashboard
- Backlog count — Total open tickets (or open unsolved, depending on your definition). Compare to last week or last month so you see direction.
- Aging — How long have tickets been open? Buckets like 0–24h, 24–48h, 48h+ (or 0–1 day, 1–3 days, 3+ days) so you spot stuck tickets.
- Breakdown — By group, tag, priority, or requester so you know what’s driving the number.
From there, the critical step: click through to the list of tickets that make up that slice. The dashboard should link to a filtered view (e.g. open, created in last 7 days, tag X) so you can triage and assign.
How to read backlog + aging together
Backlog alone can be misleading (e.g. high volume but fast resolution). Aging tells you if tickets are piling up. When backlog grows and aging worsens, you have a capacity or prioritization problem. When backlog is stable but aging spikes in one segment (e.g. one tag or group), you have a local bottleneck. For more on interpreting backlog in Zendesk, see Zendesk backlog report.
What to do when backlog spikes
- Check volume — Did ticket volume or ticket inflow spike? If yes, consider short-term capacity or triage.
- Check resolution — Did resolution time or throughput drop? If yes, look at process, complexity, or staffing.
- Check segments — Is the spike in one group, tag, or priority? Focus there first.
- Drill to tickets — Use your dashboard (or tool) to open the list of tickets in that segment and prioritize, reassign, or escalate.
For a full set of support KPIs and a weekly cadence, see support metrics dashboard and support ops metrics.
Common mistakes
- Only watching the number — Backlog count without aging or breakdown hides where the problem is.
- No link to tickets — A chart that doesn’t let you open the underlying tickets is decorative.
- Ignoring trend — One snapshot isn’t enough; compare to last period so you see if it’s getting better or worse.
FAQ
How do I build a backlog report in Zendesk Explore?
See Zendesk backlog report for how to track backlog trends and prioritize work without spreadsheets.
What’s a good backlog size?
It depends on volume, SLA, and capacity. What matters is trend and aging: stable or shrinking backlog with reasonable aging is usually healthy; growing backlog with increasing aging is a signal to act.
Where does backlog fit in our weekly review?
Use it as the second beat after volume: “How many came in? How many are still open? Where are they stuck?” See support dashboard template and customer support dashboard for a full agenda.