Why Your Zendesk Backlog Keeps Growing (and How to Fix It)
Backlog is the set of open, unsolved tickets waiting for your team. When it keeps growing, it’s usually one (or more) of four things: inflow up, resolution slowed, reopens up, or prioritization stuck. This post walks through each and gives three fixes that work for Zendesk teams.
Four reasons backlogs grow
- Inflow increased — Ticket inflow or ticket volume went up (campaign, launch, seasonality). You’re getting more tickets than before; if capacity didn’t change, backlog grows. See ticket backlog dashboard and Zendesk backlog report.
- Resolution slowed — Throughput (tickets closed per period) dropped or resolution time rose. Harder tickets, process issues, or missing knowledge can slow resolution. See Zendesk resolution time report.
- Reopens up — Tickets are being “solved” and then reopened. That adds back to the effective backlog (and lengthens full resolution time). See ticket reopen rate.
- Prioritization stuck — Tickets sit in the wrong queue or aren’t triaged; they age and backlog looks worse even if volume and resolution are stable. Check routing and time to first assignment.
So: when backlog grows, check volume, resolution, reopens, and routing/prioritization. For how to read backlog and aging together, see Backlog isn’t just a number.
Three fixes that work
- Triage and routing — Get tickets to the right agent or group quickly. Fix routing rules, skills, or assignment so tickets don’t sit in a shared queue. That can reduce backlog and improve first reply time at once. See reduce first response time.
- Capacity (when it’s really capacity) — If volume has grown and resolution time is stable or rising, you may need more people (or overtime, or overflow). Use backlog and volume trends to make the case. See support ops metrics and support metrics dashboard.
- Quality and reopens — If reopen rate is high, you’re “solving” tickets that come back. Fix definition of “solved,” handoffs, and knowledge for high-reopen tags. See reopen rate as a quality metric and ticket reopen rate.
Don’t try to fix everything at once; pick one lever (triage, capacity, or quality) and tie it to a concrete action and tickets.
How to read backlog + aging
Backlog count alone isn’t enough. Add aging (how long tickets have been open) and breakdown (by group, tag, priority) so you know where to focus. See Backlog isn’t just a number and ticket backlog dashboard.
When to add capacity
When backlog is growing and: - Volume has clearly increased, and - Resolution time is stable or rising, and - Triage and routing are already in good shape,
…then capacity is often the bottleneck. Use your support metrics dashboard and support ops metrics to review weekly and make the case with numbers.