Free tool

Support staffing calculator

Estimate how many support agents you need in 30 seconds based on ticket volume, handle time, and growth assumptions.

Support staffing decisions without guesswork

This support staffing calculator helps teams make faster capacity decisions with clear inputs. Instead of planning by intuition, you combine ticket volume, handle time, occupancy, and growth in one practical model.

Why staffing issues are often detected too late

Many teams rely on monthly averages or intuition. That delays action until queues and SLA pressure are already visible.

Backlog builds before KPI alerts become obvious.
Ad-hoc scheduling does not fix structural mismatch.
Without shared math, staffing decisions stay subjective.

Which inputs drive real capacity

Volume alone is not enough. Handle time, productive hours, and occupancy determine how much work the team can truly absorb.

Tickets per working day as baseline load.
Average handle time as effort intensity.
Occupancy as practical availability constraint.

Use growth buffer to absorb demand spikes

Growth assumptions prevent planning drift during campaigns, seasonal demand, or logistics disruption.

Do not plan only against current month averages.
Reserve capacity for unexpected volume clusters.
Align staffing assumptions with your commercial calendar.

Turn calculation output into staffing action

The capacity gap helps you decide when to hire, rebalance shifts, or improve process throughput.

Use gap as signal for hiring or shift redesign.
Use surplus as room for quality and backlog work.
Track impact on FRT, resolution time, and backlog trend.

Your support inputs

Tickets per month Average handle time (min) Working days per month Productive hours per agent/day Occupancy target (%) Expected next-month growth (%) Current number of agents

Core metrics

Tickets per working day: 0
Daily workload (hours): 0

How the formula works

1) Tickets/day = monthly tickets / working days
2) Workload hours/day = tickets/day × handle time / 60
3) Effective agent hours = productive hours × occupancy
4) Required agents = workload hours / effective agent hours
5) Recommendation = required agents × (1 + growth)

How to use the staffing calculator in planning routines

1. Input realistic monthly operating data

Use recent ticket counts and current handle-time averages.
2. Validate occupancy assumptions

Choose a target that reflects meetings, escalations, and internal work.
3. Compare recommendation with current team size

Use the capacity gap as objective planning input with leads and operations.
4. Recalculate when volume profile changes

Repeat the model regularly to avoid hidden queue growth.

Checklist for reliable staffing planning

Input data reflects a recent support period.
Handle time and productive hours are realistic.
Occupancy assumption matches team reality.
Growth buffer is included for expected demand spikes.
Output is compared against current agent count.
Action plan (hiring, shifts, or process) is documented.

Supporting guides

Support capacity planning guide WISMO and shipping updates playbook Return and refund template guide Complaint recovery template guide

Frequently asked questions

How does this calculator estimate required staffing?

It converts ticket volume and average handle time into workload hours, adjusts by occupancy, then applies a growth buffer.

What is a realistic occupancy target for support teams?

Most teams plan around 70% to 80% productive occupancy. Lower targets leave more room for spikes and escalations.

Does this replace full workforce management software?

No. This tool is for quick planning. Interval-level forecasting and scheduling still require dedicated WFM tooling.

How often should we recalculate staffing capacity?

At least weekly, or immediately after volume shifts. During peak periods, daily checks help prevent hidden understaffing.

Should part-time and full-time agents be modeled separately?

Yes. Planning by effective hours per day gives a more realistic view of true team capacity.

How is this different from an Erlang C calculator?

Erlang C models phone arrivals as random calls in a queue and answers a question in seconds: how many people keep waiting time acceptable. This calculator models ticket-based support, where work arrives as items with a handle time and lives in a backlog until an owner resolves it. If your team answers phone queues all day, use Erlang; if it answers email, chat and forms, a ticket-based model reflects the day better. The two do not exclude each other: mixed teams run both and compare the outcomes.

How do you staff for chat and email instead of phone?

Per channel, because the work differs. Email is one item per thread with a measurable handle time, so the ticket-based formula applies directly. Chat runs concurrently: one agent can hold multiple conversations, so divide conversations by the concurrency you realistically keep before dividing by handle time. Then plan the channels separately and combine only the hours, not the conversation counts.