First contact resolution (FCR) is the percentage of customer issues your team solves in a single interaction, with no callback, no reply, and no follow-up needed. You calculate it as the number of contacts resolved on the first touch divided by the total number of contacts, times 100. A good FCR rate in 2026 sits between 70 and 79 percent; 80 percent or higher is considered world-class, and only about 5 percent of support teams reach it. FCR is the closest thing support operations has to a single number that tracks both cost and customer loyalty at once.
Most support metrics measure one thing well. First contact resolution is unusual because it moves two things at once, and in the same direction. When a customer gets their problem fully solved the first time they reach out, they are more satisfied and more loyal, and your team never pays for the second, third, or fourth contact that a half-solved issue generates. That is why the Service Quality Measurement Group's long-running benchmark data shows that every one-point gain in FCR reduces operating cost by roughly one percent. This guide covers what FCR actually measures, how to calculate it, what a good rate looks like by industry in 2026, how it pulls against average handle time, and the specific changes that raise it without turning the metric into a game.
What is first contact resolution?
First contact resolution is the share of customer issues resolved during the first interaction, so the customer does not have to get back in touch about the same problem. The word "contact" matters more than the older term "first call resolution," because customers now arrive by phone, chat, email, and social, and the metric applies to all of them. A resolved contact is one where the customer's issue is actually closed out, not one where the agent gave a holding answer and promised to follow up. If the same customer reaches out again within a set window, usually 24 hours to 7 days depending on your business, about the same issue, that first contact did not resolve anything and should not count as an FCR win.
FCR is a quality and effectiveness metric, which is exactly what makes it the natural counterweight to the efficiency metrics. Average handle time tells you how long each contact takes; FCR tells you whether the contact worked. A team can look fast and cheap on handle time while quietly failing customers, and FCR is the number that exposes it, because unresolved issues come straight back as repeat contacts.
How do you calculate first contact resolution?
The formula is simple. Divide the number of issues resolved on the first contact by the total number of issues handled, then multiply by 100.
FCR = (issues resolved on first contact / total issues handled) x 100.
If your team handled 1,000 contacts in a week and 750 of them were fully resolved on the first touch with no repeat, your FCR is 75 percent.
| Input | Value |
|---|---|
| Contacts resolved on first touch | 750 |
| Total contacts handled | 1,000 |
| First contact resolution rate | 75% |
The hard part is not the arithmetic; it is deciding what counts as "resolved," and there are two honest ways to measure it. The first is the repeat-contact method: count any customer who comes back about the same issue inside your chosen window as a failure, and everyone else as a success. This is objective and pulls straight from your help desk, but it can overstate FCR, because some customers give up instead of contacting you again. The second is to ask the customer directly, with a short post-contact survey question like "Did we fully resolve your issue today?" This captures the cases where the customer quietly walked away unhappy, but it depends on survey response rates. Strong operations use both: the repeat-contact rate as the always-on number, and the survey question as a periodic reality check on it. Whatever you choose, define it once and keep it identical every month, or your trend is meaningless.
What is a good first contact resolution rate?
Across industries, a good FCR rate is 70 to 79 percent, 80 percent and above is world-class, and only about 5 percent of contact centers hit that top tier. The cross-industry average lands near 70 to 75 percent. But the right target for your team depends heavily on how complex your contacts are, so read the benchmark by industry rather than chasing a single universal number.
| Industry | Typical 2026 FCR range |
|---|---|
| Ecommerce and retail | 75 to 85% |
| Utilities and financial services | 76 to 82% |
| Cross-industry average | 70 to 75% |
| Healthcare | 65 to 75% |
| Telecommunications | 52 to 58% |
The pattern is intuitive once you see it. Industries with simple, transactional issues like ecommerce resolve most contacts on the first touch, while telecom sits at the bottom because its problems are technical, multi-system, and often need escalation. A 60 percent FCR would be poor for a retailer and genuinely strong for a telecom support desk. Use the benchmark to set a realistic target for your own contact mix, then compete against your own trend line month over month, which is a far more useful measure than your number against someone else's average.
Why does first contact resolution matter so much?
First contact resolution matters because it is one of the few metrics where the interests of the customer and the interests of the business point the same way. Solve the issue the first time and the customer is happier and more loyal, while the business avoids the entire cost of every follow-up contact that an unresolved issue would have generated. The SQM Group's benchmarking puts a number on it: roughly a one percent drop in operating cost for every one percent rise in FCR. The reverse is just as real. A low FCR means customers are contacting you two and three times for one problem, which inflates your volume, frustrates your customers, and drags down satisfaction all at once. That is why FCR is often called the single most important call center metric, because improving it improves cost and experience together instead of trading one for the other.
First contact resolution versus average handle time
These two metrics pull against each other, and understanding the tension is the whole point of tracking both. Average handle time rewards short contacts; FCR rewards complete ones. Push agents to close contacts faster and handle time drops, but so does FCR, because rushing a customer off the line leaves the problem half-solved and produces a callback. That callback is the trap: your handle time report looks great while your total workload quietly rises, because you are now paying to handle the same issue twice. The honest way to read the pair is that FCR is the guardrail on handle time. A falling AHT is only good news if FCR holds or rises with it. If handle time is dropping while FCR slips, you are not getting more efficient; you are pushing work into the future and calling it progress.
How do you improve first contact resolution?
Raising FCR is mostly about giving agents what they need to finish an issue on the first try, rather than telling them to try harder. These are the levers with the most leverage, roughly in order.
1. Give agents the knowledge and the authority to resolve. The most common reason a contact does not resolve is that the agent could not find the answer or was not allowed to act on it. A well-maintained internal customer service knowledge base puts the answer in reach, and expanding what frontline agents are empowered to decide (refunds up to a limit, account changes, exceptions) removes the escalations that turn a one-contact issue into three.
2. Route to the right agent the first time. A contact that lands with someone who cannot solve it is an FCR failure before the conversation even starts. Skills-based routing that matches the customer to a capable agent, built on top of a well-run ticketing system, is one of the fastest ways to lift the rate.
3. Find and fix your top repeat-contact reasons. Pull the issues that most often generate a second contact and treat each as a process problem, not an agent problem. If password resets or billing disputes keep coming back, the fix is usually a better workflow, a clearer help article, or a product change, and fixing the top three repeat drivers moves FCR more than any amount of coaching.
4. Solve the whole problem, not just the asked question. Next-issue avoidance means resolving the reason the customer contacted you and the follow-up they were about to have. A customer asking how to change their plan often also needs to know when it takes effect and how it is billed; answering all of it in one contact prevents the second one. This is a coaching win that raises FCR and satisfaction together.
5. Deflect simple issues to self-service, and route the rest. A good help center resolves the easy questions before they become contacts, which raises overall first-touch resolution across your channels even though it changes the mix that reaches agents.
6. Measure FCR per agent and per issue type, and coach on the gaps. An aggregate FCR hides where the losses are. Break it down by agent and by issue category, find the specific combinations that resolve poorly, and fix the cause, whether that is a training gap, a missing permission, or a broken process step.
Making first contact resolution the metric that keeps the others honest
First contact resolution deserves a permanent place at the top of your support dashboard because it measures the thing customers actually care about, getting their problem solved, while tracking cost at the same time. Define it clearly, measure it the same way every month with the repeat-contact rate as your always-on number and a survey question as your reality check, and set a target that fits your contact mix rather than a borrowed industry average. Most importantly, read it next to your efficiency metrics rather than in isolation. FCR is what stops average handle time and first response time from turning into a race to close contacts fast instead of well, and it belongs in the same view as CSAT in your core support metrics. Handled that way, FCR becomes the number that keeps the whole customer experience operation pointed at solving problems, which is the only version of efficiency that lasts.