Operations

What is support backlog?

Also known as: ticket backlog

Published September 10, 2026 · Reviewed by the Fidiora team

Definition

A support backlog is the accumulated set of unresolved requests that have exceeded the team normal working window. A backlog is a flow problem: it exists whenever the arrival rate of new requests exceeds the rate at which the team resolves them, and it compounds because delay generates follow-ups.

Why it matters

Backlogs are usually treated as an effort problem and solved with overtime or temporary staff. That clears the pile without changing the flow, so it returns. The durable fix is to change the arrival rate or the resolution rate permanently, and only one of those scales without hiring.

What to know

  • The compounding effect is the real damage: each delayed ticket generates follow-up messages that add to arrivals.
  • Temporary capacity clears a backlog and never prevents the next one, because inflow is unchanged.
  • Track arrivals and resolutions as two daily lines. Their gap is the only number that predicts the backlog.
  • Cherry-picking makes the backlog look better and the oldest tickets much worse.
  • Ageing tickets convert small problems into churn risk, so backlog age matters more than backlog size.

How to calculate it

Backlog change = arrivals - resolutions, over the same period

An example

Example: a team receives 320 tickets a day and resolves 300. The backlog grows by twenty a day, which is invisible for a week and a crisis in a quarter. Adding a temporary agent clears the pile and the gap of twenty reopens the moment they leave.

Common mistakes

  • Clearing a backlog with temporary capacity and changing nothing about inflow
  • Measuring backlog size while ignoring backlog age
  • Allowing agents to work newest-first, which buries the oldest customers
  • Reporting the backlog without reporting arrivals versus resolutions
Where Fidiora fits

Fidiora works both sides of the equation. It resolves routine questions on contact, which lowers arrivals into the human queue, and it hands the rest over with context, which raises resolution rate. That flips the gap and keeps it flipped.

See Pricing
FAQ

Questions

How do I clear a support backlog?
Reduce arrivals first, then batch the quick repetitive wins, then unblock the stalled tickets. Doing it in the other order clears the pile temporarily and guarantees it returns as soon as the extra effort stops.
Why does our backlog keep coming back?
Because the arrival rate still exceeds the resolution rate. Any clean-up that does not change one of those two numbers is a pause, not a fix.
Should I hire to clear a backlog?
Hire for the one-time pile if you must, but do not hire for the ongoing flow unless the volume is genuinely irreducible. Removing repetitive volume is faster to implement and does not have to be unwound later.

Related terms

Support queue A support queue is the ordered set of requests waiting to be worked, usually grouped by team, topic, or priority. The qu... Ticket ageing Ticket ageing is the tracking of how long unresolved requests have been open, usually bucketed into ranges such as under... Ticket volume Ticket volume is the number of support requests received in a period. On its own it says little, because volume tracks c... Support automation Support automation is the use of software to perform steps in the handling of a customer issue that a person would other...
Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

Start Free Book a 15-min Demo

No credit card · Live in under an hour