Call Centre Erlang Calculator

What is a Call Centre Erlang Calculator?

A Call Centre Erlang Calculator is a forecasting tool used to estimate how many agents are needed to answer customer contacts within a target timeframe. It is most commonly based on the Erlang C formula, which is widely used across contact centres to model queueing behaviour and staffing requirements.

It takes a handful of inputs — usually contact volume, average handling time, interval length and target service level — and converts them into a staffing requirement.

That means instead of guessing whether 12 agents is enough, or debating whether “the phones feel busy”, you can use a structured model to estimate the headcount required to meet your operational targets.

Why call centres use Erlang calculators

Customer demand does not arrive in neat, evenly spaced intervals. Calls come in randomly. Some periods are quiet, others spike, and handling times vary from one interaction to the next. That makes workforce planning difficult — especially when service levels, customer patience and labour costs are all under pressure.

This is why Erlang remains so important. A good Erlang calculator allows you to model the relationship between:

• forecast contact demand
• average handling time
• service level targets
• occupancy
• speed of answer
• the number of agents required

It is not just useful for day-to-day planning. It is also valuable when you need to:

• justify staffing budgets
• model the impact of higher call volumes
• test the effect of longer AHT
• understand the operational impact of lower staffing levels
• evaluate how shrinkage affects rostered headcount
• support business cases for better systems, processes or training

In short, an Erlang calculator helps connect customer demand to workforce reality.

What data do you need to use an Erlang calculator?

Most Erlang C calculators rely on a small set of core inputs. These are usually available from your phone system, WFM resources or reporting suite.

If your data quality is poor, your staffing outputs will be poor too. Erlang is powerful, but it cannot rescue bad forecasts, inflated AHT assumptions or unrealistic service targets.

What is the difference between Erlang A, Erlang B and Erlang C?

There are three common Erlang models, and they are used for different operational purposes.

When people search for an erlang calculator, they are usually referring to an Erlang C calculator.

How Erlang C works in a call centre

Erlang C models the probability that a contact will have to wait for an available agent based on traffic load and staffing levels. It then uses that to estimate expected service level, average speed of answer and required staffing.

You do not need to manually calculate the formula yourself. But you do need to understand the commercial logic behind it.

1. Your forecast estimates how many calls will arrive in a defined interval.
2. Your AHT estimate converts that demand into workload.
3. The Erlang C model tests how many agents are needed to absorb that workload while achieving a target service level.
4. Shrinkage is then applied to convert “agents required on the phones” into rostered headcount.

This is what makes an Erlang calculator so useful. It turns a demand forecast into an operational staffing plan.

Erlang calculator example: why AHT matters so much

One of the biggest benefits of using an Erlang calculator is that it helps leaders understand how sensitive service levels are to small changes in key inputs.

For example, if call volumes and agent numbers stay the same, but your average handling time increases, your service level can fall sharply. That means a new product issue, more complex queries, longer wrap time, inexperienced agents or poor systems can all create a significant staffing gap — even if demand itself has not changed.

That is why Erlang is not just a staffing calculator. It is also a scenario modelling tool. It helps you explain the operational consequences of changes in demand, productivity, process design and customer behaviour.

A brief history of Erlang

Mr Agner Krarup Erlang

The name Erlang comes from Agner Krarup Erlang, a Danish mathematician whose work in the early 1900s laid the foundation for modern queueing theory.

At the time, telephone systems needed a way to estimate how many operators and circuits were required to handle demand efficiently. His work solved that problem — and more than a century later, the same principles still underpin many workforce management and forecasting tools used in contact centres today.

That staying power tells you something important: even in modern omnichannel environments, the core challenge of matching random demand to finite capacity has not gone away.

What are the limitations of Erlang C?

As useful as Erlang C is, it is not magic. It makes assumptions that do not always hold true in real-world operations.

Typical limitations include:

• it assumes callers will wait rather than abandon
• it assumes contacts arrive in a broadly random and stable pattern
• it assumes all agents are equally skilled and can handle all work types
• it assumes staffing is continuously available within the interval
• it is less reliable in very low volume environments
• it is not well suited to complex skills-based routing environments on its own

That does not make Erlang C wrong. It simply means it should be used intelligently, with an understanding of your channel mix, routing design, operating model and data quality.

Common mistakes when using an Erlang calculator

Many operational leaders use the formula correctly but still end up with poor decisions because the assumptions going into the model are weak.

• Ignoring shrinkage: calculating agents on the phones is not the same as calculating the rostered headcount you need.
• Using blended AHT badly: if your handling times vary heavily by call type, a single average can distort the result.
• Setting unrealistic service levels: targeting premium responsiveness without funding the required labour will create chronic failure.
• Using hourly averages for volatile demand: large spikes inside the hour can cause service collapse even when the hourly average looks manageable.
• Treating Erlang as perfect: it is a model, not a guarantee.
• Ignoring occupancy: service level may look acceptable while agent workload becomes operationally unsustainable.

The strongest planners use Erlang as part of a wider planning discipline, not as a standalone answer.

When Erlang is not enough on its own

There are situations where an Erlang calculator is helpful but not sufficient on its own.

Examples include:

• very low volume operations
• highly variable or lumpy arrival patterns
• multi-skill or specialist routing environments
• blended teams handling calls, email, chat and back-office work
• operations where schedule adherence is poor or intraday volatility is high

In these environments, you often need more advanced workload modelling, scenario planning or workforce management tools.

Frequently asked questions about Erlang calculators