Skip to content
OmniSmart
groups Service capacity

How many people does your operation need to serve without exceeding capacity?

Convert interactions and average handle time into workload. Adjust channel, concurrency, occupancy, unavailability, and peaks to compare current team with estimated need.

visibility Open resultcalculate Formula explaineddevices Voice and digital channels
Volume, shift, and productivity

Describe monthly capacity

Start with the main channel or use weighted averages from a queue with similar behavior.

support_agent
The selection suggests concurrency; you can change the value.
contacts
people
min
Average active handling time.
per person
days
h
%
Portion of available time occupied by interactions.
%
Training, meetings, breaks, absences, and auxiliary tasks.
×
1.25 adds 25% protection over average load.
min
Registered in the diagnosis; does not replace an intraday queue model.
infoThis calculation sizes monthly capacity. For interval scheduling and formal service level, use arrival data every 15 or 30 minutes and a queue model.

Notice: The result is a monthly capacity estimate, not a work schedule or SLA guarantee. Intraday volumes, skills, legislation, actual breaks, absenteeism, and queue distribution must be validated in the project.

architecture Capacity model

The calculation separates load, availability, and peak protection

This allows you to understand which assumption is driving headcount needs and simulate operational changes without hiding the formula.

1

Convert volume into hours

Interactions × AHT, divided by concurrency, yields the monthly active load.

2

Adjust real capacity

The shift is reduced by breaks and unavailability, and then by the desired productive occupancy.

3

Protect against peaks

The peak factor adds buffer to average volume. An hourly analysis is still needed for formal scheduling.

Questions about sizing

What concurrency should I use?expand_more
Use 1 for voice. For messaging, measure how many conversations an agent can maintain with quality. The more complex or sensitive the interaction, the lower the sustainable concurrency tends to be.
What counts as unavailability?expand_more
Breaks, meetings, training, absences, feedback, and tasks that remove the person from the queue. Use actual schedule data whenever available.
Why limit occupancy?expand_more
Planning 100% of available time as service leaves no room for variation, after-call work, transition, and waiting. The appropriate percentage depends on the channel and service level.
When to use Erlang C?expand_more
For voice or real-time queues when the operation needs to estimate waiting probability per interval. You will need to provide arrivals and AHT in smaller blocks, plus the service level target.