Ticket backlog
The backlog is the set of questions open and still unresolved at a given moment. More than its size, what gets watched is its trend: if more questions come in than get closed, the backlog grows, and it grows cumulatively even when the daily difference is small.
What is ticket backlog?
The backlog is the set of questions open and still unresolved at a given moment. More than its size, what gets watched is its trend: if more questions come in than get closed, the backlog grows, and it grows cumulatively even when the daily difference is small.
Also: support queue · open tickets · arrears
Why it matters
What changes in a SaaS
It is the metric that warns earliest. Response times degrade slowly and get noticed late; the backlog starts climbing the first day capacity falls short. A difference of three tickets a day is sixty a month, and by that point it is not recoverable by working a bit harder.
Ticket backlog in detail
The ratio is what to watch
Tickets closed over tickets opened in the same period. Above one, the backlog falls; below one, it rises. The absolute size depends on the business, but a ratio under one means the same thing everywhere.
Age matters more than count
A hundred conversations opened today are nothing; ten opened three weeks ago are a problem, because each one is a customer who has stopped waiting. It is worth looking at the age distribution rather than only the total.
What to do when it grows
Not asking for extra hours, which buys a week. Either intake drops — by resolving the repeated questions without a person, or by fixing whatever in the product generates them — or capacity rises. Anything else moves the problem forward a few days.
How Intake handles it
Questions about ticket backlog
What is a healthy backlog?
There is no universal number, because it depends on volume and on the response time you promised. What is universal is the ratio: closed over opened, sustained above one. Below that, the size only grows.
Does auto-closing old tickets fix the backlog?
It fixes the chart, not the backlog. Those conversations are customers who did not get an answer, and they usually come back — either as a new ticket or as churn.
Related terms
A term on its own is only half understood. These come up in the same conversation.
Contact rate
Contact rate is how many support questions a business generates relative to its size: normally tickets per customer per month, or per hundred active customers. It is the metric that says whether support will scale with the business or suffocate it.
Resolution time
Resolution time is how long passes between a question arriving and it being resolved and closed. Unlike first response time, it measures the whole process, including waits on the customer and escalations to other teams.
Deflection rate
Deflection rate is the percentage of questions resolved without a person getting involved, either because the customer found the answer themselves or because an automated agent closed it. It is the metric used to justify any investment in self-service or in AI.
Ticket
A ticket is the record of a customer question inside a support tool. It groups every message in that conversation under one identifier and adds what is needed to manage it: status, owner, priority, tags and the history of what has happened.
SLA — Service level agreement
A service level agreement is the written commitment to respond within set deadlines. It fixes maximum times — usually first response and resolution — defines the hours in which they count, and normally states what happens when they are missed.
FCR — First contact resolution
First contact resolution is the percentage of questions resolved in the first interaction, without the customer having to write again and without the conversation passing to another person. It is the metric that best summarises whether the team has what it needs to answer within reach.
