Calculators

Call center staffing calculator

Work out how many agents you need on the phones to hit a service level target, and how many to schedule once breaks, training, and absence are counted. It uses Erlang C, the standard formula for inbound call queues.

Your numbers

These are example numbers. Replace them with your own.

calls

Calls offered in one interval, forecast or from your phone system’s interval report.

min

Usually 15, 30, or 60 minutes.

sec

Talk, hold, and after-call work, per call.

%

The share of calls you want answered within the target time.

sec

As in “80% of calls answered in 20 seconds.”

%

The most of their logged-in time you want agents busy on calls. Use 100 for no cap.

%

Paid time when agents can’t take calls, such as breaks, meetings, training, and absence.

Result

Agents needed on the phones

14

Agents to schedule, after shrinkage
20
Service level
88.8%
Average speed of answer
7.8 sec
Occupancy
71.4%
Calls answered without waiting
82.6%
Traffic (Erlangs)
10.00
Service level by number of agents
AgentsService levelAvg. speed of answerOccupancy
1264.0%40.4 sec83.3%
1379.6%17.1 sec76.9%
1488.8%7.8 sec71.4%
1594.1%3.7 sec66.7%
1697.1%1.7 sec62.5%
1798.6%0.8 sec58.8%

These results are for the example numbers. Turn on JavaScript to use your own.

How the calculator works

Traffic, A = calls per interval × average handle time ÷ interval length in seconds

Chance a call waits, Pw = X ÷ (Y + X), where X = AN ÷ N! × N ÷ (N − A), and Y is the sum of Ak ÷ k! for k from 0 to N − 1

Service level = 1 − Pw × exp(−(N − A) × target answer time ÷ average handle time)

Average speed of answer = Pw × average handle time ÷ (N − A)

Occupancy = A ÷ N

Agents to schedule = N ÷ (1 − shrinkage), rounded up

The calculator turns your call volume and handle time into traffic, measured in Erlangs. One Erlang is one hour of calls arriving every hour, so it’s the number of agents you’d need if calls lined up end to end with no gaps.

Calls don’t line up like that, so you need more agents than Erlangs. The calculator tries agent counts (N) from just above the traffic upward and stops at the first one that meets your service level target without going over your occupancy cap. Erlang C gives the chance a caller waits at all, and the service level formula turns that into the share answered within your target time.

With the example values, 100 calls in 30 minutes at 3 minutes each is 10 Erlangs. Thirteen agents answer 79.6% of calls within 20 seconds, just short of the target. Fourteen reach 88.8%, with an average speed of answer of 7.8 seconds. With 30% shrinkage, keeping 14 agents on the phones means scheduling 20.

The factorials in Erlang C get too large for a computer to hold beyond about 170 agents, so the calculator works it out through the Erlang B recursion instead. It’s the same formula rearranged, and it stays exact for thousands of agents.

Assumptions

  • Calls arrive at random, at a steady rate through the interval.
  • Handle times vary at random around the average (an exponential distribution).
  • No caller hangs up while waiting. Real queues lose some callers, so Erlang C tends to overstate the agents needed when many callers abandon.
  • Every agent can take every call, and calls are answered in the order they arrive.
  • Each interval is calculated on its own. Run each interval of the day to build a schedule.

Sources

  • A. K. Erlang published the formula in 1917. Wikipedia’s Erlang article sets out the Erlang C formula and the service level and speed of answer that follow from it. Erlang (unit) on Wikipedia
  • The example values, and the results for 13 and 14 agents, match Call Centre Helper’s worked Erlang C example. Read the worked example

Cover the peak without hiring for it

Erlang C tells you how many people a peak needs. Simple answers the calls above your staffing line on the first ring, on the phone system you already own. At Omaha Steaks, with Simple answering, abandonment fell from 16% to 2%, and planned seasonal hiring from 5,000 people to 692.

Read the Omaha Steaks story

Questions buyers ask

What is Erlang C?

Erlang C is a queueing formula, published by A. K. Erlang in 1917, that gives the chance a caller has to wait, given the traffic offered and the number of agents. Contact centers use it to work out how many agents they need to hit a service level target.

What service level should I target?

It depends on what the calls are worth. “80% of calls answered in 20 seconds” is a common way to state a target, and it’s the example here. A sales line where every abandoned call is a lost order may justify a tighter target than a line that handles routine questions, so set it from your own abandonment and conversion data.

What is shrinkage?

Shrinkage is the share of paid time when agents can’t take calls, such as breaks, lunch, meetings, coaching, training, sick days, and vacation. With 30% shrinkage, you need to schedule 10 agents to have 7 on the phones.

Why does the calculator cap occupancy?

Occupancy is the share of logged-in time agents spend on calls. With fewer agents it climbs toward 100%, leaving no time between calls, which is hard to sustain for a full shift. The cap adds agents until occupancy is at or below the limit you set, even when the service level target is already met.

Is Erlang C accurate for my contact center?

It’s the standard starting point for inbound voice queues. It assumes callers never hang up and every agent takes every type of call, so it can overstate staff when abandonment is high, and it doesn’t model skills-based routing. Workforce management tools use variants such as Erlang A, or simulation, for those cases.

Answer every call, even at peak

Tell us how your customers buy. We’ll show you where Simple can start winning revenue.