BookbagBookbag
Glossary

Ticket Backlog

A ticket backlog is the volume of open, unresolved support tickets that have aged beyond their expected resolution window — representing demand that the support team hasn't yet caught up with.

What it means

Key insight

Backlog is the clearest signal that ticket volume has outpaced team capacity. For ecommerce brands, backlog spikes predictably during peak periods like BFCM — the only durable solution is automating the high-volume routine questions before they pile up.

Ticket backlog = total open tickets that have exceeded their SLA or target response/resolution time. Some teams track 'raw backlog' (all open tickets) and 'aged backlog' (open tickets past their SLA target) separately. Aged backlog is the more meaningful number because it represents customers actively waiting too long. Backlog grows when inbound ticket volume exceeds the team's throughput. In ecommerce, this is almost always a seasonal phenomenon — BFCM, holiday sales, and post-holiday returns create volume spikes that overwhelm teams sized for normal operations. A team that handles 500 tickets/day at steady state may face 2,000 tickets/day during peak week. The two levers for backlog reduction are: (1) increase throughput — more agents, longer hours, or faster handling via AI assistance — and (2) reduce inbound volume — through deflection, proactive order notifications that preempt WISMO tickets, or AI resolution of routine questions. Backlog has a compounding effect on CSAT: every day a ticket sits unresolved, customer frustration rises. A ticket that should have been a neutral interaction becomes a negative one purely due to wait time. Clearing backlog quickly — even with AI first responses — limits CSAT damage.

Why it matters

Unmanaged backlog means customers waiting too long, SLAs being missed, and agents firefighting rather than working systematically. For ecommerce brands, backlog is also a revenue risk — a customer waiting 3 days for a return answer is a customer considering a chargeback or leaving a negative review. Monitoring and acting on backlog trends is foundational support operations.

How Bookbag helps

AI absorbs volume spikes automatically

Bookbag's AI handles incoming ticket volume at any scale without additional staffing — preventing backlog from forming during peaks by resolving routine tickets immediately.

Backlog visibility in real time

The Bookbag dashboard shows open ticket volume, aged tickets, and SLA status so managers can see backlog building and act before it becomes critical.

Priority surfacing for aged tickets

Tickets approaching or past SLA are surfaced automatically in the queue so agents work the oldest, most urgent items first rather than defaulting to newest-first.

Frequently Asked Questions

See Bookbag in action

Join the ecommerce teams resolving more tickets, answering 24/7, and turning support into a revenue channel with Bookbag.