WFM Helper
Back to Tools

Service Level Calculator

The Erlang C question in reverse: given the agents you actually have on the floor, what service level, average speed of answer and occupancy will this interval deliver?

Live · updates as you type

Interval inputs

Model a single interval at a time.

agents

Bodies on the phone, after shrinkage

calls
sec
min
sec

The 20 in an 80/20 service level target

Achieved service level
84.2% in 20s

Share of contacts answered within the target answer time.

Average speed of answer
11sec

Mean wait across all contacts, including those answered immediately.

Traffic intensity
33.33erlangs
Occupancy
85.5%
Chance of queueing
25.4%
You are above 80%. An 80/20 target needs 39 agents, so you have 0 agents of headroom against forecast error.

Save or share these results

Take a snapshot of the exact inputs and outputs on screen.

Email me these results

Get the full Excel/VBA version

Want the full Excel/VBA version with live formulas, RTM tracking, and dashboards? Pay what you think it's worth.

Suggested ₹99 · pay what it's worth to you

Results are estimates for planning purposes only and should not replace professional workforce management judgment.

Service level is the percentage of contacts answered within a stated number of seconds , the familiar "80/20" means 80% of calls answered within 20 seconds. Most staffing tools ask for the target and give you agents. This calculator runs the same maths backwards: you supply the agents, and it tells you what the customer experience will look like.

The maths behind it

First it converts demand into workload, measured in erlangs: traffic intensity = (calls × AHT) ÷ interval length in seconds. With 250 calls at 240 seconds AHT in a 30-minute interval, that is 33.33 erlangs, meaning you need at least 34 agents just to keep up on average, before any allowance for randomness.

The Erlang C formula then gives the probability that an arriving contact has to wait at all, and service level follows from it:

  • SL = 1 − P(wait) × e^(−(agents − erlangs) × target answer time ÷ AHT)
  • ASA = P(wait) × AHT ÷ (agents − erlangs)

Why extra agents help so much at the margin

Service level does not improve linearly. Near the point where agents barely cover the workload, one extra agent can move service level by twenty points or more. Once you are comfortably staffed, an extra agent may add less than one point. This is why chasing a 98% target costs far more than reaching 80%, and why small understaffing in a single interval causes a disproportionate collapse in the customer experience.

Assumptions to keep in mind

  • Erlang C assumes no abandonment, real service level is usually slightly better than the model predicts.
  • It assumes contacts arrive randomly and agents are interchangeable; heavily skill-routed queues need separate modelling per skill.
  • It assumes a steady state within the interval, so use 15 or 30 minute intervals rather than modelling a whole day at once.
  • Enter agents actually on the phone. Apply shrinkage before this step, not after.

More tools

See all tools