Skip to content
← Back to glossary

Erlang Calculator

Leaders apply Erlang Calculator to manage staffing and scheduling with clearer ownership, faster adjustments, and stronger control. It converts forecast and policy expectations into daily execution using data-driven workflows and clear ownership. Effective execution increases service reliability and efficiency and helps teams make consistent decisions. Repeated review and adjustment help maintain fit between plans and real operating conditions. The result is steadier day-to-day execution with clearer context for frontline coaching. Erlang Calculator becomes more scalable when organizations document decision rights and connect frontline signals to planning updates. Linking it to Workforce Apps and Venue-Based Technician Allocation gives managers clearer context for faster tradeoff decisions. The main advantage is more reliable execution with lower variance between shifts.

Impact on Operations

An Erlang calculator helps forecast staffing needs in contact centers based on call volume, handle time, and service level targets. It prevents over- or understaffing by quantifying how many agents are required.

Accurate Erlang modeling reduces abandonment and improves customer experience.

How It Builds Value

Planners input expected volume and average handle time, then test service level targets. The calculator outputs required staffing by interval.

It is most effective when inputs are validated regularly and shrinkage is factored in.

Frequent Mistakes to Avoid

Using outdated handle time data leads to poor staffing plans. For Erlang Calculator, another issue is ignoring seasonality or channel mix changes.

Essential Metrics

  • Service level and abandonment rate.
  • Forecast accuracy of call volume.
  • Average speed of answer trends.
  • Staffing variance versus plan.

Erlang outputs should be reviewed alongside shrinkage assumptions to avoid overconfidence.

Use separate models for different channels if handle times vary significantly.

Document inputs each cycle to track why staffing needs change.

Scenario testing helps planners see the tradeoff between service level targets and staffing cost.

Pairing Erlang outputs with real-time adherence data improves decisions.

Use historical call patterns to validate model outputs.

Comparing Erlang outputs with actual staffing outcomes builds trust in the model.

Small adjustments to handle time assumptions can have large staffing effects.

Always document service level targets used in the calculation.

When volumes are volatile, use multiple scenarios rather than a single forecast.

Track deviation between planned and actual staffing to refine inputs.

Erlang models should be reviewed when handle time changes significantly.

How Erlang Calculator Works With Workforce Apps

For adjacent concepts, see Workforce Apps and Venue-Based Technician Allocation.

Frequently asked questions

What is an Erlang calculator?
It is a staffing tool that converts forecast contact volume, average handle time and a service level target into the number of agents required per interval. It exists because staffing does not scale linearly with volume: queueing means the last few seconds of answer speed cost disproportionately more agents than the first.
What inputs does it need?
Expected contact volume for the interval, average handle time, the service level target expressed as a percentage answered within a number of seconds, and the interval length. Shrinkage is applied after the calculation to turn required agents on the phone into rostered heads.
Why does the output need shrinkage added?
Because the model returns the number of people who must be handling contacts, not the number who must be rostered. Breaks, training, meetings, absence and other paid non-productive time sit on top. Treating the raw output as a headcount is the most common way an Erlang-based plan comes up short.
Should the same model be used for every channel?
No. Use separate models where handle times differ significantly, because voice, chat and email behave differently in a queue. Chat in particular allows concurrency, which the basic voice assumption does not capture.
What are the common mistakes?
Using outdated handle-time data, ignoring seasonality or a change in channel mix, and treating one forecast as certain when volumes are volatile. Small changes to the handle-time assumption produce large staffing effects, so the inputs deserve more review than the model does.
How do you know whether to trust the output?
Compare planned against actual staffing over time and track the deviation, alongside service level, abandonment, answer speed and forecast accuracy. Documenting the service level target and inputs used in each cycle is what makes a later variance explainable rather than mysterious.

Put this into practice

See how Soon handles erlang calculator in your shift scheduling workflow.

Start Free Trial