Service Level Agreement

What is Service Level Agreement?

A Service Level Agreement (SLA) is a formal contract between a service provider and a customer outlining the expected service standards and responsibilities. It primarily defines measurable performance metrics to ensure consistent service quality and accountability.

SLA vs Service Level: What’s the Difference

The definition above describes the contractual side of things. In everyday call center conversation though, “service level” usually means something much narrower: a single performance metric, most commonly 80/20. It helps to keep the two apart:

Service Level Agreement (SLA): the documented agreement itself, covering service standards, responsibilities, escalation, and penalties, as defined above.
Service Level (SL): a specific performance metric that can sit inside that agreement, typically the percentage of calls answered within a set number of seconds.

An SLA can bundle a service level target together with other commitments, resolution time, uptime, CSAT. Service level on its own is just the one number. The rest of this page focuses on that metric.

Service Level Formula

Service level is calculated as:

Service Level % = (Calls Answered Within Threshold ÷ Total Calls Offered) × 100

For an 80/20 target, “within threshold” means within 20 seconds. So if your team answers 840 out of 1,000 calls within 20 seconds, your service level for that period is (840 ÷ 1,000) × 100 = 84%, above the 80/20 benchmark.

Common Service Level Standards

80/20 is the most cited benchmark, but it isn’t the only one in use. Which variant fits depends on your industry, queue type, and cost tolerance.

Standard	Meaning	When to Use
80/20	80% of calls answered within 20 seconds	General-purpose benchmark; sales and support queues where speed drives conversion or satisfaction
90/10	90% of calls answered within 10 seconds	High-urgency lines: healthcare, emergency services, VIP or priority-tier support
80/30	80% of calls answered within 30 seconds	Lower-urgency or cost-sensitive queues, complex technical support where longer handle times make a strict 20-second target expensive to staff for

Types of SLAs in Call Centers

Beyond the 80/20-style response time target, call center SLAs commonly cover several other service dimensions:

Type	What It Covers	Example
Response Time SLA	How fast calls or messages are answered	80% of calls answered within 20 seconds
Resolution Time SLA	How fast an issue is fully resolved, not just answered	90% of issues resolved within 2 hours
Availability SLA	Platform or system uptime commitments	99.9% uptime
Quality SLA	Professionalism, script and compliance adherence, accuracy	Call quality scores above a set threshold
CSAT SLA	Minimum customer satisfaction target tied to the agreement	85% or higher
FCR SLA	Minimum first-call resolution rate	80% of issues resolved on first contact
Omnichannel SLA	Separate response expectations per channel	Faster response on voice than on email or social

Most call centers don’t formalise every row above as a strict contractual SLA, but tracking them as internal targets alongside your 80/20 service level gives a fuller picture of performance than speed of answer alone.

Why 80/20 Isn’t Always Right For You

80/20 works as a starting point, but treating it as a universal rule can lead you to over-staff or under-staff for your actual queue. A few reasons it varies:

No scientific backing: As noted above, 20 seconds is an inherited engineering convention, not a customer-behaviour finding. There’s no research showing customers are satisfied at 20 seconds and dissatisfied at 25.

Handle time changes the math: Technical support queues with long, complex calls can make an 80/20 target expensive to maintain, you may need a much larger bench of agents than the call volume alone suggests.

Channel changes expectations: A customer messaging on WhatsApp or webchat will often accept a two-minute wait; a customer holding on a live voice queue may abandon in under a minute. Applying one voice-style service level target across every channel misreads how patient customers actually are.

Cost has to justify it: In thin-margin operations, staffing to hit 80/20 during every peak may simply cost more than the retained revenue or satisfaction it buys. A deliberately lower target, honestly set, can be the more sustainable choice.

The practical takeaway: use 80/20 as your default starting benchmark, then adjust it deliberately based on your queue’s handle time, channel mix, and cost constraints, rather than treating it as a pass/fail bar.

See how Exotel helps you hit SLA targets.  Explore Call Routing & Analytics

Service Level vs Other Metrics

Service level gets confused with a few adjacent metrics. They measure related but different things:

Metric	What It Measures	How It Differs From Service Level
Service Level	Speed of answer: % of calls answered within a set threshold	The baseline metric this page covers
First Call Resolution (FCR)	Whether an issue is resolved on the first contact, without a callback or repeat call	Measures resolution quality, not answer speed, a call can be answered fast but still need three follow-ups
CSAT	How satisfied the customer says they were, via post-call survey	A subjective outcome measure; a call can hit its service level target and still score low on CSAT if the resolution itself was poor
Average Handle Time (AHT)	How long an agent spends per call, including hold and after-call work	Measures efficiency per call, not whether the call was answered quickly in the first place

For a deeper look at resolution quality specifically, see our First Call Resolution guide.

As a general reference point, Octopus Tech’s guide to call center SLAs puts a healthy first-call resolution rate in the 70-80% range, and associates well-managed SLA programs with CSAT scores above 85%. Treat both as general industry patterns rather than fixed thresholds every business should target.

Key Characteristics of Service Level Agreement

• Performance Metrics: Specifies key indicators such as availability, response time, and resolution time.
• Roles and Responsibilities: Clearly defines duties of both service provider and customer.
• Penalties and Remedies: Details consequences for failing to meet agreed standards.
• Review and Reporting: Regular assessments ensure SLA compliance and improvements.

Use Cases of Service Level Agreement in Customer Experience

• Call Center Operations: Guarantees response and resolution times to enhance customer satisfaction.
• Cloud Service Providers: Ensures uptime and performance critical for customer applications.
• IT Support Services: Defines support availability, minimizing customer downtime.
• Telecommunication Services: Establishes quality and reliability benchmarks for seamless communication.

Why Service Level Agreement Matters

• Customer Trust: Builds confidence through clear expectations.
• Accountability: Drives responsibility for service delivery.
• Improved CX: Ensures consistent, high-quality interactions.
• Risk Management: Minimizes impact of service disruptions.

What Actually Moves Your Service Level

Shrinkage: Every hour lost to breaks, training, or unplanned absenteeism is an hour not available to answer calls, directly pulling your service level down. See our Shrinkage guide for how to calculate and plan around it.

Workforce management: Accurate demand forecasting and scheduling is what turns a service level target into a realistic staffing plan rather than a number you miss every peak. Our workforce management guide covers forecasting, scheduling, and intraday adherence.

Routing and call distribution: How efficiently your system routes calls to the next available, right-skilled agent affects how many calls get answered within threshold. See how Exotel’s call routing and analytics tools support this.

Manager oversight: Service level trends need a manager tracking them in real time, not just at month-end. Our Call Center Manager guide covers the KPIs worth watching daily.

Ready to hit your service level targets consistently? Request a Demo