Support Queue Size Calculator for Ecommerce

Example Data Table

These sample scenarios demonstrate how queue size changes with demand, handle time, and staffing.

Scenario	Tickets/day	Agents	AHT (min)	Utilization	Avg wait (min)	SLA %
Lean team, moderate demand	166	6	10.0	77.1%	6.0	100.0%
Peak sale week	510	10	14.0	162.1%	—	—
Strong self-service and staffing	240	9	9.0	58.8%	0.5	100.0%

Tip: During promotions, raise seasonality and re-check recommended staffing.

Formula Used

Adjusted demand: AdjustedTicketsPerDay = TicketsPerDay × Seasonality × (1 − Deflection%).
Arrival rate: λ = AdjustedTicketsPerDay ÷ CoverageHours (tickets per hour).
Service rate: μ = 1 ÷ AHTHours (tickets per hour per agent).
Effective agents: FTE = ScheduledAgents × (1 − Shrinkage%) × MaxOccupancy%.
Total capacity: TotalServiceRate = FTE × μ, CapacityPerDay = TotalServiceRate × CoverageHours.
Utilization: ρ = λ ÷ TotalServiceRate. If ρ ≥ 1, backlog grows.
Erlang C: Uses M/M/c queue to estimate probability of wait (Pw), average wait time (Wq), and queue size (Lq).
SLA probability: P(wait ≤ t) = 1 − Pw × e^{−(cμ − λ)×t}.
Backlog forecast: ProjectedOpen = max(0, CurrentOpen + (AdjustedTicketsPerDay − CapacityPerDay) × HorizonDays).

How to Use This Calculator

Enter average daily tickets and your coverage hours.
Set handle time based on real ticket logs.
Add scheduled agents, then shrinkage and occupancy limits.
Apply deflection and seasonality to match current demand.
Set an SLA time and SLA target percentage.
Click Calculate to view queue size, wait time, and backlog forecast.
Use the recommendation to plan staffing changes.
Export results using CSV or PDF downloads.

Ticket Inflow Versus Capacity

Queue size starts with inbound volume and coverage time. If you receive 250 tickets per day across 10 coverage hours, arrivals average 25 tickets per hour. With a 12‑minute handle time, one agent can complete about 5 tickets per hour. Eight scheduled agents provide 40 tickets per hour before adjustments, so the system can be stable. Category mix matters; returns issues often raise handle time.

Shrinkage Converts Headcount Into Real Capacity

Shrinkage removes paid time from ticket work. At 25% shrinkage, 8 scheduled agents become 6.0 effective agents. Using the same 12‑minute handle time, capacity drops from 40 to 30 tickets per hour. If arrivals remain 25 tickets per hour, utilization becomes 25/30 = 83.3%, leaving little buffer for spikes.

Occupancy Limits Protect Resolution Quality

Occupancy is a quality guardrail, not a penalty. Capping occupancy at 85% turns 6.0 effective agents into 5.1 working capacity equivalents. Service capacity becomes roughly 25.5 tickets per hour. That pushes utilization close to 98%, which increases the probability of waiting and inflates the average queue during busy intervals.

Deflection and Seasonality Shift the Baseline

Self‑service reduces tickets that reach agents. A 10% deflection rate turns 250 raw tickets into 225 agent‑handled tickets. Seasonality then scales that number; a 1.35 multiplier during a sale event lifts 225 to 303.8 tickets per day. Over 10 hours, that becomes 30.4 tickets per hour, which can overwhelm the same staffing plan.

SLA Probability Exposes Customer Experience Risk

The model estimates the probability that a ticket waits and how often it meets an SLA window. When utilization rises above 90%, the wait probability climbs quickly, and meeting an SLA like 80% within 4 hours becomes difficult. Adding one scheduled agent or lowering handle time by 1–2 minutes can materially improve SLA probability.

Backlog Forecast Turns Metrics Into Actions

Net flow is adjusted demand minus daily capacity. If net flow is +15 tickets per day, a 7‑day horizon adds about 105 tickets to the open queue. If net flow is −20, the backlog shrinks by about 140. Use the forecast and the chart to decide whether to add shifts, expand coverage hours, improve deflection, or streamline macros.

FAQs

1) What does utilization represent in this calculator?

Utilization compares hourly arrivals to hourly capacity. A value near 100% means agents are continuously busy, so small demand spikes create long waits. Aim for a buffer, especially during campaigns, weekends, and product launches.

2) Why can my backlog grow even if the system looks stable?

Steady‑state queue math assumes average conditions. If you have time‑of‑day surges, multi‑touch tickets, or batch work like refunds, net daily flow can still be positive. Use the backlog forecast and seasonality to capture growth.

3) How should I estimate average handle time accurately?

Use ticket platform reports for the last 2–4 weeks. Separate major categories like returns, delivery, and payments. Exclude outliers, then compute the weighted average minutes per ticket. Recheck after process changes or new policies.

4) What is shrinkage, and what range is typical?

Shrinkage is non‑ticket time: meetings, coaching, QA, breaks, and admin. Many teams land between 20% and 35%, but it varies by maturity and tooling. Track it weekly so staffing plans reflect real productive hours.

5) How do I choose an SLA time and target percentage?

Pick the customer promise you publish, then align it to staffing. Common first‑response targets are 2–6 hours for email and under 15 minutes for chat. Higher targets require either more agents, lower handle time, or stronger deflection.

6) What are the fastest ways to reduce queue size without hiring?

Improve deflection with a clearer help center, add macros, and standardize replies. Reduce handle time with better order lookup and templated workflows. Expand coverage hours during peaks. Triage by urgency so simple tickets exit the queue quickly.