Most businesses judge IT support on speed. How fast does someone pick up, how quickly do they reply. But the metric that actually predicts whether people are happy with their support is not speed of answer. It is first call resolution: how often your issue is sorted on the very first contact, with no callback, no second call, and no being passed around from person to person. First call resolution, or FCR, is widely regarded as the single most important key performance indicator a support desk has, because it correlates so strongly with customer satisfaction. For a UK SME, every unresolved contact is lost productivity for your team and a repeat call for the support desk. This guide explains what FCR is, how it is measured, what drives it, and how to tell whether your IT support is any good at it.
What is first call resolution?
First call resolution (FCR), also called first contact resolution, is the percentage of support contacts that are resolved on the first interaction. For a phone call or a live chat, that means the customer’s issue is fully fixed before they hang up or close the chat. For email, the standard most support teams use is resolution within about one business hour.
The key word is resolved. A contact that ends with a callback, an escalation to another team, or a transfer to the “right” department does not count as first call resolution, even if it felt quick. FCR measures whether the problem actually went away on first contact, not how fast someone answered the phone.
What counts as resolved on the first call, and what does not
It is worth being precise here, because it is easy to flatter the numbers. A contact counts as first call resolution only when the customer’s issue is genuinely closed on that first interaction. It does not count when the issue needs a follow-up call, gets escalated to a second line, or is transferred elsewhere because it reached the wrong person first.
There is also a fair adjustment to make. Some contacts genuinely cannot be resolved remotely on first contact, such as a failed piece of hardware that needs a physical swap, or an office move. This is where net and gross FCR differ. Gross FCR counts every incoming contact. Net FCR carves out the contacts that could never be resolved on first contact and measures only the ones that realistically could be. Net FCR is the number that actually tells you how well a support desk is performing, which is why most serious teams track it rather than gross.
Why first call resolution matters more than any other metric
First call resolution is the number one driver of customer satisfaction in support. The relationship is consistent across industries: when issues get resolved first time, satisfaction climbs, and when they do not, it falls sharply. People simply want closure on the first contact with whoever supports them.
The flip side is cost, and this is where it gets concrete. Repeat calls are pure waste. Industry benchmarks put repeat, dissatisfied contacts at somewhere between 20% and 30% of a support desk’s total volume, and the absence of first call resolution can account for as much as 30% of a support operation’s running costs. In plain terms, a large slice of every pound spent on support goes on fixing what was not done right the first time.
It also compounds in your favour when you get it right. Industry data links a 15% improvement in FCR to roughly an 18% reduction in call volume, because you stop generating all the follow-up calls for the same issues. Lower volume means lower operational costs, shorter wait times for everyone else in the queue, and a support team that is not permanently firefighting.
For an SME, it helps to translate all of this out of support jargon. High first call resolution means less downtime, less of your staff’s time lost waiting on IT, and fewer half-fixed problems that come back next week. It is the difference between support that quietly removes friction and support that adds to it. That, in turn, is what drives customer loyalty and reduces churn, whether you are the one buying support or the one providing it.
How to calculate FCR
The formulas are straightforward.
- Gross FCR = contacts resolved on first contact / all incoming contacts
- Net FCR = contacts resolved on first contact / (all incoming contacts – contacts that cannot be resolved remotely)
In practice, FCR is captured in one of two ways. Either the agent ticks a “resolved first time” flag on the ticket at the end of the contact, or customers are asked in a short follow-up survey whether their issue was sorted on the first interaction. Neither method is perfect on its own, so the better desks cross-check the two, which is much easier when you have a ticketing or CRM system holding the full history of every customer contact.
For a sense of scale, the worldwide average net FCR for support desks sits at around 74%, ranging from roughly 41% at the low end to about 94% at the top. That is a useful industry-standard reference point. What separates the two ends of the range is telling. The low performers tend to be “log and dispatch” desks that can handle a password reset but bounce anything more complex to another team. The top performers have well-trained agents equipped with knowledge management and remote diagnostic tools, and resolve more than 90% of eligible contacts on the first interaction.
Why calls do not get resolved first time
When a contact needs a second call, the cause almost always traces back to one of five things.
Agent skill. The person who picks up cannot solve that type of problem. This is fixable through training, coaching, or routing that class of issue to someone equipped to handle it.
Access to information. The answer exists somewhere, but the agent cannot find it quickly, so they take too long, give information from memory, or guess. A current, well-maintained knowledge base and fast access to the right systems is what closes this gap.
Authority. The agent is not allowed to make the call, so the customer has to phone back and escalate to someone who can. Giving front-line staff a little discretion, backed by management, lifts FCR noticeably.
Business systems and process. The agent does everything right, but something behind them breaks: a part is not ordered, a change is not applied, a request stalls in another team. These generate callbacks that the support desk gets blamed for even though the fault is elsewhere.
Customer behaviour. Some people call back at different times hoping for a different answer. Full contact history lets the next agent see what was already said and handle it consistently, which quickly takes the incentive out of repeat calls.
What actually drives high FCR in IT support
Turn those causes around and you get the levers a good IT support function pulls.
Well-trained agents. Agent training is the single biggest driver of first call resolution. More capable first-line engineers resolve more issues, first time, full stop. Comprehensive, ongoing training is not a nice-to-have here, it is the lever with the most leverage.
A living knowledge base. Consolidated, current, searchable answers, with a clear process for agents to add and correct entries as they work, so the knowledge base stays useful instead of rotting into disuse.
Remote diagnostics and fast tools. Tools that let an engineer see and fix the machine during the call. Speed matters: a slow system with a long response time actively hurts FCR, because agents will always take the path of least resistance.
Smart call routing. Skills-based routing gets the caller to someone who can actually help on the first attempt, rather than transferring them around or dropping them into the wrong department, which is one of the fastest ways to turn one call into three.
A self-service portal for the simple things. Letting self-service tools handle password resets and routine requests frees your agents to spend their time resolving the complex issues that genuinely need a person.
Ticketing and CRM with full history. So repeat contacts are visible, patterns are traceable, and no agent is working blind.
Problem management on top. First call resolution fixes the individual contact. Killing recurring issues at the root stops the calls from happening at all. This is where a mature support operation moves beyond break-fix into proper service management, a distinction worth understanding in its own right.
If you outsource IT support, FCR is how you judge the provider
For an SME, first call resolution is one of the cleanest signals of whether an IT support provider is actually good, rather than just cheap or quick to answer the phone. It is worth asking about directly.
Good questions for a current or prospective provider: Do you measure first contact resolution, and is it net or gross? What is your rate? How do you capture it, by agent flag, survey, or both? How do you use it to improve? What is your typical wait time, and how are calls routed to the right engineer?
The red flag to watch for is a “log and dispatch” desk: fast to answer, quick to log your ticket, but slow to actually resolve anything on first contact. Being fast to answer is not the same as being fast to resolve, and only one of those saves your team time.
This is exactly what a well-run managed helpdesk is built around. Our own IT support in London is set up to resolve issues on the first contact wherever possible, with fully trained and Microsoft-certified engineers, remote management tools, proactive monitoring and a single point of contact, so your issue is fixed rather than passed along.
The bottom line
First call resolution is the canary in the coal mine for support quality. It quietly drives satisfaction, loyalty and cost all at the same time, which is why it deserves more attention than the speed-of-answer figures most businesses fixate on.
The route to a high FCR rate is not complicated. Invest in your people, give them the information, tools and authority to fix things on the first contact, and route work to whoever can actually resolve it. Do that and the repeat calls fall away on their own.
FAQs
What is a good first call resolution rate? The worldwide net average for support desks is around 74%, and top performers exceed 90%. Context matters more than a single target, but if a desk is resolving well under half of its eligible contacts on first contact, that is a sign of a “log and dispatch” operation rather than a resolving one.
What is the difference between first call resolution and first contact resolution? They describe the same thing. “First contact resolution” is just the broader term, because modern IT support happens across phone, email, live chat and self-service portals, not only over the phone.
How is FCR calculated? Divide the number of contacts resolved on the first interaction by the number of eligible contacts. Net FCR excludes contacts that cannot be resolved remotely, such as hardware failures needing a physical swap, and is the more meaningful figure.
Why is first call resolution important in IT support? It is the biggest single driver of customer satisfaction and a major driver of cost. Repeat calls waste both your team’s time and the support desk’s, and a low FCR rate usually points to an underlying problem in skills, information, authority or process.
How can a business improve first call resolution? Better-trained agents, a maintained knowledge base, remote diagnostic tools, smart skills-based routing, self-service for simple requests, and fixing the root cause of recurring issues rather than just closing tickets.

