Support Team Productivity Benchmarks

Tickets per agent per day: the core benchmark

The most commonly used productivity benchmark for support teams is tickets resolved per agent per day. It's imperfect — it doesn't weight by ticket complexity — but it's the most practical single number for capacity planning and benchmarking.

For ecommerce support, the typical range is 40–120 tickets per agent per day, with significant variation based on channel (email vs. chat), ticket mix (simple vs. complex), and tooling. Strong performers with good tooling and a high share of simple tickets reach 100–130+. Teams with poor tooling, complex tickets, or phone-heavy volume may be at 30–50.

Productivity benchmarks by channel

Agents handling live chat can often manage 2–4 concurrent conversations, which is why chat throughput is higher. Most agents max out at 3 concurrent chats before quality degrades. Email throughput is largely a function of average handle time — reduce AHT and tickets-per-day rises proportionally.

What affects agent productivity

Beyond channel mix, several factors consistently predict whether agents are at the high or low end of the productivity range:

• Template and knowledge base quality — agents with rich, well-organized templates handle repetitive tickets in a fraction of the time. A comprehensive library of 20–30 templates can lift throughput 30–50%.
• System integration — agents who can see order data, customer history, and conversation history in a single view without switching tools spend significantly less time per ticket.
• Queue organization — well-tagged, routed queues mean agents aren't spending time triaging or context-switching across ticket types mid-workflow.
• Ticket complexity mix — agents handling mostly WISMO and basic returns will have much higher throughput than agents handling disputes and complex complaints. Routing complexity appropriately to senior agents protects the productivity of the full team.
• Experience and training — new agents typically handle 60–70% of the volume of experienced agents in their first 30 days; the gap closes with good onboarding and structured coaching.
• Agent autonomy — agents who need manager approval for every small action spend significant time waiting. Empowering agents to act within defined limits (refunds up to $X, returns within policy, credits up to $Y) lifts throughput meaningfully.

How AI changes team productivity

The 'rightsized' row shows how stores often restructure: same or slightly higher total contacts covered with a smaller human team, because AI has taken over the automatable majority. The 2-agent team in the example handles more total contacts than the 3-agent team without AI — while the agents focus on genuinely complex and high-value interactions.

Team sizing and scaling with AI

This framework consistently shows that mid-size Shopify stores (2,000–8,000 monthly contacts) can be well-served by a team of 1–3 human agents + AI, rather than the 4–8 agents the volume would require without automation. The savings in headcount are the primary driver of AI support ROI at this scale.

1. 1Calculate your total monthly contact volume (all channels).
2. 2Estimate your target deflection rate with AI — use 40–55% as a realistic starting point for most ecommerce stores.
3. 3The residual human volume = total contacts × (1 − deflection rate).
4. 4Divide residual human volume by your expected tickets-per-agent-per-day, then by ~20 working days, to get the required agent headcount.
5. 5Add a buffer for complexity: 10–15% more capacity for the harder tickets that AI escalates.
6. 6Example: 4,000 monthly contacts × 50% deflection = 2,000 human tickets. 2,000 ÷ 20 days = 100 tickets/day. At 80 tickets/agent/day, you need 1.25 agents — so 1 full-time plus part-time, or 2 agents with bandwidth for growth.