The power of one — how every agent moves the service level
What service level actually is
The service level is the simplest fairness measure in the contact centre. It’s usually expressed as “80/20” or “80/30” — 80% of calls answered within 20 (or 30) seconds. Other operations use 90/15 or 70/45, but the shape is the same: a target percentage of customers should be answered inside a target number of seconds. Anything answered after that point counts against the target.
This isn’t an abstract management number. It’s a promise the company is making to customers: when you ring us, most of you will be picked up quickly. When the SL is met the customer experience is good. When the SL drops, the customers waiting longer than the target get a worse experience — and a meaningful fraction of them hang up and try later, complain, or stop being customers altogether.
The maths nobody shows you
Here’s a working example. A team of 20 agents is logged in. The expected call volume for the next hour is 200 calls. Average handle time is 5 minutes. The team is staffed pretty much exactly to hit 80% in 20 seconds.
Now imagine one agent steps off the phones unscheduled — they go for a 20-minute extra break, or they spend 20 minutes on a problem that should have been a 2-minute aux code. The team is now 19, not 20. The maths of the queue shifts. Roughly:
Each extra minute one agent is off the phones is one or two more customers waiting longer than 20 seconds.
Twenty minutes of one person off line, on a team of twenty, is the difference between hitting and missing the SL for that hour. Not because that one agent was lazy. Because the queue is finely balanced and small choices compound.
This is the “power of one.” One agent. One choice. One hour. Visibly different customer experience.
It cuts the other way too
The same maths runs in the opposite direction. One agent coming back from break a minute early, taking one extra call instead of finishing the day exactly on schedule, helping a colleague clear a complex wrap-up faster — all of those move the SL the right way. The reason the best agents on the team are noticed by team leaders isn’t that they take more calls per day (they often don’t). It’s that they show up at the right time, they’re consistent, and they make the easy choice when the queue is high.
Being a good colleague to the queue matters as much as being a good colleague to the team. They’re usually the same thing.
What to do when the queue is high
When the queue is up, the team needs more capacity right now. Five things help, in order of impact.
1. Be on a call when it’s your turn. The single biggest contribution any one agent makes during a high queue is being available. If your status should be Ready, make sure it is.
2. Keep wrap-up tight. Wrap-up time is necessary — you genuinely need to finish the note. But the difference between a 30-second wrap and a 90-second wrap, multiplied across 30 calls a day, is real. When the queue is high, finish the note in the rhythm of the call rather than chasing perfect formatting.
3. Defer the non-urgent. Personal admin, optional training, the chat thread that can wait — defer it. Real-time will tell the team when the queue is back under control.
4. Coordinate breaks. If the queue is high and your scheduled break is in 10 minutes, ask real-time whether to take it or shift it. They’re looking at the same data and will give you a clear answer. They’d rather you ask than guess.
5. Don’t panic. Stay accurate. When the queue is high there’s a temptation to rush calls, skip steps, or close cases before they’re finished. That creates callbacks. Callbacks make tomorrow’s queue worse than today’s. The fastest way through a high queue is good, complete calls at a steady pace.
What to do when the queue is low
This is where the “power of one” gets confused. A low queue doesn’t mean you’ve stopped mattering. It means the operation has bought a small amount of time to do work that wouldn’t happen during a busy hour.
The right things to do when the queue is low: finish the wrap-ups you rushed earlier, complete any callbacks you owe, take your break (real-time will be glad you did), do the e-learning module that’s overdue, coach a newer colleague, ask the team leader if anything off-phone needs hands. Use the low queue.
The wrong things to do when the queue is low: sit in idle for 20 minutes, take a long unplanned break, decide that because the queue is low the rest of the day doesn’t matter. The queue ebbs and flows in 15-minute slices. Idle now means you’re needed later.
Three small choices that move the SL more than people realise
The break-back habit. Coming back from a scheduled break 30 seconds early, every break, every day. Over a year, that’s the equivalent of an extra week of phone time per agent. Across a team of 20, it’s 20 weeks. That’s a real customer-experience improvement done quietly, by one habit.
The aux-code honesty habit. Using the right aux code for what you’re actually doing. Aux codes aren’t a way of catching agents out; they’re how the operation knows where the time goes. When the planning team can see that “system issues” ate 12 minutes per agent per day, they can fix the system. When everyone codes it as “wrap-up,” nothing gets fixed.
The escalation-early habit. If a call is going to be long, complicated, or contentious, flag it early to the team leader rather than soldiering on alone for 25 minutes. The team leader can help, can advise, or can take the call. Soldiering on alone burns time and customer goodwill at the same time.
Why this isn’t about pressure
This article isn’t designed to make any agent feel that every minute is being watched. It isn’t. The operation is forecast and staffed with realistic assumptions about breaks, comfort time, queries, wrap-up, training, and the dozen things that fill a day. Nobody expects 100% productivity from any human, ever. What is expected is professional, consistent, well-coded effort across the shift. That’s what the planning model assumes; that’s what the team delivers; that’s how the operation hits its SL.
The point of “the power of one” is the opposite of a guilt-trip. It’s a recognition that the work matters. The maths is the maths: one person being on the floor matters; one person being elsewhere costs the operation. Knowing that is what separates an experienced agent from a new one. New agents think the day belongs to them. Experienced agents understand that for the shift they’re part of something bigger, and small choices compound into customer experience.
The line every team leader should be able to say
“On this team, on this shift, every one of you moves the dial. The numbers prove it. The customers feel it. You don’t need to work harder than you already do. You need to keep doing what you do consistently — on time, on code, on calls. The operation runs on that.”
If your team leader has never said something like that, ask them to. The maths backs it up.
Conclusion
The service level isn’t something the planning team or the leadership team controls. It’s something the agents on the phones move — one at a time, all day. Twenty minutes of one person off line can be the difference between an SL hit and an SL miss. Twenty minutes of one person on line, when it counts, can be the difference the other way. The maths is small. The effect is real. You make a difference.
Pair this with real-time management top tips, sometimes the right thing to do is nothing, and coaching from QA results.