What is FCR? First Contact Resolution (FCR) is the percentage of customer issues fully resolved in one interaction, with no follow-up or repeat contact. The formula is FCR = (issues resolved on first contact / total issues) x 100. It is one of the clearest support insights you can track, because every unresolved first contact becomes a second one.
In short
- FCR stands for first contact resolution, also called first call resolution in phone teams.
- SQM Group’s 2024 call center benchmark averaged 69%, with 80% treated as world class.
- Customers resolved first time are more satisfied, and repeat contacts cost money.
- Define “resolved” once, write it down and keep it stable.
FCR meaning: first contact resolution vs first call resolution
FCR means first contact resolution: the share of issues solved the first time the customer reaches out, on any channel.
In phone-only call centers the same metric is often called first call resolution, with the same abbreviation and the same formula. “Contact” is the broader term and fits teams that handle email, chat and messaging as well as calls. Whichever name you use, the question is the same: did the customer have to come back about this issue?
How to calculate FCR
To calculate FCR, divide the issues resolved on the first contact by all issues that came in, and multiply by 100.
The hard part is not the arithmetic, it is defining what counts as resolved. Some teams ask the customer in a survey, others check whether the same customer contacts again about the same issue within a set window, for example 24, 48 or 72 hours. Whatever the method, apply it consistently so the number stays comparable over time.
| Element | Detail |
|---|---|
| Formula | FCR = (issues resolved on first contact / total issues) x 100 |
| Worked example | 690 of 1,000 issues resolved first time = 69% FCR |
| How “resolved” is measured | Customer survey, or no repeat contact within a set window |
| Benchmark | 69% average, 80% world class (SQM Group, 2024 data) |
| Best for | Measuring resolution quality, not just speed |
How to calculate FCR in a BPO
In a BPO, calculate FCR per client account with the definition written into the contract: which channels count, which window counts as a repeat, and which contacts are excluded (for example, ones the client’s own policy forces back to the queue). The formula is the same; the agreed definition is what makes the number defensible when the client reviews it.
What is a good FCR score?
A good FCR score for a call center is around 70%, and 80% or higher is treated as world class, according to SQM Group’s FCR benchmark.
In its benchmark of 2024 call center data, SQM Group found an aggregate FCR of 69% across industries, with individual results ranging from 43% to 88%. SQM measures FCR with post-call customer surveys, so a team using a repeat-contact window will get a different number on the same work. Technical or account-specific issues naturally resolve first time less often than simple ones, so compare FCR against your own history and issue mix rather than a single universal number.
Why FCR matters
FCR matters because it improves the customer experience and the cost line at the same time.
When an issue is solved on the first contact, the customer avoids explaining themselves twice, and the business avoids the cost of a second, third or fourth interaction on the same problem. Repeat contacts are expensive, and they are usually a sign that something in the first interaction fell short.
FCR also moves with satisfaction. In its 2021 benchmark, SQM Group’s FCR research found that every 1% improvement in FCR came with a 1% improvement in customer satisfaction, and that satisfaction dropped by 16% on average for each additional call a customer needed. That makes FCR a useful early signal: when it drops, satisfaction and cost tend to move in the wrong direction soon after.
Measure FCR by issue type and channel
Measure FCR by issue type and channel, because a single average hides where first contacts fail.
For example, a team at 72% overall could be at 90% on password resets and 40% on billing disputes. Splitting FCR by contact reason, channel and queue shows which issue types need a better knowledge base article, a policy change or more agent authority. It also keeps the metric honest: an easy mix of issues can lift FCR without any real improvement in handling.
FCR and quality assurance
FCR tells you that an issue was resolved once, but not whether it was resolved well, and quality assurance fills that gap.
An agent can hit a high FCR by closing tickets quickly while missing the real question, skipping a process step or leaving the customer confused. Kaizo’s AutoPilot scores every conversation against your own scorecard once it resolves, so you can check whether strong resolution rates are backed by strong conversations. Root-cause views in Kaizo Insights trace a dip back to the conversations behind it, and because Kaizo reads conversations natively from Zendesk and Salesforce, the quality and outcome data stay in one place.
Related terms
- Customer satisfaction score
- Average Handle Time
- First Response Time
- Customer effort score
- Internal Quality Score
- Customer service metrics and KPIs
Connect conversation quality to your FCR
Start with the conversations behind your repeat contacts: they show exactly where first contacts fall short. See how Kaizo scores every conversation once it resolves, straight from Zendesk or Salesforce.
Let's talk Explore the Kaizo platform
Frequently asked questions
What does FCR stand for?
FCR stands for first contact resolution, and in phone-based call centers it is often read as first call resolution. Both describe the same metric: the percentage of customer issues resolved in a single interaction, without the customer having to contact you again. It is one of the core metrics in call center, BPO and customer service reporting.
What is the FCR formula in a BPO?
The FCR formula in a BPO is the same as anywhere else: issues resolved on first contact divided by total issues, multiplied by 100. What differs is the definition, which is usually agreed with the client. Write down which channels count, the repeat-contact window and any exclusions, so both sides calculate the number the same way.
What is the difference between FCR and AHT?
FCR measures whether an issue was resolved in a single interaction, while Average Handle Time (AHT) measures how long each interaction takes. They can pull against each other: rushing to lower AHT can hurt FCR if issues are not fully solved, so the two are best read together, ideally next to a quality score.
How can I improve FCR?
Give agents the knowledge, tools and authority to close issues in one interaction, and use quality data to find where first contacts fall short. Reviewing the conversations behind repeat contacts shows the specific gaps, such as missed questions or skipped steps, that drive customers to come back. Fix recurring causes in the knowledge base or the policy, not only in coaching.






