Ticket backlog is the cumulative count of unresolved customer support requests awaiting agent action at any point in time.

Backlog is a lagging indicator of capacity problems. When inbound volume exceeds resolution capacity over sustained periods, backlog grows. Small backlogs are normal—work in progress—but growing backlogs indicate structural understaffing, efficiency problems, or a spike you haven't recovered from. For SLA-driven teams, backlog age distribution matters more than total count: 50 tickets under 4 hours old is fine; 50 tickets over 24 hours is a crisis.

Monitor backlog trends, not snapshots. A Monday morning backlog of 200 tickets that clears by Wednesday is healthy absorption of weekend volume. A backlog of 200 that's been 200 for three weeks means you're exactly at capacity with no buffer. Fintech and insurance companies with regulatory response time requirements should set backlog alerts tied to SLA aging—you need to know when tickets are approaching breach, not after they've breached.

Related terms: Ticket volume, First reply time, Agent occupancy

---

# Fintech-Specific Terms