Free Erlang Calculator for Excel
Calculate call center staffing requirements using the Erlang C formula. Optimize agent scheduling and reduce wait times.
Comprehensive Guide to Erlang Calculators for Excel
The Erlang C formula is a mathematical model used to determine the optimal number of agents required in a call center to meet specific service level targets. Originally developed by Danish mathematician Agner Krarup Erlang in the early 20th century, this formula has become the gold standard for workforce management in contact centers worldwide.
Why Use an Erlang Calculator?
Implementing an Erlang calculator in Excel provides several critical benefits for call center operations:
- Cost Optimization: Prevents both overstaffing (which increases costs) and understaffing (which degrades service quality)
- Service Level Management: Ensures you meet your target answer times consistently
- Data-Driven Decisions: Provides objective metrics for staffing decisions rather than relying on guesswork
- Scalability: Easily adjust calculations as call volumes change
- Performance Benchmarking: Compare actual performance against theoretical models
The Erlang C Formula Explained
The Erlang C formula calculates the probability that a call will need to wait, given:
- A = Total traffic intensity (in erlangs) = (Call volume × AHT) / 3600
- N = Number of agents
- W = Average speed of answer (ASA) target
The core formula is:
P(W > t) = (AN/N!) / [(AN/N!) + (1 – A/N) × Σi=0N-1 (Ai/i!)]
Where P(W > t) represents the probability that a call will wait longer than time t.
Key Input Parameters
1. Call Volume
The number of calls expected during a specific time period (typically per hour or per 30 minutes). This should be based on historical data and adjusted for seasonal variations.
2. Average Handle Time (AHT)
The average duration of a call, including talk time, hold time, and after-call work. AHT is calculated as:
AHT = (Total Talk Time + Total Hold Time + Total After-Call Work) / Total Number of Calls
3. Service Level Target
Typically expressed as “X% of calls answered in Y seconds” (e.g., 80% of calls answered in 20 seconds). Common industry standards include:
- 80/20 (80% answered in 20 seconds)
- 85/20
- 90/20
- 95/20 (premium service level)
4. Shrinkage Factor
Accounts for time agents aren’t available to take calls due to:
- Breaks
- Training
- Meetings
- Absenteeism
- System downtime
Typical shrinkage rates range from 20% to 40% depending on the industry.
Implementing Erlang in Excel
While you can build a basic Erlang calculator in Excel using the formula directly, most implementations use one of these approaches:
| Method | Pros | Cons | Complexity |
|---|---|---|---|
| Native Excel Formulas | No dependencies, fully customizable | Complex to implement, error-prone | High |
| VBA Macro | More accurate, can handle iterative calculations | Requires macro-enabled files, security concerns | Medium |
| Add-in/Plugin | Most accurate, user-friendly interface | Potential cost, dependency on third-party | Low |
| Web-Based Calculator (like this one) | Always up-to-date, accessible from anywhere | Requires internet connection | Low |
Step-by-Step Excel Implementation
-
Set Up Your Input Cells
Create labeled cells for:
- Call volume (B2)
- Average handle time in seconds (B3)
- Target service level percentage (B4)
- Target answer time in seconds (B5)
- Shrinkage factor percentage (B6)
-
Calculate Traffic Intensity (A)
In cell B8, enter:
=(B2*B3)/3600
-
Implement the Erlang C Formula
This requires creating a series of helper columns to calculate the factorial components. For a complete implementation, you’ll need to:
- Create a column for i from 0 to N (where N is your maximum agent count)
- Calculate A^i for each i
- Calculate i! for each i
- Calculate A^i/i! for each i
- Sum these values appropriately
-
Add Shrinkage Calculation
In cell B9, calculate total staff needed:
=ROUNDUP(B7/(1-B6/100),0)
Where B7 contains your Erlang C agent requirement.
-
Create Visualizations
Add charts to show:
- Agent requirements vs. call volume
- Service level achievement
- Wait time distributions
Common Mistakes to Avoid
1. Incorrect Time Units
Always ensure consistent time units. The Erlang formula requires:
- AHT in seconds
- Call volume per hour
- Traffic intensity in erlangs (dimensionless)
2. Ignoring Shrinkage
Many calculators only provide the “bare bones” agent requirement without accounting for real-world factors that reduce agent availability.
3. Static Calculations
Call volumes vary by time of day, day of week, and season. Using a single average value will lead to inaccurate staffing.
4. Overlooking After-Call Work
AHT should include all post-call activities, not just talk time. Typical after-call work adds 30-50 seconds per call.
5. Not Validating Results
Always compare calculator results with actual performance data to identify discrepancies.
6. Using Erlang B Instead of C
Erlang B assumes blocked calls are cleared (lost), while Erlang C assumes calls queue. Most call centers should use Erlang C.
Advanced Applications
Beyond basic staffing calculations, Erlang models can be applied to:
| Application | Implementation | Benefit |
|---|---|---|
| Multi-Skill Staffing | Create separate Erlang calculations for each skill group, then optimize across the entire workforce | Improves utilization of specialized agents while maintaining service levels |
| Real-Time Adjustments | Integrate with ACD systems to adjust staffing based on actual vs. forecasted volumes | Reduces intra-day variability in service levels |
| Cost-Benefit Analysis | Model the financial impact of different service level targets | Quantifies the trade-off between service quality and operational cost |
| Channel Blending | Extend Erlang to include email, chat, and other digital channels | Creates a unified workforce management approach across all channels |
| Scenario Planning | Create “what-if” models for different call volume scenarios | Improves preparedness for unexpected volume spikes |
Industry Benchmarks and Standards
According to research from the Call Center Helper and data from the International Customer Management Institute (ICMI), typical call center metrics include:
- Average Handle Time: 3-6 minutes (180-360 seconds) across industries
- Service Level Targets:
- Retail: 80/20
- Financial Services: 85/20
- Healthcare: 90/20
- Premium Services: 95/20
- Shrinkage Rates:
- Inbound: 30-35%
- Outbound: 25-30%
- Blended: 35-40%
- Occupancy Rates: 85-90% is considered optimal (higher leads to burnout, lower indicates inefficiency)
The National Institute of Standards and Technology (NIST) provides additional mathematical resources for queueing theory applications in their publications database.
Alternative Workforce Management Approaches
While Erlang remains the most widely used method, several alternative approaches exist:
-
Simulation Modeling
Uses Monte Carlo simulations to model call center operations with more complex variables than Erlang can handle. Particularly useful for:
- Multi-channel contact centers
- Centers with complex routing rules
- Operations with significant variability in call types
-
Machine Learning Forecasting
Emerging approach that uses historical data to predict staffing needs with higher accuracy than traditional methods. Benefits include:
- Automatic adjustment for seasonal patterns
- Incorporation of external factors (weather, promotions)
- Continuous learning and improvement
-
Agent-Based Modeling
Simulates each agent and call as individual entities, allowing for:
- Detailed modeling of agent behaviors
- Analysis of skill-based routing impacts
- Evaluation of training program effectiveness
-
Queueing Network Models
Extends basic queueing theory to model complex call center networks with:
- Multiple queues
- Priority routing
- Agent skill groups
Excel Template Implementation Guide
To create your own Erlang calculator in Excel:
-
Download the Template
Start with our free Erlang calculator template which includes:
- Pre-built Erlang C calculations
- Shrinkage factor adjustments
- Visualization charts
- Sample data for validation
-
Customize Input Parameters
Modify the input cells to match your call center’s specific metrics:
- Adjust time intervals (15-min, 30-min, or hourly)
- Add multiple skill groups if needed
- Incorporate your historical shrinkage data
-
Validate with Real Data
Compare template outputs with your actual performance data:
- Check agent requirements against your current staffing
- Verify service level achievements
- Adjust AHT assumptions if needed
-
Automate Data Import
Connect your Excel template to data sources:
- ACD system reports
- Workforce management software
- CRM call logs
Use Power Query or VBA to automate data refreshes.
-
Create Management Dashboards
Enhance your template with:
- Interactive charts showing staffing vs. performance
- Conditional formatting to highlight issues
- Scenario comparison tools
Frequently Asked Questions
Q: How often should I recalculate Erlang requirements?
A: Best practice is to:
- Recalculate daily for operational planning
- Review weekly for tactical adjustments
- Analyze monthly for strategic workforce planning
Q: Can Erlang be used for email and chat channels?
A: While originally designed for phone calls, the Erlang C model can be adapted for other channels by:
- Using “handle time” instead of “talk time”
- Adjusting service level targets appropriately
- Accounting for concurrent interactions (agents can often handle multiple chats simultaneously)
Q: What’s the difference between Erlang B and Erlang C?
A: The key differences are:
| Feature | Erlang B | Erlang C |
|---|---|---|
| Queue Behavior | Blocked calls are cleared (lost) | Calls enter a queue and wait |
| Typical Use Case | Telephony networks, systems where calls can’t queue | Call centers, service desks |
| Key Metric | Blocking probability | Average speed of answer (ASA) |
| Staffing Impact | Requires fewer agents for same traffic | Requires more agents to handle waiting calls |
Q: How does shrinkage affect my staffing calculations?
A: Shrinkage increases your total staffing requirement according to this formula:
Total Staff = (Erlang Agents) / (1 – Shrinkage Percentage)
For example, with 50 required agents and 30% shrinkage:
Total Staff = 50 / (1 – 0.30) = 50 / 0.70 ≈ 71 agents
Expert Tips for Optimization
-
Segment Your Data
Calculate Erlang requirements separately for:
- Different call types (sales vs. support)
- Time intervals (peak vs. off-peak)
- Customer segments (VIP vs. standard)
-
Combine with Historical Trends
Adjust your calculations based on:
- Day-of-week patterns
- Seasonal variations
- Marketing campaign impacts
-
Implement Real-Time Monitoring
Use your Erlang model to:
- Trigger alerts when actual performance deviates from plan
- Automate intraday staffing adjustments
- Identify emerging trends before they become problems
-
Train Your Team
Ensure managers understand:
- How Erlang calculations work
- Limitations of the model
- When to override automated recommendations
-
Integrate with Other Systems
Connect your Erlang calculator with:
- Workforce management software
- ACD/IVR systems
- HR systems for scheduling
Case Study: Retail Call Center Optimization
A major retail chain with 150 stores implemented an Erlang-based workforce management system with these results:
| Metric | Before Erlang | After Erlang | Improvement |
|---|---|---|---|
| Service Level (80/20) | 65% | 87% | +22 percentage points |
| Average Speed of Answer | 45 seconds | 18 seconds | 60% faster |
| Abandonment Rate | 12% | 4% | 67% reduction |
| Agent Utilization | 72% | 88% | +16 percentage points |
| Operational Cost | $1.2M/year | $1.05M/year | 12.5% savings |
The implementation followed this timeline:
- Week 1-2: Data collection and validation
- Week 3: Excel template customization
- Week 4: Pilot testing with one team
- Week 5-6: Full rollout and training
- Week 7+: Continuous optimization
Future Trends in Workforce Optimization
The field of call center workforce management is evolving rapidly with these emerging trends:
1. AI-Powered Forecasting
Machine learning algorithms that:
- Analyze hundreds of variables simultaneously
- Automatically detect patterns humans might miss
- Continuously improve with more data
2. Omnichannel Workforce Management
Unified models that handle:
- Voice calls
- Live chat
- Social media interactions
- Video calls
3. Gig Economy Integration
Flexible staffing models that:
- Incorporate part-time and on-demand agents
- Use real-time bidding for shift coverage
- Enable rapid scaling for unexpected volume
4. Employee Experience Focus
New metrics that consider:
- Agent satisfaction scores
- Work-life balance indicators
- Career development opportunities
Additional Resources
For further study on Erlang calculations and call center optimization:
- NIST Queueing Theory Guide (PDF) – Comprehensive mathematical treatment from the National Institute of Standards and Technology
- MIT Lecture Notes on Random Processes – Advanced queueing theory from Massachusetts Institute of Technology
- Call Center Magazine – Industry publication with practical applications and case studies
- The Balance Careers – Call Center Section – Career-focused advice and industry trends