| Scenario | Avg orders | Peak mult | Contact % | Deflect % | Agents | AHT (min) | Est. tickets | Agents req. |
|---|---|---|---|---|---|---|---|---|
| Promo weekend | 2,500 | 2.5 | 2.2 | 15 | 14 | 11.6 | ≈ 2,018 | ≈ 7 |
| Flash sale | 2,500 | 3.2 | 2.7 | 10 | 14 | 12.5 | ≈ 3,024 | ≈ 10 |
| New collection drop | 2,500 | 1.9 | 1.8 | 20 | 14 | 10.0 | ≈ 1,197 | ≈ 5 |
- Peak Orders = Avg Orders × Peak Multiplier (or direct peak orders).
- Tickets from Orders = Peak Orders × (Contact Rate ÷ 100).
- Base Tickets = Tickets from Orders + Manual Tickets.
- Adjusted Tickets = Base Tickets × (1 + Repeat% ÷ 100) × (1 − Deflection% ÷ 100).
- Tickets per Hour = Adjusted Tickets ÷ Peak Window Hours.
- Weighted AHT = Σ(Channel Mix% × Channel AHT) ÷ 100.
- Productive Minutes per Agent = Shift Hours × 60 × (Utilization ÷ 100).
- Agents Required = ceil((Adjusted Tickets × Weighted AHT) ÷ Productive Minutes per Agent).
- Hourly Backlog = max(0, prior backlog + hourly demand − hourly capacity).
- Wait Estimate = backlog ÷ capacity per hour.
- Enter average daily orders and your expected peak multiplier.
- Set contact, repeat contact, and deflection rates using past data.
- Choose a realistic peak window (hours when demand concentrates).
- Add manual tickets for payment, account, and pre-sales questions.
- Set staffing, shift length, and utilization to reflect your schedule.
- Open advanced options to adjust channel mix and handle times.
- Click Calculate to review tickets, backlog, and required agents.
- Download CSV for analysis or PDF for sharing scenarios.
Peak order lift and ticket conversion
Peak demand starts with order volume. If an average day runs 2,500 orders and the peak multiplier is 2.5, the calculator models 6,250 peak orders. Ticket creation then follows the contact rate. Many ecommerce programs see 1.5% to 3.5% contacts per order during promotions, driven by delivery, payment, and address changes. A 2.2% rate on 6,250 orders produces about 138 order‑linked tickets.
Repeat contacts and deflection impact
Surges rarely stay one and done. Follow‑ups, escalations, and duplicate contacts increase workload. The repeat contact factor typically ranges from 5% to 20% when response times rise. Self‑service and automation reduce the lift. Deflection of 10% to 25% is common when order‑status pages, proactive emails, and chat bots are tuned for peak. In the sample scenario, 12% repeats and 15% deflection convert a base volume into a realistic adjusted ticket total.
Channel mix changes handle time
Average handle time is different by channel, so the calculator uses a weighted AHT. Email often runs 10–14 minutes, chat 6–10 minutes, and phone 14–22 minutes, depending on policy complexity. A mix of 50% email, 30% chat, and 20% phone with AHTs of 12, 8, and 18 minutes yields a weighted AHT near 11.6 minutes. Lowering phone share or improving macros can increase capacity.
Utilization and capacity planning
Capacity is productive minutes, not paid minutes. Utilization captures breaks, coaching, after‑call work, and handoffs. Many teams plan 60% to 75% utilization for stability; pushing above 80% risks quality drops. With 14 agents, 8‑hour shifts, and 70% utilization, each agent contributes 336 productive minutes. Dividing productive minutes by weighted AHT converts staffing into tickets processed, then into tickets per hour for the peak window.
Backlog risk and response targets
The hourly simulation assumes tickets arrive evenly across the peak window. It compares hourly demand to hourly capacity and carries any difference forward as backlog. Peak backlog is the highest queue size; peak wait is backlog divided by hourly capacity. If demand exceeds capacity for several hours, backlog and waits grow quickly, signaling a need for more agents, higher deflection, or shorter AHT. Use the export files to compare scenarios and set staffing buffers.
FAQs
What does peak window hours represent?
It is the time span when ticket arrivals are concentrated, such as the first 12 hours of a flash sale. The calculator spreads demand evenly across this window to estimate backlog and wait risk.
How should I estimate contact rate?
Use historic tickets divided by orders for similar promotions. Start with 1.5%–3.5% for many ecommerce stores, then refine by category, shipping promises, and payment failure rates.
Why include repeat contacts?
When queues grow, customers often follow up through new tickets or channel switching. The repeat factor approximates that extra load so staffing plans reflect real peak behavior.
How is weighted AHT calculated?
The tool normalizes your channel mix to 100%, then computes weighted AHT as the sum of mix percentage times each channel’s handle time. This produces one blended minutes-per-ticket value.
What utilization should I use?
Plan utilization as productive time after breaks, meetings, and admin work. Many teams target 60%–75% for quality. Higher values raise capacity but can be unrealistic during outages or escalations.
What actions reduce peak backlog fastest?
Increase deflection with order-status links and proactive messaging, reduce AHT with macros and clear policies, or add staffed capacity. Run scenarios and compare CSV exports to pick the most cost-effective mix.