What it means
The measure is popular because it links customer experience and cost in a single number. Every contact that has to be repeated costs the business a second agent's time and costs the customer their patience, so improving the rate tends to pull satisfaction up and cost per case down at the same time.
Definitions matter more than the arithmetic here. Teams have to agree what counts as a contact, what window counts as a repeat (usually seven days), and whether a case that is correctly escalated to a specialist team counts as a failure of first contact resolution or as a legitimate handoff.
Measurement comes from two sources, and they rarely agree. System-based measurement counts whether the customer came back within the window, while survey-based measurement asks the customer directly, and the survey figure is typically lower because customers count partial answers as unresolved.
The rate is easy to game, which is why it should never be a lone target. An agent under pressure can close a ticket that is not really solved, or a team can quietly encourage customers to open new tickets rather than reopen old ones, so the number should sit beside satisfaction, repeat-contact volume and quality scores.
Fixing a weak rate is usually about access rather than agent effort. The common cures are giving front-line staff permission to issue refunds up to a limit, putting order and account data in one screen instead of four, and rewriting the knowledge base around the questions customers actually ask.
In practice
Real-world examples.
Example
A broadband provider finds that 40% of repeat calls concern a single billing scenario, the pro-rata charge on an upgrade. Adding one plain-English line to the bill and a short script for agents lifts the first contact resolution rate from 62% to 71% in two months.
Example
A software company's support team can see licence data but not payment history, so every billing question becomes a handoff. Giving agents read-only access to the payments system removes an entire category of second contacts without adding headcount.
Example
A retail bank's branch team resolves 85% of enquiries at first contact while its chat channel manages only 55%, because chat agents cannot verify identity to the same standard. The bank invests in in-app authentication rather than more chat staff.
Think of it
“FCR shows how often you solve problems on the first try-no callbacks needed.
Formula
Calculation
First Contact Resolution Rate = (Contacts resolved on the first interaction / Total contacts) x 100
Take a support team handling 12,000 contacts in a month, of which 8,400 are resolved on the first interaction.
First contact resolution rate = 8,400 / 12,000 x 100 = 70%
The remaining 3,600 contacts generate an average of 1.5 follow-up contacts each, which is 5,400 extra interactions. At a fully loaded cost of $6 per contact, those repeats cost 5,400 x $6 = $32,400 a month.
Now suppose better refund permissions lift the rate to 75%. First-time resolutions rise to 9,000, unresolved contacts fall to 3,000, and follow-ups fall to 3,000 x 1.5 = 4,500, costing 4,500 x $6 = $27,000. The saving is $32,400 - $27,000 = $5,400 a month, or $64,800 a year, before counting any improvement in retention.Case study
Seen in the real world.
The following example is illustrative and the company is fictional. Northgate Home Insurance handled about 30,000 contacts a quarter and measured a first contact resolution rate of 64%, which the board considered acceptable until someone compared it with the cancellation numbers. Customers who had to make two or more contacts about the same issue cancelled at nearly twice the rate of those sorted out first time.
The operations team spent six weeks listening to repeat contacts and found that two thirds of them involved a claim status question that agents could not answer because the claims system was updated only overnight. Moving to hourly updates and giving agents a single status screen raised the rate to 78% within a quarter.
The illustrative point is that the metric earned attention only once it was connected to revenue. Support cost savings alone would not have justified the systems work, but the retention effect did.
Watch out
Common mistakes.
- Setting an aggressive first contact resolution target without a quality check, which encourages agents to close tickets that are not genuinely resolved.
- Comparing the figure across channels or companies as though the definitions match, when the repeat window and the treatment of escalations differ widely.
- Treating a low rate as an agent performance problem, when it is more often caused by restricted permissions, fragmented systems or confusing policies.
Questions
People also ask.
What is a good first contact resolution rate?
It varies by channel and complexity, but many service teams sit somewhere between 65% and 80%, and the trend in your own numbers matters more than the benchmark.
Should a transfer to a specialist count as a failure?
Most teams count it as a failure if the customer has to explain the problem again, and as a success if it is a warm transfer resolved within the same interaction.
How does it relate to average handle time?
They pull against each other, because rushing a call to shorten handle time often creates a repeat contact, so the two should always be reviewed together.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%