Service level vs answer rate

Deep-dive lesson · about 10 minutes · short quiz at the end

ccPlanning academy · metrics · deep dive

Service level vs answer rate

Two service metrics that sound similar and measure very different things.

Definitions

Speed vs eventual success.

Service level: the percentage of contacts answered within a target time — “80% within 20 seconds.” Answer rate (or % answered): the percentage of contacts answered at all, whenever. One measures speed; the other measures whether you got to them.

Service level

80/20 is a choice, not a law.

“80% in 20 seconds” is the most quoted target in the industry — and it has no scientific basis. It’s a convention. The right target depends on what your customers tolerate and what the contact is worth; copying 80/20 unthinkingly is how many centres over- or under-invest.

What SL hides

The average is silent about the tail.

Hit 80/20 and 20% of callers waited longer than 20 seconds — but how much longer? SL doesn’t say. A centre at 80/20 with a few callers waiting ten minutes looks identical to one where the slowest waited 25 seconds. The tail is where complaints live.

Answer rate

The metric customers actually feel.

Customers don’t experience “80% in 20 seconds” — they experience whether their call was answered or they gave up. Answer rate captures the contacts you simply never served, which is often what really damages satisfaction and revenue.

The abandonment trap

A high answer rate can hide abandonment.

If impatient callers bail before counting as “offered,” the rate flatters you.

The trap, explained

Short-abandons can game the number.

Many systems exclude calls abandoned in the first few seconds from the calculation. Push waits up and frustrated callers abandon early — they vanish from the denominator, and your answer rate improves even as service gets worse. Always know what your formula counts.

Using them together

SL for the experience, answer rate for the misses.

Service level tells you whether answered customers waited acceptably. Answer rate (with abandonment) tells you how many you lost entirely. You need both: a great SL on the calls you took means little if a chunk of customers never got through.

Deferred channels

These are voice/chat ideas — email needs its own.

“Answered in 20 seconds” is meaningless for email. Deferred channels need their own service definitions — percentage resolved within the promised time (e.g. 95% within 24 hours). Don’t force a live-channel metric onto a deferred one.

Two centres, same 80/20

Identical score, very different day

Centre A: the slowest-answered caller waited 25 seconds. Centre B: most are instant, but a handful waited eleven minutes. Both report “80% in 20 seconds.” The headline can’t tell them apart.

And if B’s eleven-minute callers gave up before the clock counted them, its answer rate looks better, not worse. One number, two hidden truths — which is why you read SL, the tail and answer rate together.

The takeaway

Know what each measures — and what it hides.

Service level is speed (and 80/20 is just a convention that hides the tail). Answer rate is whether you served them at all (and abandonment rules can flatter it). Use both, set targets that fit your customers, and always check the formula.

Now test yourself ↓

1 / 10

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: two service metrics that sound alike and aren’t

Service level and answer rate are quoted almost interchangeably, but they measure different things. Service level is the percentage of contacts answered within a target time — “80% within 20 seconds” — so it’s about speed. Answer rate is the percentage answered at all, whenever — so it’s about whether you got to them. You need both, because each is silent about something the other reveals.

What service level hides

First, 80/20 is a convention, not a law — the most-quoted target in the industry has no scientific basis, and the right target depends on what your customers tolerate and what the contact is worth, so copying it unthinkingly is how centres over- or under-invest. Second, the average is silent about the tail: hit 80/20 and a fifth of callers waited longer than 20 seconds, but how much longer? A centre where the slowest waited 25 seconds looks identical to one where a few waited ten minutes — and the tail is where the complaints live.

What answer rate hides — and the deferred-channel caveat

Answer rate is closer to what customers actually feel: their call was answered, or they gave up. But it can be gamed, because many systems exclude calls abandoned in the first few seconds — so push waits up, frustrated callers abandon early, they vanish from the denominator, and the answer rate improves even as service worsens. Always know what your formula counts. Used together, service level tells you whether answered customers waited acceptably and answer rate (with abandonment) tells you how many you lost entirely. And remember these are live-channel ideas: “answered in 20 seconds” is meaningless for email, which needs its own definition — percentage resolved within the promised time, like 95% within 24 hours.

The principle to remember: know what each metric measures and what it hides. Service level is speed (and 80/20 just a convention that hides the tail); answer rate is whether you served them at all (and abandonment rules can flatter it). Use both, fit the target to your customers, and check the formula.

Service level vs answer rate