Tickets per order: the core benchmark
The most useful normalization for ecommerce support volume is tickets per 100 orders (or per 1,000, depending on scale). This metric lets you compare your support intensity across time periods and against other stores regardless of absolute volume.
Industry-typical ranges vary by category, price point, and how well a store's post-purchase experience is set up. High-complexity products (electronics, apparel with sizing variation) generate more tickets per order than low-complexity consumables. Stores with excellent proactive notifications generate fewer WISMO tickets.
Most ecommerce stores generate 3–8 support tickets per 100 orders under normal conditions. That translates to 30–80 tickets per 1,000 orders. Strong performers with good self-service and proactive notifications land at 2–4 tickets per 100 orders. Stores with poor post-purchase communication or complex products may see 10–15+ tickets per 100 orders.
Ticket volume benchmarks by store size
Smaller stores tend to have a higher ratio of tickets to orders because they rely more on manual post-purchase communication and have less automation. As stores scale, self-service content and order notification systems reduce the per-order contact rate — but only if those investments are made.
| Store tier (monthly orders) | Typical monthly tickets | Tickets per 100 orders |
|---|---|---|
| Under 200 orders/month | 50–200 | 8–15% |
| 200–500 orders/month | 100–400 | 5–10% |
| 500–1,500 orders/month | 300–900 | 4–8% |
| 1,500–5,000 orders/month | 700–3,000 | 3–7% |
| 5,000–15,000 orders/month | 2,000–8,000 | 3–6% |
| 15,000+ orders/month | 5,000–20,000+ | 2–5% (scale efficiencies) |
Ticket volume by type
WISMO alone typically accounts for the largest share of volume. For many stores it is 40%+ of all contacts — which means automating order status lookup has a bigger impact on total ticket volume than anything else. A store handling 3,000 monthly tickets where 40% are WISMO has 1,200 order-status contacts every month, most of which are answerable with a simple data lookup.
| Ticket type | Typical % of volume | Notes |
|---|---|---|
| Order status / WISMO | 25–50% | Largest single category; highly automatable |
| Returns and exchanges | 15–25% | Spikes after peaks; partially automatable |
| Shipping issues / delays / lost packages | 8–15% | Spikes during peak season and carrier disruptions |
| Product questions (pre/post purchase) | 10–20% | Varies heavily by product complexity |
| Billing, payments, refunds | 5–12% | Often requires action; some automatable |
| Account, login, subscription | 5–10% | Higher for subscription brands |
| Other / complaints / misc | 5–10% | The long tail |
Seasonal patterns in ticket volume
Ecommerce support volume is not flat across the year. Predictable spikes occur around major retail events, and stores that plan staffing and automation around these spikes avoid the reactive scramble that degrades support quality during the periods when customer expectations are highest.
The two largest spikes are Black Friday / Cyber Monday (BFCM) and the holiday shipping season (mid-December). In both cases, order volume rises and customer anxiety about delivery timing rises even faster — generating disproportionate WISMO and shipping-issue tickets relative to order count.
| Period | Typical volume vs. baseline | Primary drivers |
|---|---|---|
| BFCM week | 2–4x baseline | Order surge, shipping anxiety, return policy questions |
| Dec 10–22 (holiday shipping) | 2–3x baseline | Delivery deadline anxiety, lost/delayed packages |
| Dec 26 – Jan 10 (returns season) | 1.5–2.5x baseline | Gift returns, exchanges, refund requests |
| Valentine's Day, Mother's Day (for relevant stores) | 1.5–2x baseline | Gifting-related delivery questions |
| Summer (most categories) | 0.7–0.9x baseline | Slower than average |
A store with 1,500 monthly tickets at baseline should plan for 3,000–6,000 tickets during BFCM week and the holiday shipping period. If your AI deflection rate is 50%, AI absorbs most of the spike without additional headcount. If you're running all-human, plan 2–4x your normal staffing coverage.
How to reduce your ticket volume
Ticket volume reduction is different from ticket deflection. Deflection means a ticket arrives but gets resolved without a human. Volume reduction means the contact never happens because the customer's question was already answered — proactively. Both matter, but volume reduction is lower-cost because you're not processing the contact at all.
- 1Send proactive order notifications at every key stage: confirmation, fulfillment, shipping with tracking link, out for delivery, delivered. Proactive shipping updates reduce WISMO tickets by 30–50%.
- 2Build a comprehensive, searchable FAQ that covers your top 20 questions. A customer who finds the answer in 30 seconds doesn't open a ticket.
- 3Add tracking to your order confirmation and account pages so customers can self-serve without contacting support.
- 4Make your return policy visible, specific, and unambiguous. Customers who aren't sure if they qualify for a return contact support to ask; customers who know they qualify initiate the return directly.
- 5Use post-purchase email sequences to proactively answer common questions (sizing, care instructions, delivery windows) for your category.
- 6Review your top 10 ticket types monthly and ask: 'What would prevent this question from being asked?' That's your volume reduction roadmap.
Key takeaways
- Most ecommerce stores generate 3–8 support tickets per 100 orders; strong performers with good automation hit 2–4.
- WISMO (order status) is typically 25–50% of total ticket volume — the single highest-ROI category to automate.
- Peak season (BFCM, holiday shipping) generates 2–4x baseline ticket volume — plan automation and staffing accordingly.
- Volume reduction (preventing contacts) is higher-ROI than deflection alone — proactive notifications eliminate WISMO before it starts.
- Ticket volume per order tends to fall as stores invest in self-service, proactive notifications, and AI automation.