Free Erlang C Staffing Calculator
Estimate how many agents you need to hit a target service level while keeping occupancy under control.
Model used: Erlang C (assumes inbound queueing, no abandonment, and stable interval conditions).
What is an Erlang call center calculator?
An Erlang call center calculator is a staffing tool used to estimate how many agents are needed to answer customer calls at a target service level. It is one of the most common workforce management methods for inbound voice operations. Instead of guessing staffing, you can use demand and handling time to get a data-based estimate.
In practical terms, this calculator helps you answer questions like:
- How many agents do I need to answer 80% of calls in 20 seconds?
- What occupancy will my team run at this call volume?
- How does shrinkage affect scheduled headcount?
- What happens if I only staff my currently planned number of agents?
How this calculator works
1) Convert demand into traffic intensity (Erlangs)
Traffic intensity, usually called offered load, measures how much work arrives in the interval.
Example: 400 calls in 30 minutes with a 360-second AHT means roughly 80 Erlangs of offered load.
2) Use Erlang C to estimate wait probability
Erlang C estimates the probability that a caller has to wait before reaching an agent. As staffing rises above offered load, wait probability drops.
3) Calculate service level and ASA
Once probability of waiting is known, service level at a target answer time can be computed. The calculator also estimates average speed of answer (ASA), occupancy, and immediate answer rate.
Input definitions
- Forecasted calls in interval: Expected inbound calls for one planning bucket (commonly 15 or 30 minutes).
- Average handle time (AHT): Talk + hold + after-call work, in seconds.
- Interval length: Time bucket size in minutes.
- Target service level: Percent of calls answered within target time (e.g., 80%).
- Target answer time: Threshold in seconds (e.g., 20 seconds).
- Maximum occupancy: Optional guardrail to avoid overloading agents.
- Shrinkage: Paid time not available for calls (breaks, meetings, PTO, training, absenteeism).
Why occupancy and shrinkage matter
If you only chase service level and ignore occupancy, teams can become unsustainably busy. High occupancy usually increases burnout, errors, and attrition. Likewise, if you ignore shrinkage, you under-schedule and miss targets even when your base math was correct.
This calculator gives both:
- Base required agents: Seats needed actively handling calls.
- Scheduled agents after shrinkage: Gross staffing needed on the roster.
Common mistakes to avoid
- Using monthly average AHT instead of interval-relevant AHT.
- Applying one shrinkage rate across all days and seasons.
- Not recalculating when promotions, outages, or billing cycles change demand.
- Assuming Erlang C includes abandonment behavior automatically.
Practical planning tips
Plan by interval, not by day averages
Daily averages hide peaks. Staffing to averages often creates under-staffed spikes and over-staffed valleys. Use 15- or 30-minute buckets for better control.
Track forecast error
Even strong models miss sometimes. Keep a forecast accuracy log and tune assumptions weekly. Better forecasts improve staffing more than any single formula tweak.
Use scenario testing
Run “what if” scenarios for AHT increases, demand spikes, or absenteeism. Proactive planning is cheaper than emergency overtime.
FAQ
Is this an Erlang B or Erlang C calculator?
This is Erlang C. Erlang B is typically used for blocked-call systems without queueing. Most inbound service desks use Erlang C-style assumptions.
Does it model customer abandonment?
No. Erlang C assumes callers wait indefinitely. If abandonment is material, use a queueing model that includes patience/abandon curves.
Can I use this for chat or email?
You can use it directionally, but asynchronous channels often need concurrency and backlog-aware models beyond classic voice assumptions.
Bottom line
An Erlang call center calculator gives you a fast, credible way to convert demand into staffing requirements. Use it with good forecasting, realistic shrinkage, and occupancy guardrails to keep both customer experience and agent experience healthy.