Support Staffing Workload Forecast
Calculate support staffing needs based on ticket volume and utilization. Enter values for instant results with step-by-step formulas.
Frequently Asked Questions
How do I calculate support staffing requirements?
Formula: Required agents = Total handle time / (Work hours × Utilization target). Example: 200 tickets/day, 15 min handle time = 3,000 minutes = 50 hours. Agents work 8 hours at 75% utilization = 6 productive hours. Required: 50 / 6 = 8.3 → 9 agents. Utilization target (70-80%) accounts for: breaks, meetings, training, buffer for spikes. Don't target 100%—no capacity for volume increases or complex tickets. Erlang C formula provides more precise queueing model for real-time support (chat, phone).
What is a good utilization target for support teams?
Optimal: 70-80% utilization. Below 70%: Overstaffed (high labor cost relative to volume). Above 80%: Risk of burnout, long queues, quality drops. At 90%+: Critical—any spike causes queue explosion. Why not 100%: (1) Agents need breaks, training, meetings. (2) Ticket volume varies—need buffer for peaks. (3) Complex tickets take longer—averages don't account for variance. (4) Quality degrades under constant pressure. Different channels: Chat (higher utilization OK, ~80%), phone (70-75%), email (can flex to 85% since async).
How do I forecast ticket volume growth?
Methods: (1) Historical trend: Plot last 12 months, calculate growth rate. If 10% MoM growth, forecast next month = current × 1.1. (2) Customer correlation: Tickets per customer is stable (~0.5-2/month for SaaS). Forecast = Projected customers × Tickets per customer. (3) Product launches: Major releases spike volume 2-3x for 2-4 weeks. Plan temporary staffing. (4) Seasonality: Retail spikes Q4, tax software spikes April. Use year-over-year comparison. Combine methods: Base forecast (historical) + adjustments (launches, seasonality). Add 10-20% buffer for unknowns.
Should I use Erlang C for staffing calculations?
Erlang C is queuing theory formula for real-time support (phone, chat) where customers wait in queue. Calculates: Probability of waiting, expected wait time, service level. Use Erlang C when: (1) Real-time channel (phone, live chat). (2) Need specific service level (e.g., 80% answered in 60 seconds). (3) Volume is high enough for statistical modeling (>100 interactions/day). Simpler approach OK when: (1) Async channel (email, tickets). (2) Lower volume. (3) Planning at daily/weekly level, not hourly. Most support tools (Zendesk, Intercom) have built-in Erlang calculators. For email/ticket support, simple handle time / available hours calculation is sufficient.
What metrics should I track for support staffing?
Key metrics: (1) Tickets per agent per day: Productivity measure. Benchmark: 20-40 for email, 30-50 for chat. (2) First response time: How fast customers get initial reply. Target: <1 hour email, <1 min chat. (3) Resolution time: Total time to close ticket. Target: Varies by complexity. (4) CSAT/NPS: Customer satisfaction. Target: >90% CSAT, >50 NPS. (5) Utilization: % of available time spent on tickets. Target: 70-80%. (6) Backlog: Unresolved tickets. Should trend down or stay flat. (7) Escalation rate: % needing senior help. High rate = training gap. Track weekly, trend monthly. Compare to industry benchmarks.
How do I staff for 24/7 support?
Coverage model: Minimum 5 agents per shift for true 24/7 (accounts for PTO, sick, training). 3 shifts × 5 agents = 15 agents minimum. Reality often needs 18-20 for buffer. Alternatives: (1) Follow-the-sun: Teams in different time zones (US day → EU evening → Asia night). Each team works normal hours. (2) On-call: Skeleton crew at night, on-call escalation for urgent. (3) Outsourcing: BPO handles off-hours, in-house handles business hours. (4) Self-service priority: Invest in help center so customers can self-serve 24/7, humans for complex only. Cost: 24/7 is ~3x cost of business-hours-only support. Justify with: Global customer base, real-time product (uptime-critical), premium support tier.