If you run an IT support team, you’ve probably been asked to prove service quality with data — but picking the right metric is harder than it sounds. CSAT, CES, and NPS each measure something different, and using the wrong one (or only one) gives you an incomplete picture. This guide breaks down how each metric works, what it actually tells you in an IT support context, and how to decide which combination makes sense for your team.
What Each Metric Measures
Before comparing them, it helps to understand what problem each metric was designed to solve. They come from different research traditions and answer fundamentally different questions.
Customer Satisfaction Score (CSAT)
CSAT measures how satisfied a user was with a specific interaction — usually a resolved ticket, a service request, or a support call. The survey is sent immediately after the interaction closes, while the experience is still fresh.
The standard question is: “How satisfied were you with the support you received?” Users respond on a scale, typically 1–5 or 1–10. The score is calculated as the percentage of respondents who selected the top one or two ratings.
Formula: (Number of satisfied responses ÷ Total responses) × 100 = CSAT %
For example, if 80 out of 100 respondents rated the interaction 4 or 5 out of 5, your CSAT is 80%.
CSAT is highly actionable at the ticket level. A low score on a specific ticket tells you exactly where something went wrong, and you can tie it to an agent, a category, or a process. The limitation is that it only captures the moment — it doesn’t tell you how users feel about IT overall, or whether they’d recommend your services.
Net Promoter Score (NPS)
NPS measures loyalty and overall sentiment toward your IT department — not a single interaction, but the relationship over time. It was originally designed for customer-facing businesses, but IT teams have adapted it to measure internal user perception.
The standard question is: “On a scale of 0–10, how likely are you to recommend IT support to a colleague?” Respondents are grouped into three categories: Promoters (9–10), Passives (7–8), and Detractors (0–6).
Formula: % Promoters − % Detractors = NPS (ranges from −100 to +100)
NPS is typically sent on a recurring schedule — quarterly or biannually — rather than after individual tickets. It captures cumulative experience across many interactions and touchpoints. A low NPS tells you that users broadly distrust or feel frustrated by IT, even if individual CSAT scores look acceptable. The weakness: it’s not diagnostic. A score of +20 doesn’t tell you what to fix.
Customer Effort Score (CES)
CES measures how much effort a user had to put in to get their issue resolved. It was introduced by the Corporate Executive Board in 2010 and has strong predictive validity — research consistently shows that high-effort experiences drive dissatisfaction more reliably than low-effort experiences drive loyalty.
The standard question is: “The IT team made it easy for me to resolve my issue.” Users rate their agreement on a scale (commonly 1–7, where 7 = strongly agree). CES is the average of all responses.
Formula: Sum of all scores ÷ Number of responses = CES
In an IT support context, CES is particularly powerful because effort is a real pain point. Users don’t just want their issue fixed — they want it fixed without having to chase tickets, repeat themselves, or navigate a confusing portal. A high CES means users found the process smooth. A low CES is a direct signal that your processes, not just your agents, need attention.
CSAT vs CES vs NPS for IT Support: Key Differences at a Glance
| Metric | What it measures | Survey timing | Scale | Best for |
|---|---|---|---|---|
| CSAT | Satisfaction with a specific interaction | Post-ticket / post-interaction | 1–5 or 1–10 | Agent performance, ticket quality |
| CES | Ease of getting an issue resolved | Post-ticket / post-interaction | 1–7 (agreement scale) | Process improvement, self-service friction |
| NPS | Overall loyalty and perception of IT | Periodic (quarterly, biannual) | 0–10 (promoter scale) | Strategic IT perception, leadership reporting |
How Each Metric Applies Specifically to IT Support
Where CSAT Fits in IT Support
CSAT is the workhorse of IT support measurement. Most ITSM platforms — ServiceNow, Freshservice, Jira Service Management, and others — include built-in CSAT surveys that trigger automatically when a ticket is closed. This makes CSAT easy to implement and maintain at scale.
Use CSAT to monitor agent performance, identify low-quality resolutions, and track improvement over time after training or process changes. It’s also the right metric for SLA reporting to business stakeholders who want to know whether users are happy with IT’s responsiveness.
The main risk with CSAT in IT is response bias. Users who had a terrible experience often don’t bother responding — they just complain informally. And users whose issue was resolved correctly may rate it 5/5 even if the process was frustrating. This is where CES fills a gap.
Where CES Fits in IT Support
CES is arguably the most underused metric in IT support — and potentially the most valuable. IT users care deeply about effort. Being transferred between teams, having to re-explain an issue, waiting multiple days for a follow-up, or struggling with a self-service portal all represent effort that erodes trust in IT regardless of whether the issue eventually gets fixed.
CES is particularly useful when evaluating your self-service portal or knowledge base. If users frequently abandon self-service in favor of submitting a ticket for something that should be resolvable independently, a CES survey on self-service interactions will surface that friction quickly.
CES is also more predictive of user behavior than CSAT in many cases. Research from the original CEB study found that reducing customer effort was more effective at building loyalty than exceeding expectations. In IT terms: getting out of users’ way matters more than going above and beyond.
Where NPS Fits in IT Support
NPS in IT support is primarily a strategic and communications tool. It’s less useful for day-to-day service improvement and more useful for understanding your department’s standing within the organization, justifying headcount or budget requests, and tracking long-term perception shifts after major initiatives (a platform migration, a new ITSM rollout, an SLA restructure).
A low internal NPS is a meaningful signal that IT has a reputation problem that individual ticket scores aren’t capturing. Maybe users have been satisfied with individual interactions but feel IT is slow, hard to reach, or out of touch with business needs. NPS surfaces that gap.
Because NPS is periodic and relationship-level, it’s better suited for IT leadership reporting than for service desk management. Don’t use it as a daily operational metric — the lag between experience and survey makes it poor for incident-level improvement.
Using CSAT, CES, and NPS Together
The strongest IT support measurement programs use all three metrics, but for different purposes and at different cadences. The mistake most teams make is picking one metric and treating it as the single source of truth.
A practical framework looks like this:
- CSAT after every closed ticket: Captures transaction-level quality. Use it to coach agents, flag outliers, and track resolution quality by category or team.
- CES after key touchpoints: Trigger CES surveys after self-service interactions, complex multi-step requests, or escalations. Use it to diagnose process friction.
- NPS quarterly: Send to a sample of users across the organization. Use it to measure IT’s overall reputation and report trends to leadership.
When these three metrics diverge — for example, CSAT is high but NPS is low — that’s a signal worth investigating. It usually means users are satisfied with individual interactions but frustrated with something systemic: wait times, communication gaps, recurring incidents that never get permanently resolved.
Similarly, if CES scores drop on self-service while CSAT on agent interactions stays stable, you know the portal or knowledge base is the problem, not your team.
What Good Scores Look Like in IT Support
Benchmarks vary by industry and organization size, but these are reasonable reference points for internal IT support teams:
- CSAT: A score above 85% is generally considered strong for internal IT. Below 75% signals a meaningful service quality issue worth addressing systematically.
- CES: On a 1–7 scale, an average above 5.5 is a positive signal. Below 5.0 suggests users are experiencing significant friction.
- NPS: Internal IT NPS benchmarks are lower than commercial benchmarks. A score above +20 is solid. Many IT departments operate in the 0–+30 range. Negative scores indicate a real perception problem that leadership should address strategically.
Don’t get too attached to absolute scores. Trends over time — and comparisons between segments (VIP users vs. general staff, location A vs. location B, Tier 1 vs. Tier 2) — are usually more actionable than a single number.
Common Mistakes IT Teams Make with These Metrics
- Measuring CSAT on everything but acting on nothing: Collecting data without a feedback loop to agents and managers makes the survey feel pointless to users and doesn’t drive improvement.
- Ignoring CES entirely: Many ITSM platforms don’t include CES out of the box, so teams default to CSAT only and miss the effort dimension entirely.
- Treating NPS as an operational metric: Running NPS after every ticket or every week produces noisy data and survey fatigue. NPS works on a longer cadence.
- Low response rates killing statistical validity: A CSAT score based on 8 responses out of 200 tickets is not representative. Design your surveys to maximize completion: keep them short (one or two questions), send them at the right moment, and make it easy to respond.
- Not segmenting data: An overall CSAT of 82% can hide a team or category with a 55% score. Always analyze scores by agent, category, priority, and business unit.
How to Collect These Metrics in Practice
Most enterprise ITSM platforms support at least CSAT natively. Some also support CES and NPS with configuration or third-party integrations. When evaluating tools, check whether they support automated survey triggers on ticket closure, customizable survey templates for different metric types, reporting dashboards that break scores down by category and team, and integration with communication channels your users actually use (email, Slack, Microsoft Teams).
For NPS specifically, dedicated survey tools — or ITSM platforms with strong survey modules — work better than bolting an NPS question onto a ticket closure flow. The periodic, relationship-level nature of NPS calls for a different delivery mechanism than transactional CSAT.
Frequently Asked Questions
Which metric should an IT help desk use first?
If you’re starting from scratch, begin with CSAT. It’s the most widely supported metric in ITSM platforms, easiest to explain to stakeholders, and immediately actionable at the ticket level. Once CSAT is established and you have baseline data, add CES for self-service and process evaluation, then NPS for periodic strategic reporting.
Is NPS relevant for internal IT support teams?
Yes, though it works differently than in customer-facing contexts. Internal NPS (sometimes called eNPS in an employee context) measures whether IT has the trust and confidence of the business. It’s useful for IT leadership to track perception trends, justify improvement investments, and demonstrate value during budget cycles. It’s less useful for day-to-day service management.
Can CSAT and CES give conflicting signals?
Yes, and that’s actually useful information. A user might rate an interaction 5/5 on CSAT because the agent was friendly and the issue was eventually resolved — but also rate effort low because they had to follow up three times before getting an answer. High CSAT with low CES is a signal that your team is likeable but your processes are inefficient. Both scores together tell a richer story than either alone.
How do you avoid survey fatigue when using multiple metrics?
Keep each survey to one or two questions, stagger the delivery (don’t send a satisfaction survey and an NPS survey in the same week), and use logic to avoid surveying the same user too frequently. Some ITSM platforms let you set a minimum interval between surveys per user. For NPS, a quarterly cadence with a randomized sample — rather than surveying everyone every time — works well at scale.
What’s a realistic response rate for IT support surveys?
Response rates for internal IT CSAT surveys typically range from 10–30%. Anything above 20% is solid. Rates improve significantly when surveys are short (one question), sent promptly after ticket closure, and delivered through a channel the user already uses. Embedding the rating directly in the email (rather than linking to an external form) tends to increase response rates meaningfully.
Pricing accurate as of the publish date and subject to change. Verify current pricing on each vendor’s official site before purchasing.
Photo by Compagnons on Unsplash
