Free Erlang C Calculator Excel

Calculate call center staffing requirements using the Erlang C formula. Get Excel-ready results with visual charts.

The Erlang C formula is the gold standard for call center workforce management, helping managers determine the optimal number of agents needed to meet service level targets. This comprehensive guide explains how to use our free Erlang C calculator, interpret the results, and implement the findings in your call center operations.

What is the Erlang C Formula?

The Erlang C formula is a mathematical model developed by Danish mathematician A.K. Erlang to calculate:

• The number of agents required to handle incoming calls
• The probability that calls will wait in queue
• The average time callers will wait before being answered
• The service level (percentage of calls answered within a target time)

Unlike Erlang B (which assumes blocked calls are lost), Erlang C assumes calls that can’t be answered immediately are held in a queue until an agent becomes available – making it perfect for call center environments.

Key Components of Erlang C

1. Call Volume (λ): Number of calls arriving per time period
2. Average Handle Time (AHT): Average duration of each call (including talk time and after-call work)
3. Number of Agents (N): The variable we’re solving for
4. Service Level Target: Percentage of calls to be answered within a specific time (e.g., 80% in 20 seconds)
5. Shrinkage Factor: Accounts for time agents spend not handling calls (breaks, training, etc.)

How to Use Our Free Erlang C Calculator

Our interactive calculator provides Excel-compatible results you can use for workforce planning. Here’s how to use it effectively:

Step 1: Gather Your Input Data

Before using the calculator, collect these key metrics from your call center:

• Historical call volume: Use your ACD reports to determine calls per hour/interval
• Average handle time: Calculate from your call recordings or WFM system
• Service level goals: Typically 80% of calls answered in 20 seconds, but may vary by industry
• Shrinkage factors: Account for breaks (usually 20-30%), training, meetings, etc.

Step 2: Enter Your Parameters

Input your data into the calculator fields:

1. Call Volume: Enter your expected calls per hour
2. Average Handle Time: Input in seconds (include talk time + after-call work)
3. Target ASA: Your desired average speed of answer in seconds
4. Target Service Level: Percentage of calls to answer within ASA target
5. Shrinkage Factor: Percentage of time agents aren’t available to take calls
6. Time Interval: Select your forecasting interval (15, 30, or 60 minutes)

Step 3: Interpret the Results

The calculator provides several critical outputs:

Metric	Description	Industry Benchmark
Required Agents (without shrinkage)	Minimum agents needed to meet service level targets	Varies by call volume and AHT
Required Agents (with shrinkage)	Total agents needed accounting for non-productive time	Typically 20-30% higher than raw requirement
Achieved Service Level	Percentage of calls answered within target ASA	80% is standard for most industries
Average Speed of Answer	Average time callers wait before being answered	<20 seconds for most industries
Probability of Waiting	Likelihood a caller will experience any wait time	Should be <20% for good service
Occupancy Rate	Percentage of time agents spend handling calls	80-85% is optimal (higher leads to burnout)

Erlang C Formula Explained

The Erlang C formula calculates the probability that a call will wait in queue based on these parameters:

The formula is:

P_W = (A^N/N!) / [ (A^N/N!) + (1-ρ) * Σ_i=0^N-1 (Aⁱ/i!) ]

Where:
A = λ * AHT (traffic intensity in erlangs)
N = number of agents
ρ = A/N (utilization factor)
P_W = probability of waiting

Our calculator solves this iteratively to find the minimum N that achieves your service level target.

Practical Example Calculation

Let’s work through an example with these parameters:

• Calls per hour: 300
• Average handle time: 180 seconds (3 minutes)
• Target ASA: 20 seconds
• Target service level: 80%
• Shrinkage: 30%

Step 1: Calculate traffic intensity (A)

A = (300 calls/hour * 180 seconds) / 3600 seconds/hour = 15 erlangs

Step 2: The calculator would iterate through possible agent counts to find the minimum N where:

P(W < 20 seconds) ≥ 80%

Result: The calculator determines you need 22 agents (without shrinkage) to meet this target.

With shrinkage: 22 / (1 – 0.30) = 31.4 → 32 agents needed

Implementing Erlang C Results in Your Call Center

Once you have your Erlang C results, follow these steps to implement them effectively:

1. Staffing Schedule Creation

• Use the “Required Agents (with shrinkage)” number as your baseline
• Distribute agents across your operating hours based on call volume patterns
• Consider implementing split shifts or part-time roles to match peak periods
• Build in buffer for unexpected volume spikes (typically 5-10% extra)

2. Performance Monitoring

Track these key metrics to ensure your staffing meets targets:

Metric	Target	How to Improve
Service Level	≥80% in 20 sec	Add agents, reduce AHT, improve routing
Average Speed of Answer	<20 seconds	Optimize staffing, improve IVR, add callback options
Abandonment Rate	<5%	Add agents, offer callbacks, improve self-service
Occupancy Rate	80-85%	Adjust staffing, cross-train agents, improve processes
First Call Resolution	>70%	Improve training, knowledge base, agent empowerment

3. Continuous Improvement

• Compare actual performance vs. Erlang C predictions weekly
• Adjust your inputs as AHT or call volume patterns change
• Use the Excel export to create historical trend analysis
• Conduct root cause analysis when metrics deviate from targets
• Regularly recalibrate your shrinkage factors based on actual data

Common Erlang C Mistakes to Avoid

1. Using incorrect time intervals: Always match your forecasting interval to your call volume data collection period
2. Ignoring shrinkage: Forgetting to account for non-productive time leads to understaffing
3. Overlooking call patterns: Seasonality and day-of-week variations significantly impact requirements
4. Static AHT assumptions: Handle times often vary by call type and agent experience
5. Not validating results: Always compare calculator outputs with actual performance data
6. Ignoring multi-channel: Modern contact centers must account for email, chat, and social media volume

Advanced Erlang C Applications

Multi-Skill Staffing

For centers with specialized agent groups:

• Run separate Erlang C calculations for each skill group
• Account for cross-training percentages between groups
• Use the calculator for each queue separately
• Consider implementing skills-based routing to optimize agent utilization

Blended Contact Centers

For centers handling multiple contact types (calls, emails, chats):

• Calculate separate requirements for each channel
• Use equivalent workload units to combine requirements
• Account for different handle times across channels
• Consider using Erlang X for true multi-channel modeling

Real-Time Adjustments

For intra-day management:

• Use the calculator to create “what-if” scenarios
• Develop playbooks for volume spikes (e.g., “If volume exceeds forecast by 20%, add 3 agents”)
• Implement real-time adherence monitoring
• Use the Excel export to create dynamic staffing templates

Erlang C vs. Other Workforce Management Methods

Method	Best For	Advantages	Limitations
Erlang C	Call centers with queues	Accurate for predictable patterns, industry standard	Assumes Poisson arrival distribution, no call abandonments
Erlang B	Systems with no queue (blocked calls lost)	Simpler calculation, good for network design	Not appropriate for call centers
Simulation Modeling	Complex environments with many variables	Can model abandonments, callbacks, complex routing	Requires specialized software, more complex
Machine Learning	Centers with large historical datasets	Can learn complex patterns, adapt to changes	Requires data science expertise, black-box nature
Rule of Thumb	Quick estimates	Simple to calculate (e.g., AHT * calls / 3600)	Very inaccurate, doesn’t account for service levels

Excel Implementation Tips

While our calculator provides Excel-compatible outputs, you may want to build your own Erlang C model in Excel. Here are some advanced tips:

Building Your Own Erlang C Calculator

1. Use the GAMMALN function for factorial calculations in the Erlang C formula
2. Implement goal seek to solve for the required number of agents
3. Create data validation for all input cells
4. Build a sensitivity analysis table to show how changes in inputs affect outputs
5. Add conditional formatting to highlight when targets aren’t met

Excel Formulas for Key Calculations

Traffic Intensity (A):

=(Calls_per_hour * AHT_seconds) / 3600

Utilization (ρ):

=A/agents

Erlang C Probability (simplified):

=EXP((-1*(agents-A)*target_ASA/AHT) * (A/agents)^agents / (FACT(agents) * (1-(A/agents))))

Excel Template Structure

Organize your workbook with these sheets:

• Inputs: All parameters and assumptions
• Calculations: Intermediate calculations and formulas
• Results: Final staffing recommendations
• Charts: Visualizations of staffing vs. service level tradeoffs
• Historical: Past performance data for comparison

Industry-Specific Erlang C Applications

Healthcare Call Centers

• Typically require higher service levels (90% in 20 seconds)
• Must account for HIPAA-compliant call handling times
• Often need multi-language support staffing
• Seasonal variations from flu season or health crises

Financial Services

• High security requirements may increase AHT
• Peak volumes around market openings/closings
• Often require specialized compliance-trained agents
• May need separate queues for different product lines

Retail/E-commerce

• Extreme seasonality (holiday peaks)
• High volume of simple inquiries (order status, returns)
• Opportunity for self-service deflection
• Often benefit from chat/email blending

Technical Support

• Wide variation in call complexity
• Longer AHT for complex issues
• Benefits from tiered support structure
• Often requires specialized technical skills

Future Trends in Call Center Staffing

The Erlang C formula remains foundational, but emerging trends are shaping how it’s applied:

AI and Predictive Staffing

• Machine learning can predict call volumes with greater accuracy
• AI can optimize intra-day staffing adjustments
• Natural language processing helps categorize call types for better routing

Omnichannel Workforce Management

• Unified forecasting across all digital channels
• Skills-based routing for multi-channel agents
• Blended Erlang models for different contact types

Gig Economy Staffing

• On-demand agents for peak periods
• Flexible scheduling models
• Performance-based compensation structures

Real-Time Optimization

• Dynamic staffing adjustments based on real-time data
• Automated break scheduling to optimize coverage
• Predictive abandonment modeling

For official workforce management standards, refer to the U.S. Bureau of Labor Statistics Occupational Outlook Handbook for Customer Service Representatives.

The original Erlang formulas were developed by A.K. Erlang. Learn more about his foundational work from University College London’s telecommunications resources.

For academic research on call center operations, explore publications from MIT Sloan School of Management’s Operations Research Center.