What is Backlog?

Backlog definition: a backlog is the set of open, unresolved tickets waiting on your team at any given moment. The term is borrowed from inventory and project management, where it describes work that has been received but not yet completed, and carries the same meaning in customer support — every conversation that has arrived but is not yet closed counts toward the backlog.

In practice, "what does backlog mean" depends on which tickets you choose to include. Most modern help desks count any ticket whose status is open, pending, or on-hold. Tickets marked solved, closed, or spam are excluded. A few teams also exclude tickets that are paused waiting for a customer reply, because the clock is on the customer's side, not the team's.

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 the age distribution, not just the total count. 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.

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. Zendesk's CX Trends 2024 report found that 70% of customers expect a conversational, immediate experience from support, and slow first responses are the single most cited reason customers say service is getting worse. A team running with chronic backlog cannot meet that expectation.

Aged backlog is particularly damaging. Tickets older than 3 days have significantly lower CSAT scores because the customer has been waiting, and 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. A 2023 Harvard Business Review analysis of 1.25M sales leads also showed that responding within 5 minutes makes you 21× more likely to qualify the lead — the same effect compounds on support, where every additional day of wait time degrades the outcome. Preventing backlog growth is always easier than clearing an accumulated backlog.

In early 2026, a 5-person 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.