Contact center

Designing Service Levels for Phone Support Teams

How to design service levels for phone support: choose measures, set targets you can meet, write them as promises, report honestly and review them over time.

Call editorial team · Published · 6 min read

Service levels are easy to write and hard to live with. A sentence in a contract or a banner on a website promises that calls will be answered quickly, and then a Monday morning arrives with half the team absent. The aim of good design is a target that reflects what customers need, what the team can do and what you can measure without fuss.

A team lead pointing to a service chart on a screen while colleagues watch
Illustrative image

This article is about designing the whole framework. For a detailed look at the most widely used measure, see Service Level Explained: The 80/20 Target and Its Limits and for choosing numbers, Setting Realistic KPI Targets.

Start from the caller's point of view

Before choosing any numbers, ask what a caller actually wants from a phone line. Most want three things: to get through without a long wait, to have the problem solved in one conversation, and to be told honestly what happens if it cannot be. A service level that does not map to one of those three is probably a measure for the team's benefit, not the customer's. That is not wrong, but it should not be sold as a promise.

Ask the team, too. Agents know which waits provoke complaints, which times of day are overloaded and which promises are impossible. A short workshop with a few agents and a supervisor often produces a better draft than a spreadsheet alone, and it gives the team a stake in the result. Combine what you hear with a few weeks of call data and complaints, and you have the raw material for sensible targets.

Service levels, targets and agreements

The terms are often mixed up, so settle them first.

TermMeaningExample in plain words
Service level (measure)A figure describing what happenedThe share of calls answered within a set number of seconds
Target (objective)The figure you aim for internallyAnswer most calls within the set time
Service level agreementA commitment made to a customer or another teamA written promise of response times for a contract
Alert thresholdA limit that triggers actionA longest-wait limit that notifies a supervisor

Internal targets can be ambitious. External agreements should be modest, because breaking them has consequences. Keep the two separate so that you do not promise your stretch goal.

Choose what to measure

Callers experience a service in three moments: getting through, getting help and getting a follow-up. Pick a measure for each moment and resist adding more.

Measures that map to the caller's experience

  • Getting throughSpeed of answer, abandoned calls and the share of calls answered. See Average Speed of Answer and Answer Rate and Abandonment Rate.
  • Getting helpFirst-call resolution and, where relevant, transfer rate.
  • Follow-upTime to return a callback or reply to a message, and callback completion.
  • ExperienceA simple satisfaction question after the call.

Set targets you can actually meet

Look at what you do today before choosing a number. If your current answer speed varies widely, a tight target is a fantasy. Use several weeks of data, including the bad ones, to see the range. Then pick a target slightly better than the middle, and review it after a few weeks. Remember that the cost of a target rises quickly as it tightens: the last few points of speed need disproportionately more staff. Erlang C Explained Without the Math Headache shows why.

State what is covered

A service level applies to specific hours, channels and call types. Say so. A promise to answer within a set time during opening hours is different from one that includes weekends. Urgent lines may have a stricter target than general ones. Different queues can have different targets, as long as the reasons are clear: a sales line might aim for speed, a technical line for resolution. Write the details into one page so that nobody has to guess.

Writing a service level as a promise

  1. ScopeWhich line, queue or channel, and which hours.
  2. MeasureWhat is counted, from when to when, and what is excluded.
  3. TargetThe figure and the period over which it is judged.
  4. ExceptionsOutages, force majeure and unusually high volume.
  5. ReportingWho reports it, how often and to whom.

Avoiding the traps

Any measure can be gamed. Agents who are judged on short calls will end them too soon. A team judged only on answer speed may let simple callbacks pile up. Teams measured on abandoned calls may hold callers at the greeting with a long message. Protect against this by pairing measures: speed with resolution, handle time with quality, and by reading calls, not only numbers. Reducing Average Handle Time Without Hurting Quality gives an example of the balance.

Different callers, different targets

Not every call deserves the same speed. Callers with an urgent fault, a safety issue or a time-limited payment problem need a faster response than someone asking about opening hours. Consider separate queues or priority for urgent categories, and tell the team how priority works so that nobody is surprised. Make sure the extra speed for one group does not starve the rest; check the longest waits in every queue, not only the average. When in doubt, favour simplicity: two or three clear tiers are easier to explain and to staff than a dozen special cases.

Written channels need their own targets. An email or message does not require an answer in seconds, but it does need a predictable reply time. Setting one stops customers from phoning to chase, which adds to your call load. Response Times for Messages vs Calls explains how to set them.

Report in a way people use

A service level that is only in a quarterly report does nothing. Show the current position where the team can see it: a wallboard, a daily summary, an alert when thresholds are crossed. Supervisors need a live view; managers need a weekly view; executives need a monthly one. Keep the figures consistent across all three. What Contact Center Supervisors Should Monitor and Building a Call Analytics Dashboard offer layouts.

Who needs what

Live viewReview
SupervisorCalls waiting, longest wait, agents availableDaily and weekly results by queue
Team leadAlerts and abandoned callsCoaching priorities and trends
ManagerNot usually needed in real timeTargets met, causes of misses, staffing needs

Review and change the targets

Business changes. A new product, a new market or a new channel changes demand and expectations. Review each service level at least twice a year: is it still the right measure, the right figure and the right scope? If you keep missing the target, decide whether to add capacity, reduce demand or change the target. Do not leave a missed target in place and pretend it is fine; it teaches the team that numbers are decoration.

Service levels in Call

In Call, each queue has a target: the share of calls to answer, within a number of seconds, plus alert limits for longest wait, number of calls waiting and abandon rate. The Queues & SLA screen shows service level, average speed of answer, handle time, waiting and abandoned calls for a chosen window, and wallboards can put selected figures on a floor display. See Setting Up Call Queues: Members, Priority and Overflow and Reading the Analytics Screens in Call.

Frequently asked questions

What is a good service level target?

It depends on your callers, staffing and cost. Use your own data to find what is achievable, start with a modest figure and tighten gradually.

Should every queue have the same target?

Not necessarily. Urgent or revenue-critical queues can have stricter targets, as long as you can staff them and the reason is clear.

How often should we report service levels?

Show live figures to supervisors, daily or weekly summaries to team leads and monthly summaries to managers, using the same definitions throughout.

What if we cannot meet the target?

Find the cause: staffing, demand, handle time or scheduling. Then fix the cause or change the target, but do not ignore the miss.

Do service levels include callbacks?

They should. A callback promise is part of the service, so measure how quickly and reliably callbacks are made.

Set queue targets and alerts for your phone team in Call

In the demo console you can try incoming calls in a simulation.

Related guides