Help Desk SLAs Explained: FCR, CSAT, AHT

Any IT provider can promise “fast support.” The metrics on the Service Level Agreement (SLA) are what hold them to it. But the alphabet soup — FCR, CSAT, AHT, response and resolution times — hides real trade-offs, and a provider can look great on one number while quietly failing on another. This guide explains the help-desk metrics that actually predict your experience, and how to read them together. For the service itself, see our 24/7 help desk support and outsourced IT help desk pages.

What it measures: the share of tickets resolved in the first interaction, with no callback, escalation, or second touch. Why it matters: FCR is the single best proxy for help-desk quality — it rolls speed, technician skill, and good tooling into one number. High FCR means problems actually get fixed, not just acknowledged. A healthy range: 70–75%+ for a mature help desk; below roughly 60% usually signals thin staffing, weak knowledge bases, or under-skilled tier-1 agents. Ask how FCR is defined — some providers count a ticket “resolved” the moment it’s assigned.

What it measures: how users rate an interaction, usually a short post-ticket survey (“How satisfied were you?” on a 1–5 scale), reported as the percentage of positive responses. Why it matters: it’s the human counterweight to purely technical metrics — a ticket can be closed “correctly” and still leave the user frustrated. A healthy range: 90%+ positive, with a response rate high enough to trust. Watch for: tiny sample sizes and survey-gaming; CSAT is most useful as a trend over time, not a single snapshot.

What it measures: the average time an agent spends actively working a ticket. Why it matters: it’s an efficiency and capacity signal — useful for planning, not for judging quality on its own. The trap: AHT is the easiest metric to game and the most misleading in isolation. Push agents to drive it down and they close tickets prematurely, which tanks FCR and CSAT as the same issues bounce back. Read AHT alongside FCR: fast and resolved is the goal; fast but unresolved is just rework with a stopwatch.

These two are often confused, and the difference matters. Response time is how long until a human acknowledges your ticket; resolution time is how long until it’s actually fixed. A 15-minute response SLA means little if resolution then drags for days. Good SLAs set both, and tier them by priority: a server outage (P1) should carry a far tighter target than a password reset (P4). Make sure the agreement defines the priority levels and the clock rules — when the timer starts, when it pauses (for example, awaiting your input), and when it stops.

Four questions cut through most of the sales gloss: (1) How are FCR and CSAT defined and measured — and will you see the raw reports? (2) Are response and resolution targets set per priority level? (3) What are the support hours, and is after-hours coverage real 24/7 staffing or just an on-call pager? (4) What happens when a target is missed — service credits, escalation, or nothing? A provider that reports transparently on the metrics that could embarrass it is usually one worth trusting. For where help-desk cost fits the bigger picture, see our managed IT services cost guide.

ConsultingCrafts runs a remote-first, genuinely staffed help desk and reports the metrics that matter — FCR, CSAT, and tiered response/resolution times — openly, so you can hold us to them rather than take “fast support” on faith. Whether you need a full 24/7 help desk or co-managed overflow for an in-house team, the reporting is the same. Book a free consultation to see a sample SLA and metrics report.