Customer support KPIs for small teams
Start with five customer support KPIs: first response time, resolution time, first contact resolution, customer satisfaction and ticket volume by channel. Set targets from your own numbers.
Tools our VAs use for this
Track five things to start: first response time, resolution time, first contact resolution, customer satisfaction (CSAT) and ticket volume by channel. Give each one an owner, read them weekly, and review them properly once a month. Set targets from your own numbers, because there is no official UK benchmark for small teams. Everything else can wait until those five are steady. If someone else handles your support, the same customer support KPIs become the report they send you.
On this page
What customer support KPIs are
A KPI (key performance indicator) is a number you have chosen to judge performance against a goal. In customer support, the goal is usually some mix of speed, getting it right, and how the customer felt about it. The same numbers apply once you have handed support to a virtual assistant.
KPIs versus metrics
Every number your inbox or phone system can produce is a metric: emails received, calls answered, average words per reply. A metric becomes a KPI when you decide it tells you something important, give it a target, and act when it moves. A small team needs many metrics in the background and only a few KPIs in front of it.
Why they matter for a small team
In a small business, support problems tend to hide. The owner hears about the angry customer and not about the many who waited days for a reply. A few tracked numbers show you slow replies, repeat contacts and unhappy customers before they show up as lost sales. They also make delegation possible: you cannot hand support to someone and judge their work fairly without them.
The core support KPIs
The core support KPIs are first response time, resolution time, first contact resolution, escalation rate, CSAT, customer effort score, NPS, abandon rate, ticket volume by channel and cost per resolution. Each KPI below has a plain definition and a way to work it out. Decide up front whether you measure in business hours or clock hours, and write it down, because the answer changes every number.
First response time
The time between a customer's message arriving and the first reply from a person. An automatic "we have received your email" message does not count. Work it out per conversation, then use the median (the middle value) across the week, so one very slow reply does not distort the picture.
Resolution time
The time between the message arriving and the issue being solved, from the customer's point of view. A ticket closed and then reopened by the customer is not resolved. Track the median, and look separately at the slowest conversations, because they are usually where the process breaks.
First contact resolution
The share of issues solved in the first conversation, with no follow-up needed from either side. Work it out as issues solved on first contact divided by all issues, as a percentage. A falling figure usually means replies are missing information, or the person answering lacks the authority or knowledge to finish the job.
Escalation rate
The share of conversations passed to someone else, such as you, a specialist or a supplier. Some escalation is healthy: refunds over a limit or legal threats should reach you. A rising rate tells you the escalation rules, the training or the help articles need work.
Customer satisfaction (CSAT)
A short survey after a conversation asks the customer how satisfied they were. CSAT is the share of responses that rate you satisfied or better, as a percentage. Read the comments as well as the score, and watch the response rate: a score built on a handful of replies moves a lot from week to week.
Customer effort score and Net Promoter Score
Customer Effort Score asks how easy it was to get the issue sorted. Net Promoter Score asks how likely the customer is to recommend you, and subtracts the share who would not from the share who would. Effort is about the support experience; NPS reflects the whole business, including product, price and delivery.
Abandon rate
For phone and live chat: calls or chats where the customer gives up before anyone answers, divided by all calls or chats offered. It is the clearest sign that you are short of cover at certain times of day. Cover for late chats is discussed in round-the-clock live chat support.
Ticket volume by channel
How many conversations arrive each week by email, phone, chat and social messages. Volume is a metric more than a KPI, but every other number needs it: a slower response time in a week with twice the volume means something different from the same slowdown in a quiet week.
Cost per resolution
Total support cost for a period (people, tools, any outsourced service) divided by the number of issues resolved in that period. There is no reliable published figure for UK small businesses, so compare yourself with your own previous months. It matters most when you are deciding how to staff support; our guide to the cost of outsourcing customer service covers that decision.
Which KPIs to track first
A support team of one to five agents should start with five KPIs: first response time, resolution time, first contact resolution, CSAT and ticket volume by channel. Start small and add a number only when you know what you would do if it moved.
A starter set for one to five agents
- First response time: customers notice speed first.
- Resolution time: speed of reply means little if the issue drags on.
- First contact resolution: the best single sign that replies are complete and correct.
- CSAT: the customer's own verdict, with comments that tell you why.
- Ticket volume by channel: the context for every other number, and the basis for cover decisions.
If you only have the time for three, keep first response time, CSAT and volume.
What to leave until later
Leave NPS until you have enough customers for the score to be stable, and treat it as a business number. Leave cost per resolution until your volume and staffing are settled. Leave per-person handle time alone in a small team: it rewards rushing, and you can see the work directly instead.
A one-page KPI scorecard
Copy this table into a spreadsheet. Add a column for each week and a target column once you have your baseline.
| KPI | What it tells you | How to work it out | Owner | Read |
|---|---|---|---|---|
| First response time | How long customers wait for a person | Median time from message arriving to first human reply | Whoever answers support | Weekly |
| Resolution time | How long issues stay open | Median time from message arriving to issue solved | Whoever answers support | Weekly |
| First contact resolution | Whether replies finish the job | Issues solved on first contact divided by all issues, as a percentage | Support lead or owner | Weekly |
| CSAT | How customers felt | Satisfied responses divided by all survey responses, as a percentage | Support lead or owner | Weekly, with comments |
| Ticket volume by channel | How busy each channel is | Count of new conversations per channel | Whoever answers support | Weekly |
| Escalation rate | Whether the rules and training fit | Conversations passed on divided by all conversations, as a percentage | Owner | Monthly |
| Cost per resolution | What support costs per solved issue | Total support cost divided by issues resolved | Owner | Monthly |
Setting targets and reviewing results
Give each KPI one named owner, measure for a few weeks to set a baseline, aim a little better than it, and review the numbers weekly and monthly. A KPI with no owner and no review is just a number on a screen. This is the part most guides skip.
Who owns each number
The person doing the work owns the speed numbers and the volume count: they collect them and explain them. The owner or support lead owns the quality and cost numbers, because those depend on decisions about policy, training and staffing. One name per KPI, written on the scorecard.
How to set a target without a benchmark
There is no official source of customer service benchmarks for UK small businesses, and vendor benchmarks are drawn from their own customers. Measure for a few weeks first to get your baseline. Then set a target a little better than the baseline, and make sure it fits what you promise customers. If you publish a reply time, the internal target should be tighter than the promise; our guide to setting a customer service SLA covers how to word that promise.
How to run a weekly and monthly review
- Weekly, short: read the five starter numbers against last week. Look at the three slowest conversations and any low CSAT comments. Agree one fix.
- Monthly, longer: look at the trend, not the week. Check volume by channel against cover, review escalations, and decide whether a target, a help article, a reply template or the hours of cover need to change.
- Every quarter: ask whether the KPIs are still the right ones.
Numbers tell you where to look; reading real conversations tells you why. A short quality review alongside the KPIs is the subject of our guide to customer service quality assurance.
Where to find the numbers without enterprise software
You do not need an analytics suite. If your help desk, shared inbox or phone system shows when a conversation arrived, when it was first answered and when it was closed, use its built-in reports. If it does not, keep a simple log: one row per conversation, with the channel, time received, time of first reply, time resolved, whether it was solved first time, and whether it was escalated. For CSAT, a single-question survey sent after the conversation is enough. A spreadsheet with those columns produces every number in the scorecard above.
KPIs for an outsourced or VA team
When someone outside your business answers your customers, KPIs stop being a self-check and become the main way you see the work. Most guides assume an in-house team and say nothing about this.
What the team should report back
Ask for the starter set every week, in the same format, with a line of commentary: what moved, why, and what they suggest. Ask for the escalation log and a sample of conversations to read. Agree before they start whether times are measured in business hours or clock hours, and what counts as resolved.
Linking KPIs to the service promise and quality
The KPIs show what is happening; the service level agreement says what was promised; quality reviews show whether the answers were right. Keep the three separate and consistent. If you are weighing up handing support over, our guide on how to hire a VA for customer support covers the hiring steps.
Getting help from a customer service virtual assistant
An Ant Assist customer service VA is one dedicated person, never shared, working your inbox, chat or phone during UK business hours, 9am to 5pm Monday to Friday, with extended hours and weekend cover at additional cost. VAs are recruited, managed and supervised in Ant Assist's own office in Cairo, and the service is UK-managed. Agree the KPIs above, how they are measured and how often they are reported before your VA starts. Cover runs from 20 hours a week up to a full 40-hour VA, from £5 per hour on the introductory rate. Put your hours into the calculator to see the monthly cost.
Support metrics FAQs
Didn't find your answer? Browse more common questions in the Help Center.
Support numbers you can trust each week.
A dedicated customer service VA, from £5 per hour. Book a free 15-minute call.