Backlog Isn’t Just a Number: How to Read Backlog + Aging Together

Backlog is the set of open, unsolved tickets waiting for your team. A single number (“we have 47 open tickets”) tells you size but not whether tickets are stuck or where the risk is. Reading backlog and aging together—how long tickets have been open—gives you that. This post is about why that matters and how to do it in Zendesk.

Why backlog count alone isn’t enough

• No trend — One snapshot doesn’t tell you if backlog is growing or shrinking.
• No aging — You don’t see if tickets are 2 hours old or 2 days old; aging tells you where tickets are stuck.
• No breakdown — You don’t see which group, tag, or priority is driving the number.

So: report backlog over time, add aging (e.g. 0–24h, 24–48h, 48h+), and break down by segment. Then you know when and where to act. See ticket backlog dashboard and Zendesk backlog report for how to build and use that view.

How to read backlog + aging together

• Backlog growing, aging stable — Volume may have spiked; resolution may be keeping up for now. Watch; if aging starts to rise, you have a capacity issue.
• Backlog stable, aging rising — Tickets are staying open longer. Look at complexity, routing, or capacity in the segments where aging is worst.
• Backlog shrinking, aging shrinking — You’re closing more than you’re adding and clearing old tickets. Healthy.
• Backlog growing, aging rising — Capacity or prioritization problem; act (triage, reassign, or add coverage). See support metrics dashboard and support ops metrics for a weekly cadence.

How to report backlog and aging in Zendesk

In Zendesk Explore you can:

• Backlog count — Count tickets in “open” (or open + pending) status over time.
• Aging — Time since ticket creation (or last update) bucketed (e.g. 0–1 day, 1–3 days, 3+ days).
• Breakdown — By group, tag, priority so you see which segment is driving backlog and aging.

For step-by-step, see Zendesk backlog report. For a view that combines size, aging, and a path to the tickets, see ticket backlog dashboard.

What to do when backlog and aging spike

1. Check volume — Did ticket inflow spike?
2. Check resolution — Did resolution time or throughput drop?
3. Check segments — Which group, tag, or priority? Focus there first.
4. Drill to tickets — Open the list of tickets in that segment and triage, reassign, or escalate.

For more on backlog and weekly review, see support dashboard template and customer support dashboard.

See your backlog in minutes — start free