Help Desk Metrics: The 8 KPIs That Actually Matter
First contact resolution, time to resolution, reopen rate, cost per case: the help desk metrics small IT teams and MSPs should track, with formulas.


If all you count is tickets, you are measuring busyness. Not support.
“How good is our support, actually?” is a question managing directors ask their IT and customers ask their MSP. The honest answer is often: “It feels pretty good.” Metrics turn that into something measurable. But not every metric helps, and some even tempt people into the wrong behavior.
From our own work on AI support, we know that the key question is not how fast a ticket is closed but whether the problem is really gone afterwards. Here are the eight metrics that matter for small IT teams and MSPs, with formulas and typical pitfalls.
1. Number of cases
How many requests come in per week or month, in total, per customer, per topic?
- Shows load and trends.
- Per topic is more valuable than the total: if ten printer cases come in every week, a permanent fix is worth it. See Set up a printer with PowerShell.

2. First contact resolution
Formula: cases solved at first contact ÷ all cases.
- Perhaps the most important metric for users: no callback, no second appointment.
- Pitfall: Only count what is really solved, not what was marked “done for now”.
3. Time to first response
How long does it take until someone responds to a request?
- Important for the feeling of “I am being heard”.
- Pitfall: An automatic acknowledgment of receipt is not a response.
4. Time to resolution
How long does it take from receipt to the actual solution?
- Median instead of average, because individual outliers skew the average heavily.
- Separate by priority: a total outage is something different from a new mouse.
5. Reopen rate
Formula: reopened cases ÷ closed cases.
- The counterweight to fast resolution times. If you close cases too early, this is where you see the bill.
- If possible, also count “same problem, new case”.
6. Share of cases solved without a technician
Formula: cases solved without a technician ÷ all cases.
- Self-service, knowledge articles, AI support: anything that takes load off the technician.
- Pitfall: Only count it if the problem is really solved, not if the user gave up.
7. Satisfaction
A short question after closing: “Were you helped?” Thumbs up/down or 1 to 5.

14 days free
IT support that fixes itself.
SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.
Start free trial- Few questions, otherwise nobody answers.
- Read the free-text comments, because that is where the most valuable hints are.
8. Cost per case
Formula: total cost of support in the period ÷ number of cases.
- Staff, tools, share of infrastructure.
- Often forgotten: the user's downtime. Half an hour of waiting for a callback costs something too.
Which metrics tend to do harm
- Only the number of closed tickets per technician rewards fast closing instead of solving.
- Only average call duration rewards short calls instead of complete solutions.
- Too many metrics: nobody looks anymore.
The monthly report on one page
- Metric: Total cases – This month: …; Previous month: …; Target: –
- Metric: First contact resolution – This month: … %; Previous month: … %; Target: … %
- Metric: First response (median) – This month: …; Previous month: …; Target: …
- Metric: Resolution (median, by priority) – This month: …; Previous month: …; Target: …
- Metric: Reopen rate – This month: … %; Previous month: … %; Target: < … %
- Metric: Solved without a technician – This month: … %; Previous month: … %; Target: … %
- Metric: Satisfaction – This month: …; Previous month: …; Target: …
- Metric: Top 3 topics – This month: …; Previous month: …; Target: –
Add one action: Which recurring problem will be solved permanently next month?
For MSPs: metrics as a selling point
Customers often see only the invoice. A short monthly report with response times, topics, and one concrete improvement shows the value of the service, and it also delivers evidence for customer questionnaires, for example on NIS2 or cyber insurance.
How does SuperSupport help with metrics?
With SuperSupport, every chat is also the case, with timestamp, topic, steps carried out, and result. From that you get metrics such as number of cases, topics, and share of cases solved without a technician, with no additional recording. What this looks like for internal IT teams and MSPs is on their respective pages.

Frequently asked questions
Which help desk metrics matter most?
For small IT teams and MSPs, mainly: number of cases, first contact resolution, time to first response, time to resolution, reopen rate, share of cases solved without a technician, satisfaction, and cost per case.
What is first contact resolution?
The share of cases solved at the first contact, with no callback, handoff, or second appointment. Formula: cases solved at first contact divided by all cases. A high rate saves time on both sides.
How do I calculate the cost per case?
The total cost of support in a period (staff, tools, share of infrastructure) divided by the number of cases in the same period. This should also include the users' downtime, which you should at least estimate roughly.
Why is the reopen rate important?
It shows how often a case marked as solved comes back. A high rate means cases are closed too early or the cause was not fixed, which makes fast resolution times misleading.
Which metrics should an MSP report to customers?
Number of cases, response and resolution times compared with agreed times, most common topics, share of cases solved without a technician, and satisfaction, supplemented by notes on where recurring problems can be solved permanently.

14 days free
IT support that fixes itself.
SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.
Start free trial
Nico Haslberger is Co-Founder & CEO of SuperSupport.ai. With years of experience as an IT technician, he knows the problems in IT support first-hand: from overloaded help desks to recurring tickets that slow teams down. That knowledge is built into every feature of the platform today. He makes sure SuperSupport.ai solves exactly the problems he experienced himself for years.
This article was created with AI assistance and editorially reviewed.
Related Articles

Restart a Windows Service Automatically If It Stops
A program feature suddenly stops working because a background service stopped? Find the service and have Windows restart it automatically from now on.

Microsoft 365 Quarantine: How to Release an Email
An important email is stuck in Microsoft 365 quarantine? Here is how to check it, release it, and keep it from happening again.

Remove Local Admin Rights: How to Do It Without Chaos
Admin rights are a security risk, but removing them floods the helpdesk. How SMBs remove local admin rights: preparation, LAPS, Intune, GPO, exceptions.