If you do not measure, you do not know. Simple as that. Without KPIs (Key Performance Indicators) for the IT help desk, managing a team is shooting in the dark. Not all KPIs are equally important - IT managers usually focus on 3-4 metrics that really count: MTTR (resolution time), FCR (first contact resolution), SLA compliance. In this article I show 12 KPIs that really matter, with benchmarks for Polish companies, and how to track them in ManageEngine ServiceDesk Plus.
Why measuring KPIs is critical
The IT help desk is a service. And like any service, it must be measurable. Without KPIs:
- You do not know whether your team works efficiently
- You cannot show the business the value of IT (no data for ROI)
- You do not know where the bottlenecks are (is it Help Desk, is it the IT Manager?)
- You cannot negotiate budget - you do not have benchmarks
12 key help desk metrics (table with benchmarks)
| KPI | Definition | Benchmark | Below = problem |
|---|---|---|---|
| MTTR | Mean time to resolve an incident | <4h P1-P2 / <24h P3 | Team overloaded or lacking permissions |
| FCR | % resolved without escalation | >75% | Help Desk needs training |
| SLA compliance | % of tickets resolved on time | >95% | Team has overly ambitious SLA |
| Backlog | % of tickets waiting beyond SLA | <10% backlog | Team cannot keep up, hiring needed |
| CSAT | Customer satisfaction | >4.2/5 or >80% | Poor help desk, action needed |
| MTBF | Mean time between system incidents | >720h (a month) | System unstable, action plan |
| Agent utilization | % of technician time on incidents | 70-85% | <60%: underuse, >90%: burnout |
| First response time | Time to first response | <1h for P1, <4h for P2 | Queue clogged, alerts unclear |
| Cost per ticket | Per-unit cost of a ticket | 50-150 PLN | >200 PLN: team inefficient |
| Ticket volume | Number of tickets per month | ~50-100 per technician/month | <30: team not engaged, >150: chaos |
| Escalation rate | % escalated to Tier 2 | <20% | >30%: Help Desk too weak, >50%: system designed badly |
| Repeat rate | % of tickets from the same user | <15% | >25%: systemic problems, knowledge base unknown |
MTTR, FCR, SLA compliance - the top three
MTTR (Mean Time To Resolve): average time from ticket creation to closure. If MTTR is rising, the team is overloaded, systems are slow, or processes are inefficient. Track MTTR per priority and per category.
FCR (First Contact Resolution): % of tickets resolved without escalation. If FCR is below 60%, the Help Desk needs: (a) more permissions (the ability to change passwords, reset printers), (b) a better knowledge base, (c) training. FCR above 80% is also a sign - the Help Desk is doing too much; some things should go to specialists.
SLA compliance: % of tickets resolved on time. Above 95% is standard, above 98% is excellent. Below 90% says either the SLA is too tight OR the team really cannot keep up. Review SLA every quarter. How to configure SLA for manufacturing environments is described in the article about IT response times for a manufacturing plant.
How to measure KPIs in ManageEngine ServiceDesk Plus
ManageEngine SDP has a KPI dashboard out of the box. Admin -> Analytics -> KPI Reports. You can choose:
- MTTR by priority
- FCR trend (3/6/12 months)
- SLA compliance trend
- Technician performance (MTTR per technician, tickets closed per technician)
- Category performance (which categories have the worst MTTR?)
Export to CSV and publish to Slack / a BI tool daily / weekly. More about the capabilities and costs of ServiceDesk Plus is described in the article about ManageEngine ServiceDesk Plus pricing 2026.
KPI dashboard - what to show the board
For the board (not IT): top 5 KPIs
- SLA compliance % - binary, everyone understands it
- MTTR trend - are we improving or getting worse
- CSAT - are users satisfied
- Cost per ticket - are we cost-efficient
- Ticket volume - is the number of tickets growing or falling (a sign of system health)
FAQ
What is MTTR and how do you measure it?
MTTR (Mean Time To Resolve) is the average time from ticket creation to its complete resolution. Benchmark: under 4h for P1-P2, under 24h for P3, under 5 days for P4. Measure it in ManageEngine ServiceDesk Plus in the Resolution Time analysis report.
What level of FCR (First Contact Resolution) should you target?
FCR is the % of tickets resolved without escalation. Benchmark: above 75% for an IT help desk. If FCR is under 60%, the team lacks sufficient permissions or training. If FCR is above 85%, the Help Desk is doing too much.
What level of SLA compliance is expected?
SLA compliance is the % of tickets resolved on time. Benchmark: above 95% is standard, above 98% is excellent. Below 90% signals an overloaded team or an overly ambitious SLA. Review SLA every quarter.
How do you track KPIs in ManageEngine ServiceDesk Plus?
ManageEngine SDP has a KPI dashboard out of the box: Admin -> Analytics -> KPI Reports. You can build custom reports with any metrics. Export to CSV for weekly/monthly documentation.
Related articles
SLA for a manufacturing plant - how to set IT response times? ManageEngine ServiceDesk Plus pricing 2026 - how much does implementation cost? ITSM for manufacturing - solutions for factoriesWant to implement KPI tracking in your help desk?
Rotech Group will configure a KPI dashboard in ManageEngine ServiceDesk Plus tailored to your business goals.
Book a consultation