The Five KPIs a Small Phone Team Needs on One Dashboard
A small phone team does not need thirty metrics. Learn which five to put on one dashboard, how to read them together and how often to review them.
Large contact centres have analysts, dozens of reports and several screens on the wall. A team of three to ten people needs none of that. It needs to know, quickly and honestly, whether callers are being answered, how long they wait and whether their problems get solved. Five numbers can tell you most of that.

This guide proposes a starter set, explains how the numbers interact, and offers a rhythm for reviewing them. If you want a longer catalogue to choose from later, see Call Centre KPI List.
Principles for choosing metrics
Before the list, a few rules help you decide what belongs on the dashboard at all.
- Every number should lead to a decision. If nobody would change anything whatever the value, remove it.
- Mix speed and outcome. A dashboard full of speed measures encourages rushing. Include at least one measure of result.
- Keep it readable. Five figures fit on a phone screen. If you need to scroll, you have too many.
- Use your own history as the benchmark. Your trend matters more than another company's average.
- Show who owns each number. A metric without an owner is decoration.
The five KPIs
Here is a starter set. You may swap one or two to suit your business, but keep a balance between volume, speed, loss, resolution and customer view.
The starter set
- Answer rateCalls answered by a person or an AI agent divided by calls received. It says whether people get through.
- Speed of answerHow long callers wait before someone picks up. It says how that feels.
- Abandon rateCalls where the caller hung up while waiting. It says how many you lose.
- First-contact resolutionIssues solved without a second contact. It says whether the work works.
- Customer feedbackA short satisfaction or effort measure. It says how customers see it.
Each has a longer guide: Answer Rate and Abandon Rate, Average Speed of Answer, First-Call Resolution, CSAT After Calls and Customer Effort Score.
Reading them together
Single numbers mislead. The value of the set is in how the five move relative to each other.
| Pattern | What it often means |
|---|---|
| Speed of answer rises, abandon rate rises | Not enough capacity at that hour; look at staffing and call volume. |
| Speed of answer is fast, resolution falls | Agents may be rushing; check handle time and notes. |
| Answer rate is high, feedback is low | Calls are answered but the experience is poor; check transfers and repeats. |
| Abandon rate high only at certain hours | A schedule problem; compare with arrival patterns. |
| Everything steady, feedback falls | Something outside the numbers has changed, such as a product issue; read the comments. |
Whenever a number changes, look at one other number before drawing a conclusion. A quick glance at all five is usually enough to tell a staffing issue from a quality issue.
Where the numbers come from
A small team should not need a data project. Use what your phone system and your notes already record.
Where to find each number
| Phone system | Your own notes | |
|---|---|---|
| Answer rate | Calls received and answered, from the call log | Hard to track by hand |
| Speed of answer | Wait time recorded by the queue | Rough estimate only |
| Abandon rate | Callers who left before an answer | Tally of missed calls |
| Resolution | Repeat contacts from call history | Outcome code on each call |
| Feedback | End-of-call question or follow-up | Short survey link |
If you cannot measure one reliably, start with a manual tally for a month. A rough number you trust is better than a precise number nobody believes, and you can automate it later.
A review rhythm that works
How often you look matters as much as what you look at. A simple rhythm for a small team:
Daily, weekly, monthly
- Daily glanceCheck yesterday's answer rate, abandon rate and wait. Only act if something is unusual.
- Weekly huddleSpend fifteen minutes on the five numbers, one cause behind any change and one action for next week.
- Monthly reviewLook at trends over several weeks, check whether your actions worked and decide whether to change a target.
- Quarterly resetAsk whether the five are still the right five, and whether anything should be added or dropped.
A hypothetical week on the dashboard
Picture a six-person veterinary reception team. On Monday the dashboard shows a normal answer rate but a longer wait than usual and a few more abandoned calls in the first hour. At the huddle they look at arrival patterns and see a spike at opening time after the weekend. The action is small: one person moves their break, and the opening-hour message mentions the online booking option. By the following Monday the wait is back to normal, and the abandon rate has eased. Nobody needed a long report; five numbers and fifteen minutes were enough.
The same example shows why feedback belongs on the board. If the wait improves but customers say they still cannot get a straight answer, the team has solved the wrong problem. Reading comments alongside the numbers keeps the conversation honest.
Pitfalls to avoid
Even a short list can go wrong. Watch for these:
- Targets without context. A target set from nowhere creates stress and gaming. See Setting Realistic KPI Targets.
- Ranking agents by one number. Speed measures reward the wrong behaviour, and small teams make comparisons unfair because call mixes differ.
- Ignoring small volumes. With few calls, one long wait moves the average. Use ranges and read the individual calls.
- Adding metrics each time something goes wrong. Fix the problem, but resist the urge to add a permanent number for every incident.
- Forgetting outbound. If you make calls too, add one or two outbound numbers on a separate view; Outbound Call Metrics explains which.
Dashboard readiness check
- Each number has a plain definition written on the page
- Each number has an owner
- The dashboard fits one screen
- The team knows where to find it
- A weekly slot is in the calendar
- You know which decision each number supports
Building this in Call
Call's Reports area groups half-hour intervals, agent scorecards, arrival patterns, a report builder, saved and scheduled reports and wallboards. The wallboard lets you create a named board, choose which tiles it shows (calls waiting, longest wait, service level, agents ready, handled today and abandon rate), and put a message across the top. That covers speed and loss on a floor display. Saved and scheduled reports can be sent by email, which suits the weekly huddle. Resolution and feedback are usually taken from call history and your own follow-up. For a closer look, read Call Analytics Dashboard.
Frequently asked questions
Why only five metrics?
Because a small team can act on five. More numbers dilute attention, and the extra ones are rarely used for decisions. You can add more later when a specific question needs them.
Can I swap one of the five?
Yes. Teams with appointments might replace speed of answer with booking completion, for example. Keep a balance of volume, speed, loss, resolution and customer view.
How often should the dashboard be updated?
Daily is enough for most small teams. A live wallboard helps during busy periods, but decisions about trends need days or weeks of data.
Should agents see the numbers?
Yes, team figures at least. Showing the team's results and discussing them together builds ownership. Individual comparisons need more care and context.
What if I cannot get one number automatically?
Track it by hand for a month, using a simple tally. Once you know it matters, find a way to automate it.
How do I handle seasonal peaks?
Compare with the same season in earlier years where you can, and note peaks on the dashboard so the team does not read them as failures. A short note beside a spike, such as "holiday weekend" or "new product launched", saves a lot of guessing later. See Seasonal Peaks in the Contact Centre.