A backlog represents unresolved tickets that have accumulated beyond a team's normal handling capacity or target resolution time. It is a direct indicator of whether staffing, processes, or volume spikes are putting service levels at risk.
Backlog is typically tracked as an absolute count and monitored against trend lines rather than in isolation—a backlog of 200 tickets means very different things for a team of 5 versus a team of 50.
Common causes of a growing backlog:
- Sudden contact volume spikes (product incidents, launches)
- Understaffing or high agent attrition
- Complex tickets requiring long handle times or cross-team input
- Inefficient routing that leaves tickets sitting in the wrong queue
Reducing backlog usually requires a combination of short-term surge capacity, improved self-service to prevent new inbound volume, and root-cause fixes to stop recurring issue types. Left unmanaged, a persistent backlog drives up first response times and erodes customer satisfaction.