A green dashboard is of little use if it doesn’t track the right metrics and key performance indicators (KPIs). Whether an IT service team serves internal users (i.e., employees) or external clients, the challenge is the same: choosing from a multitude of measurements to identify the ones that connect IT performance to the organization’s strategic objectives.
What Are IT Service KPIs and Metrics?
IT service KPIs and metrics are quantitative measurements used to evaluate IT service operations. Metrics record how activities and processes perform—ticket volume and response times, for example—while KPIs frame these metrics in terms of progress toward goals, such as tying first contact resolution rate to reduced support costs.
Key Takeaways
- IT service management KPIs connect performance to desired business outcomes, such as boosts in revenue, productivity, or customer retention.
- KPIs operate as a system; optimizing one in isolation can create or mask problems in another.
- Complete KPI measurement requires integrating data from multiple sources.
Why Do IT Service KPIs Matter?
A hospital ER doesn’t measure success by how many patients pass through; it tracks outcomes. IT service KPIs work the same way, measuring whether problems are actually solved. After all, a service desk can close thousands of tickets a month and still leave customers frustrated. Or, a server can show 99.9% uptime while users struggle with slow applications every day.
Consistent measurement provides:
- Visibility into IT service performance problems and successes
- Accountability for delivering on commitments
- Alignment between IT operations and business outcomes
- Early warning when trend lines indicate potential issues
- Capacity planning to match resources with demand
- Continuous improvement by using results to inform process changes
14 Critical IT Service Metrics and KPIs
The following 14 metrics and KPIs span experience, speed, quality, cost, and capacity—the dimensions that most influence IT service effectiveness. They apply whether an IT team serves internal users or external clients, both of whom can be considered customers.
-
Customer Satisfaction Score (CSAT)
CSAT measures the percentage of customers who participate in a short post-interaction survey are happy with a specific service or experience. A high score generally indicates that issues are being resolved competently and communication is clear, while a declining score may point to problems with solution quality, response times, or how well technicians set customers’ expectations. One caveat: CSAT can skew toward extremes, since the most satisfied and frustrated customers are the ones most likely to respond to the survey. Tracking it alongside other response rates helps verify that results reflect the broader customer base.
The formula to calculate CSAT is:
CSAT = (Number of positive responses / Total number of responses) × 100
-
Net Promoter Score (NPS)
NPS assesses the likelihood of customers recommending an organization’s IT services to others. Unlike CSAT, which reflects satisfaction with a single interaction, NPS captures broader sentiment about IT service over time. Like CSAT, NPS is based on customer surveys, through which respondents rate their likelihood to recommend the company’s IT services to others. Those who score 9 or 10 are considered “promoters,” scores of 7 or 8 are “passives,” and scores of 6 or lower are “detractors.”
The NPS formula subtracts the percentage of detractors from the percentage of promoters:
NPS = Percentage of promoters – Percentage of detractors
A rising NPS suggests that IT service is building trust and loyalty; a falling score may signal repeated incidents, poor communication, inconsistent service quality, or other frustrations.
-
Return on Investment (ROI)
IT services represent a significant operational cost, and leadership needs to know if that investment is paying off. ROI, also known as rate of return, measures whether the money a company spends on IT service management is generating value for the organization in the form of reduced downtime, increased productivity, or better outcomes. (The challenge is quantifying benefits in financial terms.) In fact, ROI becomes more credible when tied to operational metrics, such as reduced resolution time or fewer escalations.
The formula to calculate ROI is:
ROI = [(Total benefits – Total costs) / Total costs] × 100
-
Average First Response Time (AFRT)
AFRT measures how long it takes IT to acknowledge a customer’s issue, excluding automated responses. A slow first response can leave customers wondering if their issue was ever seen, damaging trust. However, optimizing for speed alone can backfire. If first responses are fast but don’t contain any real information—customers may feel brushed off. Pairing this metric with average resolution time (next) and satisfaction scores can shed light on the effectiveness of quick responses.
The formula to calculate AFRT is:
AFRT = Sum of first response times / Number of submitted tickets
-
Average Resolution Time (ART)
ART calculates how long it takes it takes to fully resolve an issue, from when a support ticket is first opened until the problem is corrected. A low ART means most problems are fixed quickly, enabling agents to handle more tickets and reduce backlogs. A high ART could signal that support staff is overwhelmed or needs better training, tools, or documentation. Because ART reflects more than just agent work—it also includes approvals, dependencies, and time waiting on customers or vendors—it becomes most actionable when segmented by request type, priority, or wait state.
The formula to calculate ART is:
ART = Time to resolve all tickets / Number of resolved tickets
-
First Contact Resolution (FCR) Rate
FCR measures the percentage of support tickets resolved on the first interaction with a customer, without the need for callbacks, escalations, or follow-ups. High FCR rates indicate that front-line support is equipped to handle issues quickly and effectively, which improves customer and employee satisfaction alike. A low FCR rate may indicate training gaps, weak knowledge resources, or unclear intake processes.
The formula to calculate FCR rate is:
FCR = (Number of resolved incidents on first contact / Total incidents) × 100
-
Average Handle Time (AHT)
AHT measures the average time a support agent spends actively working with customers. This includes interacting on live calls or chats, hold times to research an issue, and after-call tasks, such as updating the ticket or initiating follow-up actions. Because AHT can be reduced by rushing, it should be analyzed in context with quality metrics like FCR and CSAT. A short handle time that leads to repeat contacts or unresolved issues isn’t an efficiency gain—it’s a cost shift.
The formula to calculate AHT is:
AHT = (Live engagement time + Hold time + After-call tasks) / Total number of calls
-
Mean Time to Resolution (MTTR)
So many R’s, so little time. Depending on the source, the “R” in MTTR can stand for resolution, recovery, or repair. As a resolution metric, MTTR measures the average number of times it takes to resolve an incident once work gets underway. It reflects team efficiency and coordination across support tiers, or the lack thereof.
MTTR is a subset of mean time to recovery, in which the clock begins ticking when an issue is first reported. And as a repair metric, it measures active repair time that, unlike AHT, excludes wait times and handoffs; it is often more relevant for hardware and infrastructure teams.
The formula to calculate MTTR, where the “R” means resolution, is:
MTTR = Total time to resolve all incidents / Total number of incidents
-
Ticket Resolution Rate
Ticket resolution rate measures the percentage of support tickets that were closed during a specific period. This throughput metric helps determine how well the service desk is keeping pace with ticket volume. A consistently low rate may indicate inadequate staffing or training, process bottlenecks, or an influx of complex issues. However, a high rate isn’t necessarily good news—tickets closed prematurely or without proper resolution will show up later as reopens or repeat contacts.
The formula to calculate ticket resolution rate is:
Ticket resolution rate = (Number of resolved tickets / Total number of tickets) × 100
-
Ticket Volume
Ticket volume is a simple demand signal that counts the number of support requests filed over a given period. A high ticket volume relative to the business’s size may suggest that customers need more self-support options, better training, or upgraded technology.
The formula to calculate ticket volume is:
Ticket volume = Total number of support tickets received during a specific period
Because larger organizations naturally generate more tickets, measuring tickets per customer or per employee can be more informative than raw volume. The formula to calculate tickets per customer is:
Tickets per customer = Total number of tickets / Total number of customers
-
Escalation Rate
Escalation rate reveals the percentage of tickets that are not resolved on first contact and must be reassigned to a higher support tier. High escalation rates increase resolution time and often frustrate customers who have to re-explain their issue. Reasons for a rising escalation rate may include front-line staff lacking the training, tools, or authority to resolve common issues. It can also reflect poor ticket routing or overly rigid tiering policies.
The formula to calculate escalation rate is:
Escalation rate = (Number of tickets escalated / Total number of tickets received) × 100
-
SLA Compliance Rate
SLA compliance rate measures the percentage of tickets resolved within the time frames specified in a service-level agreement. SLAs often carry contractual weight, and noncompliance can result in penalties, strained relationships, or lost business. Tracking SLA compliance by priority level or ticket type is a best practice for identifying where failures are concentrated. A team may hit overall targets yet consistently miss commitments on high-priority issues—a pattern that won’t show up in an aggregate number.
The formula to calculate SLA compliance rate is:
SLA compliance rate = (Number of tickets resolved within SLA / Total number of tickets with SLA) × 100
-
Cost per Request
Cost per request measures how much money is spent, on average, to resolve support tickets. By connecting IT operations to financial performance, cost per request can uncover inefficiencies as well as validate investments in automation, self-service portals, and training.
That said, cost per request can be misleading on its own. Closing tickets prematurely or rushing through interactions might lower this KPI, but service quality will likely suffer. For a fuller picture, pair cost per request with CSAT and ticket resolution rate.
The formula to calculate cost per request is:
Cost per request = Total IT support operating costs / Total number of tickets
-
Capacity Utilization
Capacity utilization evaluates the proportion of IT service resources, such as staffing, scheduling, software licenses, and tools, that are in active use. This sustainability metric helps pinpoint mismatches between supply and demand and is best paired with response and resolution time KPIs. Utilization that’s too low suggests overstaffing or inefficient workflows, while utilization that’s consistently too high creates backlogs, delays, and burnout risk.
The formula to calculate capacity utilization is:
Capacity utilization = (Capacity used / Total capacity available) × 100
How Are IT Service KPIs Used?
With the right KPIs in place, the next question is how to apply them. In practice, IT service teams use them in four main ways:
- Benchmarks: Comparing performance against industry standards or historical baselines helps gauge progress and set realistic targets (though definitions must match for comparisons to be meaningful).
- Dashboards: Real-time, role-based dashboards provide an instant view of queue health and emerging issues. Service delivery managers can also use them to monitor SLA risks and trends.
- Reporting: Weekly, monthly, and quarterly reports add context that support service reviews, audits, and cross-functional accountability.
- Planning: KPI trends help justify staffing levels, prioritize automation and knowledge investments, and build the case for budget.
Tools That Track IT Service KPIs
IT service data rarely lives in one place. For many IT service teams, monitoring KPIs requires them to pull data from multiple sources:
- ITSM platforms capture ticket events, time stamps, and user interactions to evaluate KPIs on FCR rate, SLA compliance, and escalation rate.
- Monitoring and observability tools track system uptime and feed MTTR calculations.
- Customer experience and survey tools gather CSAT and NPS data.
- Financial and cost-tracking tools connect ITSM data with back-end financial systems to evaluate ROI and cost per IT request.
- Business intelligence and analytics tools pull data from ITSM platforms, observability tools, and financial systems for advanced reporting.
- Workforce management tools track staffing levels and feed capacity utilization analysis.
- ERP systems tie these (and other) tools together, centralizing data for a unified view of IT service performance.
Track and Improve IT Service Metrics With NetSuite ERP
The most valuable IT service KPIs connect performance to business outcomes, but calculating them involves combining data that typically lives in separate systems. Without an integrated platform like NetSuite ERP for IT Services, IT leaders have to switch between tools, manually reconcile inconsistent data, and tie operational metrics to financial results. NetSuite’s ERP solution brings financial, operational, and workforce data together in a single cloud-based platform. Real-time dashboards display metrics and KPIs from across the business so IT leaders can see the true costs of service delivery—including labor, tools, downtime, and SLA performance—alongside revenue and profitability. That visibility supports better resource utilization, more accurate project planning, and faster decisions supported by what the numbers say.
IT service management metrics and KPIs help demonstrate IT’s value to the business. The key is selecting the right ones—including customer satisfaction, ART, escalation rate, and capacity utilization—and integrating the data sources needed to track them accurately. Among the payoffs: a green dashboard that’s also meaningful.
IT Service Metrics and KPIs FAQs
What are the core key performance indicators for IT support?
Core IT support key performance indicators (KPIs) fall into five broad categories—volume, speed, quality, cost, and experience. Because KPIs in one category can influence another, they work best when tracked together. For example, a decrease in average handle time can hurt first contact resolution if issues aren’t fully addressed.
What KPIs should be included in an IT service dashboard?
Core key performance indicators (KPIs) and metrics include ticket volume, average first response time, mean time to resolution, first contact resolution, and escalation rate.
What data sources do you need to report IT service KPIs?
Data sources include operational data from IT service management platforms, uptime data from monitoring and observability tools, customer feedback from surveys, and financial data from HR and accounting systems. ERP systems can centralize these sources for unified reporting.
