Service Level: Definition, How It Works, and Standards Across Every Channel
Service level is the percentage of customer contacts answered or responded to within a defined time threshold. It is one of the most widely used performance standards in contact centre management — expressed as two numbers, such as 80/20, meaning 80% of contacts handled within 20 seconds (or other time units depending on the channel).
Critically, service level is not just a call centre metric. It applies across every customer contact channel — voice, live chat, email, social media, and SMS — and the standards, measurement methods, and operational implications differ significantly between them. This page covers service level in its broadest sense across all channels.
If you work in a call centre and are specifically looking for the voice service level metric — traditionally known as Grade of Service (GOS) — the ACXPA Grade of Service guide covers the voice-specific formula, Erlang-based staffing calculations, and the 80/20 benchmark in detail. This page covers the broader concept across all channels.
What service level measures
The percentage of customer contacts answered within a defined time threshold — expressed as a ratio such as 80/20 (80% within 20 seconds).
Why it matters
Service level is the primary measure of customer accessibility — how quickly customers can reach you. It directly drives staffing requirements, customer satisfaction, and operational costs.
What this guide covers
Definition, formula, channel-by-channel standards, the relationship with staffing, key limitations, and how to set the right service level target for your operation.
What is Service Level?
Service level is a performance standard that defines the speed at which customer contacts should be answered or responded to. It is always expressed as a pair of values: a percentage target and a time threshold. The most widely known example is the voice channel standard of 80/20 — 80% of calls answered within 20 seconds.
The concept applies across every inbound contact channel where customers are waiting for a response. The specific values, measurement methods, and operational implications vary significantly by channel — but the underlying principle is consistent: what percentage of your customers will you commit to serving within what timeframe?
In plain English
Service level answers: of all the contacts customers sent us, what percentage did we respond to within our target time? It is the primary measure of how accessible your organisation is to customers who reach out.
Service level vs Service Level Agreement (SLA)
These terms are related but distinct. A service level is the performance metric — the percentage of contacts answered within a threshold. A Service Level Agreement (SLA) is a formal contract that defines the service levels an organisation commits to delivering, often with financial penalties or remedies if targets are missed. SLAs are common in outsourced contact centre (BPO) arrangements and in business-to-business service relationships. In everyday contact centre management, "service level" typically refers to the metric, not the agreement.
How to Calculate Service Level
The service level formula divides the number of contacts handled within the threshold by the total number of contacts offered, expressed as a percentage.
For example, if a contact centre received 200 calls in an interval and answered 164 of them within 20 seconds, the service level for that interval is 164 ÷ 200 × 100 = 82% — meeting the 80/20 target.
💡 The abandoned call question
How to handle abandoned calls in the service level calculation is one of the most debated points in contact centre measurement. If a caller abandons before the threshold time, should they be included in the denominator (total contacts offered)? Most operations include them — meaning abandons count against service level. Some exclude very short abandons (under 5 seconds) as these are often misdialled or immediate hang-ups rather than genuine wait-related abandons. Always clarify how your system calculates service level, as the methodology significantly affects the reported figure.
Service Level Standards by Channel
Service level standards vary significantly across contact channels — reflecting the different nature of each interaction, customer expectations by channel, and the operational reality of handling each contact type. What is considered best practice for voice is completely different from email, chat, or social media.
About these benchmarks
The figures below are commonly cited industry reference points drawn from global industry surveys and practitioner consensus — they are not ACXPA's own research and should not be treated as universal standards. Customer expectations, industry norms, and technology capabilities vary considerably. Use these as a starting point for internal discussion, not as targets to adopt without analysis.
| Channel | Common industry standard | Notes |
|---|---|---|
| Voice (inbound calls) | 80% within 20 seconds | The traditional 80/20 benchmark. Some contact centres target 90/15 for tighter service. For the specific voice measure, see Grade of Service. |
| Live chat | 80% within 20 seconds | Mirrors voice standards as customers expect near-real-time responses. Some operations use 80/30. Chat agents can handle multiple simultaneous sessions, which affects staffing calculations. |
| 100% within 24 hours | Best practice organisations target 80% within 15 minutes for high-priority queues. The 24-hour standard is a minimum — customer expectations are increasingly moving toward same-day response. | |
| Social media | 80% within 1 hour | Public-facing channels like Twitter/X and Facebook carry reputational risk for slow responses. The 1-hour standard is widely cited, though expectations vary by platform and customer segment. |
| SMS / messaging apps | 80% within 40 seconds | Treated similarly to chat given the conversational, near-real-time nature of the channel. Standards are still evolving as messaging volume grows. |
| Web chat / chatbot | Immediate (automated) or 80/20 (agent escalation) | Automated responses are instantaneous. If chatbot cannot resolve and escalates to a human agent, voice/chat service level standards typically apply to the handover. |
Service Level and Staffing — A Direct Relationship
Service level and staffing are inseparably linked. The service level target you set determines how many staff you need — you cannot set a service level target without implicitly committing to the staffing required to achieve it. This is one of the most fundamental principles of contact centre workforce management.
The universal law
The higher the service level target you set, the more staff you need. A tighter threshold (faster answer required) or higher percentage (more calls must meet the threshold) both require more agents — and more cost.
For voice and chat channels, the Erlang C formula calculates exactly how many agents are required to achieve a defined service level at a given call volume and average handle time. This is the mathematical foundation of contact centre workforce planning — and the reason why service level targets must be set with full awareness of their staffing and cost implications.
Higher service level → more staff needed
Targeting 90% of calls within 10 seconds requires significantly more agents on standby than targeting 80% within 30 seconds — even at the same call volume. The tighter the threshold, the more buffer capacity required, the higher the cost.
Service level and occupancy are inversely linked
As service level targets go up, agent occupancy goes down — because more agents need to be available and waiting. You cannot simultaneously target high service levels and high occupancy. This is mathematically inescapable.
💡 Model the staffing implications before setting targets
Use the ACXPA Erlang C Calculator to model exactly how changes to your service level target affect staffing requirements and resulting occupancy before committing to a target. A service level decision made without modelling the staffing implications is not a fully informed decision.
How to Set the Right Service Level Target
One of the most common mistakes in contact centre management is adopting the 80/20 standard without analysis — simply because it is what everyone else uses. The right service level for your operation depends on your specific context, and setting it without that analysis means you may be over- or under-investing in accessibility relative to what your customers actually need.
Understand what your customers actually expect
Customer tolerance for waiting varies by channel, industry, contact urgency, and alternatives available. A customer calling about an emergency has zero tolerance for waiting. A customer querying a non-urgent account balance may be perfectly comfortable waiting 2 minutes. Research your customers' actual expectations rather than assuming the industry standard is right for your context.
Understand the commercial implications
In revenue-generating contact centres — inbound sales, financial services — every missed or abandoned call has a direct cost. A high service level target can be directly justified by the revenue it protects. In non-commercial service environments, the calculus is different. What is the cost of a customer not being served within threshold versus the cost of the additional staff required to serve them faster?
Model the staffing and cost impact
For voice and chat, use Erlang C to calculate exactly how many agents are required at your proposed service level, call volume, and AHT. Calculate the cost of those agents. Then ask: is the customer experience benefit of this service level worth the cost? This is the conversation that should precede any service level commitment.
Set a range, not a fixed target
Best practice is to manage service level as a band — for example, targeting 78–85% rather than exactly 80%. A band acknowledges the natural variation in call arrival patterns and staffing, allows for interval-level fluctuation without triggering unnecessary escalation, and is more meaningful operationally than a single-point target that is either exactly met or missed.
Measure at the interval level, not just daily or monthly
A monthly or daily service level average can mask significant intraday variation — a contact centre might hit 82% for the month while running at 65% during the morning peak and 95% overnight. Service level should be monitored and managed at the half-hour interval level for operational meaning. Monthly averages are useful for trend analysis and reporting, not for operational management.
Key Limitations of Service Level as a Metric
Service level is valuable and important — but it has well-documented limitations that every contact centre manager should understand. Treating it as the primary or sole measure of contact centre performance is a common mistake.
❌ Measures speed, not quality
Service level tells you how quickly contacts were answered. It says nothing about what happened during the interaction — whether the customer's issue was resolved, whether they were treated well, or whether they will need to call back. A contact centre can hit 90/20 consistently while delivering poor customer outcomes. Service level must always be paired with quality and outcome metrics.
❌ Averages hide intraday peaks
A contact centre that hits 80% service level for the day may have run at 55% during the morning peak and 95% in the afternoon. The customers who called during the peak experienced poor service, but that is invisible in the daily average. Manage at the interval level.
❌ Does not capture abandoned callers
Customers who abandoned before being answered are often excluded from service level calculations or handled inconsistently. These are precisely the customers who experienced the worst service. Always monitor abandonment rate alongside service level — a good service level with a high abandonment rate is a warning sign, not a success.
❌ The 80/20 standard is arbitrary
The widely cited 80% in 20 seconds benchmark has no scientific basis — it emerged as an industry convention and has persisted largely by inertia. Research does not consistently show that customers are more satisfied when 80% of calls are answered in 20 seconds versus 75% in 30 seconds. Set your service level based on your customers' actual expectations and your commercial context, not convention.
Service Level for Voice — Grade of Service
For voice (inbound telephone) contacts, service level has a specific traditional name in the contact centre industry: Grade of Service (GOS). The two terms are used interchangeably in most contact centres, but GOS is the older, more technical telecommunications term and remains widely used in Australian contact centre operations.
GOS is expressed as a ratio — most commonly 80/30 (80% of calls answered within 30 seconds) — and is the primary operational metric used in Erlang-based workforce planning for voice channels. The ACXPA glossary covers Grade of Service in detail, including how to calculate it, the relationship with staffing, and the specific risks and limitations of the voice service level measure.
Frequently Asked Questions About Service Level
What is service level in a contact centre?
Service level is the percentage of customer contacts answered or responded to within a defined time threshold. It is expressed as two numbers — a percentage and a time value — such as 80/20 (80% of contacts handled within 20 seconds). It applies across all contact channels including voice, chat, email, social media, and SMS, though the specific thresholds and industry standards differ by channel.
What is the standard service level for a call centre?
The most widely cited voice channel benchmark is 80% of calls answered within 20 seconds — commonly written as 80/20. Some contact centres use 80/30 (80% within 30 seconds) or target tighter standards like 90/15. However, the 80/20 figure is an industry convention rather than a scientifically derived standard. The right service level for your operation should be based on your customers' actual expectations and your commercial context.
What is the difference between service level and Grade of Service?
Grade of Service (GOS) is the traditional telecommunications term for the voice channel service level metric. The two terms are largely interchangeable in contact centre operations — both measure the percentage of calls answered within a time threshold. Service level is the broader term that applies across all channels (voice, chat, email, social media, SMS), while Grade of Service is used specifically for voice/telephony. See the Grade of Service guide for the detailed voice-specific treatment.
What is the difference between service level and SLA?
A service level is a performance metric — the percentage of contacts answered within a threshold. A Service Level Agreement (SLA) is a formal contract that defines the service levels an organisation commits to delivering, usually with financial consequences for missing targets. SLAs are common in outsourced contact centre arrangements and B2B service relationships. In everyday contact centre operations, "service level" refers to the metric; "SLA" refers to the contractual commitment.
How does service level affect staffing?
Service level and staffing are directly linked — the higher your service level target, the more agents you need. For voice and chat channels, the Erlang C formula calculates exactly how many agents are required to achieve a given service level at a defined call volume and average handle time. Setting a service level target without modelling the staffing implications is not a fully informed decision. Use the ACXPA Erlang C Calculator to model the relationship for your specific operation.
What are the service level standards for email and chat?
Industry standards vary by channel. For live chat, most operations target 80% within 20–30 seconds — similar to voice, reflecting real-time customer expectations. For email, the common standard is 100% within 24 hours, though best-practice operations target much faster response times for priority queues. Social media contacts are typically targeted at 80% within 1 hour. These are industry reference points, not universal requirements — the right standard for your organisation depends on your customers' expectations and your business context.
Should service level be measured as a daily average?
Daily averages are useful for trend analysis but insufficient for operational management. A daily service level of 80% can mask intervals where service level dropped to 50% during a morning peak while reaching 95% overnight. For operational decision-making, service level should be monitored and managed at the half-hour interval level. Daily and weekly averages are appropriate for performance reporting and trend analysis.
Is the 80/20 service level rule still relevant?
The 80/20 benchmark remains widely used, but its relevance as a universal standard is increasingly questioned. It originated as a convention, not from research into what customers actually require. Some contact centres are tightening targets (90/15); others are relaxing them in favour of investing in quality and first contact resolution. The most meaningful approach is to base your service level target on your customers' actual wait tolerance data and your commercial context — not on the convention simply because it is familiar.
Where to Next
Summary: Service Level
Service level is the fundamental measure of customer accessibility in a contact centre — the percentage of contacts answered within a defined time threshold, across every channel. The standard varies by channel: 80/20 for voice and chat, 100% within 24 hours for email, 80% within an hour for social media. But the principle is consistent: what percentage of your customers will you commit to serving within what timeframe?
The most important thing to understand about service level is that it is not a standalone quality measure. It tells you how quickly contacts were answered — nothing about what happened during the interaction, whether issues were resolved, or whether customers will call back. It must always be used alongside quality, CSAT, and first contact resolution data to give a complete picture of performance.
For the voice channel specifically, service level has a traditional name — Grade of Service — and a direct relationship with Erlang-based workforce planning. For that detailed treatment, see the Grade of Service guide. For all channels combined, service level is the operational standard that connects customer expectations, staffing decisions, and the cost of accessibility — and setting it well requires more than defaulting to 80/20.
