What is Backlog?

What is Backlog?

A support backlog is the number of open, unresolved tickets at any given point in time. Some backlog is normal—tickets that arrived today and are being worked on. Problematic backlog is aged tickets that have been sitting unresolved for days or weeks, growing faster than your team can clear them.

Healthy backlog management means tracking not just the total count but the age distribution. A backlog of 50 tickets that are all less than 24 hours old is fine. A backlog of 50 tickets where 20 are over 3 days old signals a capacity or process problem that needs immediate attention.

Why Backlog Matters

Backlog is a leading indicator of support health. A growing backlog means your inflow exceeds your team's throughput—the longer this continues, the worse response times and CSAT become. A healthy team maintains a steady-state backlog where daily inflow roughly equals daily resolution count.

Aged backlog is particularly damaging. Tickets older than 3 days have significantly lower CSAT scores because the customer has been waiting. They also take longer to resolve because the agent must re-read the conversation, the customer's situation may have changed, and context is lost. Preventing backlog growth is always easier than clearing an accumulated backlog.

Backlog in Practice

A support team came back from a holiday weekend to find a backlog of 180 tickets (their normal Monday is 60). Instead of working through them chronologically, they triaged by age and urgency: the 40 oldest tickets (pre-weekend) got assigned first, high-priority tags were filtered to a senior agent, and simple questions were routed to a junior agent with quick-reply templates. They cleared the backlog to normal levels by Wednesday, with the oldest tickets resolved within 24 hours of returning.