Free Contact Centre Erlang Calculator

Estimate staffing needs, service level, average speed of answer, occupancy, and scheduled headcount with a premium Erlang C calculator built for contact centre planning. Enter your volume, average handle time, service target, and shrinkage to see how many agents you need.

Calculator Inputs

Calls in interval Total calls expected during the planning interval.

Interval length in minutes Most workforce teams plan in 15 or 30 minute blocks.

Average handle time in seconds Include talk time, hold, and after call work if applicable.

Target answer time in seconds Example: 20 seconds for an 80/20 target.

Target service level percent Percent of calls you want answered inside target answer time.

Maximum occupancy percent Helps prevent overloading agents during busy intervals.

Shrinkage percent Accounts for breaks, meetings, training, absence, and admin time.

Result precision Controls how many decimal places are shown.

Tip: Erlang C assumes delayed calls remain in queue until answered and is best used for inbound voice environments with stable interval forecasting.

Results

Required agents on phones –

Scheduled agents with shrinkage –

Traffic intensity –

Expected service level –

StatusEnter values and click Calculate.

How to use a free contact centre Erlang calculator to plan staffing with confidence

A free contact centre Erlang calculator is one of the most practical tools in workforce management because it turns call volume and handling time into a staffing requirement you can act on. If your team needs to answer more calls inside a service target without overstaffing every interval, Erlang C provides a disciplined queueing model for estimating how many agents must be available. It is widely used in inbound voice planning because it connects operational reality to measurable service outcomes such as service level, average speed of answer, occupancy, and queue delay.

What the Erlang model actually measures

At its core, Erlang C starts with offered load, often called traffic intensity and measured in Erlangs. Offered load is calculated from two simple pieces of information: call arrivals and average handle time. If you expect 240 calls in 30 minutes and each call takes 300 seconds to handle, your workload is 40 Erlangs. That means the equivalent of 40 agents would be busy continuously if there were no variability, no waiting, and no performance target. In the real world, arrivals are uneven, call durations vary, and customers may queue, so you usually need more than the raw Erlang load to meet service expectations.

The model then estimates the probability a caller will have to wait, the percentage of callers answered within a target time, the average speed of answer, and agent occupancy. Those outputs matter because they influence customer experience and employee strain at the same time. A plan with very high occupancy may look efficient on paper, but it can produce long waits during spikes, poor morale, and no recovery time between contacts. That is why experienced planners evaluate Erlang results alongside occupancy caps and shrinkage assumptions rather than focusing on service level alone.

Why contact centres rely on 15 and 30 minute intervals

Queueing performance is highly sensitive to timing. Daily averages can hide severe undercoverage in specific periods. A contact centre that appears properly staffed for a full day can still miss targets badly between 10:00 and 10:30 if demand spikes. That is why serious workforce planning is usually done in short intervals, commonly 15 or 30 minutes. Forecasting by interval lets you convert demand into precise staffing decisions and identify where schedule optimization is needed.

Using a free contact centre Erlang calculator at interval level gives you much more actionable insight than working with daily call totals. You can compare busy periods to quieter periods, determine where split shifts or staggered lunches make sense, and see where intraday management will be most critical. The calculator above is designed for exactly that use case: practical inbound planning, interval by interval.

The key inputs that drive your staffing result

Calls in interval: The expected number of inbound contacts in the selected planning block.
Average handle time: The total time an agent is occupied per call, usually including talk time, hold, and after call work.
Target answer time: The time threshold used in your service goal, such as answering calls within 20 seconds.
Target service level: The percentage of calls you want answered within the target answer time, such as 80 percent.
Maximum occupancy: A control that helps keep agent workload realistic. Many operations avoid planning too close to 100 percent occupancy because it leaves no room for variability.
Shrinkage: The percentage of paid time unavailable for handling calls due to breaks, coaching, meetings, leave, system time, and other non-productive activities.

One of the most common planning mistakes is forgetting shrinkage. Erlang C tells you how many agents need to be ready to take calls. It does not tell you how many people must be scheduled on payroll to produce that ready staffing level. If your shrinkage is 30 percent and you need 50 agents available, you must schedule more than 50 people. In that case, the scheduled requirement is roughly 72 agents, because only about 70 percent of paid time is available for handling calls.

How to interpret the outputs

Required agents on phones: This is the minimum concurrent staffed level the model found to hit both the service and occupancy constraints.
Scheduled agents: This adjusts the required on-phone staffing for shrinkage so your roster matches real operating conditions.
Service level: The predicted percentage of calls answered within your stated target time.
Average speed of answer: The average time callers wait before an agent answers.
Probability of waiting: The share of callers expected to queue rather than connect immediately.
Occupancy: The portion of agent time expected to be consumed by workload. High occupancy raises strain and can amplify delays when arrival patterns fluctuate.

A useful operating principle is this: service level protects the customer experience, while occupancy protects workforce sustainability. Strong planning balances both.

Public data points that matter for contact centre leaders

When you use a free contact centre Erlang calculator, you are not just choosing a number of seats on the phone. You are making decisions that affect labor cost, employee utilization, and customer access. Public data from government sources provides valuable context for those choices.

Public statistic	Value	Why it matters in staffing	Source
U.S. customer service representative median annual pay	$39,680	Even small overstaffing or understaffing errors have real labor cost implications across large teams.	U.S. Bureau of Labor Statistics
Typical entry level education for customer service representatives	High school diploma or equivalent	Training quality, ramp time, and shrinkage planning remain essential because large teams often include new hires.	U.S. Bureau of Labor Statistics
FCC complaint channels cover billing, service, and access issues	National complaint intake across multiple communications categories	Access and response quality remain visible regulatory and customer experience issues in high volume service environments.	Federal Communications Commission

Those data points reinforce a simple truth: contact centre staffing is not just a math exercise. It is a labor management, quality management, and customer access problem all at once. A free contact centre Erlang calculator provides the mathematical core, but good planning still depends on strong assumptions and operational discipline.

Comparison table: how service outcomes change as staffing increases

The exact result depends on your inputs, but the pattern is consistent across most inbound queues: each additional agent lowers delay risk, but the marginal gain gradually becomes smaller. That is why the best planning approach is to choose a target based on customer expectations, business value, and practical occupancy constraints rather than staffing to perfection.

Scenario	Offered load	Agents on phones	Approximate occupancy	Expected operational effect
Tight staffing	40 Erlangs	44	90.9%	Very high pressure, limited recovery time, vulnerable to short demand spikes.
Balanced staffing	40 Erlangs	48	83.3%	More stable queue behavior with a healthier trade-off between cost and service.
Service-led staffing	40 Erlangs	52	76.9%	Better speed of answer and lower delay probability, but at a higher labor cost.

This comparison is especially useful for budget conversations. A planner can show leadership that one or two fewer agents may save cost in the short term but raise occupancy beyond sustainable levels. Conversely, too much staffing reduces occupancy sharply and may not provide enough incremental service gain to justify the expense. A strong staffing recommendation is usually the point where service target, occupancy ceiling, and budget logic align.

Common mistakes when using a free contact centre Erlang calculator

Using blended averages: If voice, chat, and back office work are mixed into one average, the result may misstate voice staffing. Queue types should be modeled carefully.
Ignoring after call work: If AHT excludes wrap time, the model understates required capacity.
Planning from daily totals only: You can hit the daily average and still fail badly in peak intervals.
Setting occupancy too high: An occupancy target above the practical limit for your operation can create burnout, increased absence, and inconsistent service.
Forgetting shrinkage and attrition effects: A precise queueing answer still fails operationally if your schedules do not account for real non-productive time.
Applying Erlang C to high abandonment queues without caution: If many customers hang up rather than wait, the model can overstate staffing because it assumes queued calls remain until answered.

When Erlang C works well and when you should be careful

Erlang C is best suited to inbound voice environments where customers are willing to wait in queue, contacts arrive with some statistical randomness, and handle times are reasonably stable. It works especially well for service desks, reservations, utility support, healthcare access lines, public sector hotlines, and other high volume inbound teams that track service level by interval.

Use more caution if your queue has high abandonment, aggressive callbacks, substantial overflow logic, severe call retries, or channel mixing that changes work patterns. In those cases, Erlang C is still useful as a baseline, but the result should be validated with historical interval performance and, where possible, simulation. The smart approach is not to reject the model but to understand its assumptions and apply it within the operating context.

Best practice workflow for workforce teams

Forecast contacts by 15 or 30 minute interval.
Validate average handle time using recent, cleaned operational data.
Set a realistic service target and occupancy ceiling.
Run the free contact centre Erlang calculator for each interval.
Apply shrinkage to convert on-phone need into scheduled headcount.
Compare staffing requirement against the schedule plan.
Use intraday management to react when actual arrivals or AHT deviate from forecast.

Teams that follow this process typically get much better control over both cost and customer wait times. The reason is simple: they are using the calculator as part of a management system, not as a one-time estimate. Queueing math is strongest when it is paired with disciplined forecasting, schedule design, and real-time performance review.

Authoritative references for deeper study

These sources are useful for understanding the labor context, customer access implications, and academic foundations behind service operations and queueing analysis.

Final takeaway

A free contact centre Erlang calculator is most valuable when it helps you make better staffing decisions, not just produce a number. The strongest plans combine interval demand, accurate AHT, realistic occupancy, and honest shrinkage. If you use the tool that way, you can forecast labor needs more credibly, defend staffing decisions more clearly, and improve the customer experience without relying on guesswork. Use the calculator above to test scenarios, compare outcomes, and build a more resilient contact centre staffing plan.