Support Backlog
What is Support Backlog?
Support Backlog is the accumulation of open, unresolved support tickets that have not been handled or resolved within an expected timeframe. Unlike queue size (a real-time snapshot of tickets waiting), backlog specifically refers to tickets that are overdue relative to expected handling times. A growing backlog is a lagging indicator of under-staffing, unexpected volume spikes, or systemic resolution bottlenecks, and a leading indicator of SLA failures and customer churn.
How is Support Backlog calculated?
Backlog = Total open tickets − Tickets opened within the current business day
Different teams define backlog differently. Some count all tickets older than one business day; others count only tickets that have breached SLA. Pick one definition and hold it constant. Track backlog size at the same time each day (end of shift) for consistent trend analysis.
What is a good Support Backlog?
B2B SaaS, end-of-day snapshot
What are the most common Support Backlog mistakes?
- 1Letting backlog grow silently without threshold alerts. Define a backlog threshold (e.g., >50 tickets or >1 day equivalent volume) that triggers a staffing escalation.
- 2Clearing backlog by closing old tickets without resolving them. Artificially reducing backlog inflates resolution rate without serving customers.
- 3Not separating backlog by priority. P1 tickets in backlog are a customer emergency; P3 tickets at the same age are a workflow inefficiency.
- 4Treating backlog as a support team problem exclusively. Chronic backlog often has root causes in product stability, documentation gaps, or customer success coverage gaps.