Ticket Backlog
Definition
Ticket backlog is the number of open, unresolved support tickets that have accumulated and are still waiting to be handled at a given point in time.
How to calculate it
Backlog is a snapshot count of unresolved tickets at a moment in time, and it grows whenever new tickets arrive faster than they're resolved: end-of-day backlog = starting backlog + new tickets − resolved tickets.
Example: a queue starts the day with 200 open tickets, receives 150, and resolves 120. End-of-day backlog = 200 + 150 − 120 = 230. A backlog that climbs day over day means capacity isn't keeping up with volume.
Why it matters
Backlog is an early-warning gauge of team health. A growing backlog leads to longer resolution times, aging tickets, and SLA breaches — and it compounds, because delayed replies often trigger follow-up tickets. Automation helps by clearing the repetitive share of incoming volume before it ever adds to the pile.
Frequently asked
What is the difference between backlog and ticket volume?
Volume is how many tickets arrive over a period; backlog is how many remain unresolved at a point in time. Backlog grows when volume outpaces your resolution capacity.
How do you reduce a ticket backlog?
Increase resolution capacity (staffing, better routing, macros), cut inflow with self-service and automation, and triage so the oldest and highest-priority tickets are cleared first.
Related terms
Ticket Volume
Ticket volume is the total number of support requests received over a given period, across all channels a team handles..
Backlog Rate
Backlog rate is a measure of how the volume of unresolved support tickets is changing — typically the ratio of open or incoming tickets to those being resolved over the same period..
Ticket Aging
Ticket aging is a measure of how long open support tickets have been unresolved, usually grouped into buckets (for example 0–1 days, 1–3 days, 3–7 days, 7+ days) to show where tickets are getting stuck..
Average Resolution Time
Average Resolution Time is the average length of time it takes to fully resolve a support ticket, measured from when it's created to when it's marked solved..
SLA Breach
An SLA breach occurs when a support team fails to meet a target defined in a Service Level Agreement — for example, not sending a first response or resolving a ticket within the promised time window..
Put these ideas to work
Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.
Start Trial
Zendesk
Freshdesk
Gorgias
Front
Shopify
Stripe
Slack
Notion
Google Workspace
Confluence