Macha
CX & Support Metrics

Ticket Backlog

Definition

Ticket backlog is the number of open, unresolved support tickets that have accumulated and are still waiting to be handled at a given point in time.

Also known as: support backlogopen ticket backlogqueue backlog

How to calculate it

Backlog is a snapshot count of unresolved tickets at a moment in time, and it grows whenever new tickets arrive faster than they're resolved: end-of-day backlog = starting backlog + new tickets − resolved tickets.

Example: a queue starts the day with 200 open tickets, receives 150, and resolves 120. End-of-day backlog = 200 + 150 − 120 = 230. A backlog that climbs day over day means capacity isn't keeping up with volume.

Why it matters

Backlog is an early-warning gauge of team health. A growing backlog leads to longer resolution times, aging tickets, and SLA breaches — and it compounds, because delayed replies often trigger follow-up tickets. Automation helps by clearing the repetitive share of incoming volume before it ever adds to the pile.

Frequently asked

What is the difference between backlog and ticket volume?

Volume is how many tickets arrive over a period; backlog is how many remain unresolved at a point in time. Backlog grows when volume outpaces your resolution capacity.

How do you reduce a ticket backlog?

Increase resolution capacity (staffing, better routing, macros), cut inflow with self-service and automation, and triage so the oldest and highest-priority tickets are cleared first.

Put these ideas to work

Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.

Start Trial