KPIs and metrics

Setting Realistic KPI Targets for a Phone Team

How to set call centre KPI targets that people can actually reach: start from your baseline, link targets to goals, avoid gaming and review them often.

Call editorial team · Published · 5 min read

Setting a target looks easy: choose a number and tell the team. In practice, a badly chosen target does damage. It can push agents to rush calls, hide problems, or give up because the goal was never reachable. A good target is one the team understands, believes in and can influence.

A manager and a team member discussing a printed chart at a meeting table
Illustrative image

This guide walks through setting targets for a phone team in a way that holds up, and what to do when they stop working. It follows naturally from The Five KPIs a Small Phone Team Needs and from the catalogue in Call Centre KPI List.

Start with a baseline

Before setting any target, find out where you are. Collect at least four to eight weeks of data for the measure, and look at more than the average.

Building a baseline

  1. CollectGather several weeks of the measure, split by day and hour where you can.
  2. CleanRemove outliers caused by outages, closures or one-off events, and note them.
  3. DescribeWrite down the typical value, the strongest and weakest weeks, and the spread.
  4. ExplainNote what drove good and bad weeks, such as staffing or a campaign.
  5. ShareShow the team before you propose any target.

A baseline also tells you whether a target is realistic. If your wait is long every Monday morning because staffing is thin, a target that ignores Mondays cannot be reached by effort alone.

A target that does not serve a goal becomes a number to chase. For each measure, write one sentence: "We want X so that customers can Y." For example, "We want fewer abandoned calls so that people with urgent issues reach us." That sentence guides the target, and it helps when you need to decide whether a trade-off is worth it.

Connecting targets to purpose

  • AccessTargets for answer rate, wait and abandon rate protect the customer's ability to reach you.
  • ResolutionFirst-contact resolution and repeat calls protect the outcome of the call.
  • ExperienceSatisfaction and effort measure how the customer felt about it.
  • EfficiencyHandle time and wrap-up protect cost, but only after the others are healthy.
  • PeopleSchedule adherence and workload protect the team and keep the other targets possible.

Notice that efficiency comes after the others. Cost targets should follow service targets, not overrule them.

Choose the shape of the target

A target does not have to be a single line. Several shapes work better in practice.

Ways to express a target

Single figureRange or direction
Example"Answer within a fixed number of seconds""Keep waits inside this band, and improve the slow hours"
StrengthSimple to communicateReflects real variation
WeaknessEvery miss feels like a failureNeeds explanation
Best forMature, stable processesNew or small teams, noisy data
RiskGaming around the lineVagueness if left undefined

For small teams, a range plus a direction ("stay within this band; reduce the worst hour") is usually kinder and more accurate. Small volumes produce noisy data, and one bad day should not turn a good month red.

For a service-level style target, see The 80/20 Service Level for how the idea works and why it needs context.

Balance the set

Any target can be met in a way that harms something else. Shorter handle time can mean rushed calls. A higher answer rate can mean shorter conversations. A lower transfer rate can mean agents holding calls they cannot solve. Protect against this by pairing each target with a counterweight.

If you targetPair it with
Handle timeResolution or repeat calls
Speed of answerSatisfaction or effort
Transfer rateResolution
Outbound call volumeQuality of conversations or outcome
OccupancyWorkload and wellbeing signals

Keep the total number of targets small. Four or five are enough to guide a team; ten or more become noise. Our guide to Average Speed of Answer and Occupancy and Utilisation shows how two common targets can pull in opposite directions.

Involve the team

People meet targets they helped shape. Ask the team what they think is reachable, what stops them today and what support they need. Agents know where the system gets in their way. A target set after that conversation is far less likely to be treated as a threat.

A hypothetical example: a small support team wants a faster answer to calls. The manager proposes a tight number. In discussion, agents point out that the callbacks list is crowding out live calls during the morning peak and that the break schedule leaves one person on the phones at lunch. The team agrees a more modest wait target, moves breaks and sets a separate window for callbacks. The result is a goal they all believe in plus changes that make it achievable.

Watch for gaming

When people are measured, they respond. Most of that is healthy, but some of it is not. Typical signs of gaming include calls ended early, tickets closed without resolution, callers transferred to meet a talk-time goal, and wrap-up states used to avoid new calls.

Review and adjust

Targets age. A new product, a seasonal peak or a change in staffing can make last quarter's goal wrong. Review each target on a fixed schedule, such as every quarter, and ask four questions: is it still tied to a goal, did we reach it, how, and what did it cost? Change it openly, with a reason, so the team trusts the process.

Target review questions

  • Is the goal behind the target still the right goal
  • Has the baseline moved because of staffing, volume or product changes
  • Did meeting it cause any side effects
  • Does the team understand and accept it
  • Should it be tighter, looser, or retired

Tracking targets in Call

Call's Reports area shows half-hour intervals with a service-level projection, agent scorecards and arrival patterns, so you can check the baseline by hour and see which hours are hard. Wallboards put a few tiles on a floor display, and saved reports can be scheduled by email to the team lead for the weekly review. Quality scorecards and call summaries give you the quality counterweight to speed. See Call Analytics Dashboard for what the analytics views offer.

Frequently asked questions

How many targets should a small team have?

Four or five. More than that dilutes attention and makes balancing harder. Start with a few and add one only when you have a decision it supports.

Should targets be the same for every agent?

Team targets are usually fairer. If you use individual ones, adjust for the type of calls handled and the shifts worked, and focus on coaching rather than ranking.

Where do I find a benchmark?

Published industry numbers are rarely comparable to your set-up. Use them only as loose context, and rely on your own baseline for decisions.

How often should targets change?

Review quarterly, and change when the goal, volume or staffing changes. Changing too often confuses the team; never changing leaves targets stale.

What if we keep missing a target?

Check the baseline and capacity before blaming people. A target that is missed week after week may be unrealistic, or it may expose a staffing or process gap worth fixing.

Can targets be too easy?

Yes. A target that is always met teaches nothing. Look at whether the baseline has improved and raise the goal, or move attention to a different measure.

Track your team's results against targets in Call

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

Related guides