Measuring
Service level 80/20: what it means and how to set a target for your call centre
By the V4N team · Published · 2 min read
The short answer
Service level is the percentage of calls answered within a set number of seconds. An '80/20' target means 80% of calls answered within 20 seconds. It is a convention many centres start from, not a rule. Average speed of answer can look healthy while the service level fails, so report both, by half hour, and choose your threshold from how long your own callers actually wait before hanging up.
Service level
calls answered within X seconds ÷ calls offered × 100
X is your threshold. 80/20 means 80% answered within 20 seconds.
Service level is the figure most call-centre contracts and dashboards are built around, and the one most often misread. Two things to get right: what threshold you choose, and which other number you read beside it.
Why average speed of answer is not enough
Average speed of answer (ASA) is the mean wait before an agent picks up. A mean can pass while many callers are badly served. Take 100 calls in an hour:
| Calls | Answered after | Share of calls |
|---|---|---|
| 75 | 5 seconds | 75% |
| 25 | 60 seconds | 25% |
ASA is (75 × 5 + 25 × 60) ÷ 100 = 18.75 seconds, which looks fine against a 20-second goal. But only 75% of calls were answered within 20 seconds, so an 80/20 service level has failed. A quarter of your callers waited a full minute and the average hid it.
Choosing a threshold
80/20 is a common starting point, and different kinds of line tolerate different waits. A sales line where a lead goes elsewhere in seconds needs a tighter target than a support line where customers expect to wait a little. For a bank or SACCO member line, where the caller has a payment or a loan in mind, lean tighter.
Do not guess the threshold. Look at your own abandoned calls and note how long people waited before hanging up. If abandons climb after 30 seconds, a 20-second threshold is protecting you; if they climb after 10, it is too generous.
Staffing to the target: offered load
How many agents you need depends on how much work arrives, not on how many calls there are. The measure is offered load, in erlangs:
Offered load (erlangs)
calls per hour × average handle time in seconds ÷ 3,600
If 120 calls an hour arrive and each takes 300 seconds to handle (talk plus after-call work), the load is 120 × 300 ÷ 3,600 = 10 erlangs. That means you need *more* than ten agents free and on the phones, because calls arrive in clumps and not evenly. How many more depends on your target. The Erlang C formula, built into most free workforce calculators, gives the number for a given load and service level.
- Plan by half hour, not by day. The lunch peak and the quiet mid-morning need very different headcounts.
- Allow for shrinkage. Agents on breaks, in training or in meetings are on the roster but not on the phones.
- Include after-call work in handle time. Leaving it out understates the load and overstates your capacity.
What to report
- Service level for each half hour, against the target.
- ASA and the longest wait, beside it.
- Abandonment rate, defined the way we describe in call abandonment rate.
- Agents signed in against agents planned.
Read together, those four lines tell you whether a bad hour was too few agents, a late shift, or an unusual spike in calls.