First Contact Resolution (FCR) is the percentage of customer issues fully resolved in one interaction, with no follow-up or repeat contact. FCR = (issues resolved on first contact / total issues) x 100.
In short
- A strong FCR sits around 70% to 75%, varying by channel.
- Customers resolved first time are far more satisfied.
- Every unresolved first contact becomes a repeat contact.
- Low FCR quietly inflates support cost and volume.
How to calculate FCR
First Contact Resolution is a ratio: how many issues were closed on the first interaction, out of every issue that came in. You divide resolved-on-first-contact issues by total issues and multiply by 100 to get a percentage.
The hard part is not the arithmetic, it is defining what counts as resolved. Some teams measure it by asking the customer, others by checking whether the same person contacts again within a set window, often 24 to 72 hours. Whatever the method, it should be applied consistently so the number stays comparable over time.
| Element | Detail |
|---|---|
| Formula | FCR = (issues resolved on first contact / total issues) x 100 |
| Good benchmark | Around 70% to 75% |
| Repeat-contact window | Commonly 24 to 72 hours |
| Best for | Measuring resolution quality, not just speed |
Why FCR matters
FCR is one of the few metrics that improves both the customer experience and the cost line at the same time. When an issue is solved on the first contact, the customer avoids the frustration of 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.
Because of this, FCR correlates strongly with CSAT. Customers rate their experience far higher when they are resolved once. That makes FCR a useful early signal: when it drops, satisfaction and cost tend to move in the wrong direction soon after.
FCR and quality assurance
FCR tells you that an issue was resolved once, but not whether it was resolved well. 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. That is the gap quality assurance fills. Kaizo scores the content of each conversation with its Internal Quality Score (IQS), then connects that quality signal to operational metrics like FCR, so leaders can see whether strong resolution rates are backed by strong conversations. Kaizo reads conversations natively from Zendesk and Salesforce, which keeps the quality and outcome data in one place.
Frequently asked questions
What is a good FCR score?
Around 70% to 75% is widely treated as a strong benchmark, but the right target depends on your channel mix and issue complexity. Highly technical or account-specific issues naturally resolve on first contact less often than simple ones, so compare FCR against your own history rather than a single universal number.
How is FCR calculated?
FCR = (issues resolved on first contact / total issues) x 100. The main decision is how you define resolved: either by asking the customer directly or by checking whether they contact again within a set window, commonly 24 to 72 hours.
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.
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 are driving customers to come back.
Related terms
- CSAT
- Average Handle Time
- First Response Time
- Internal Quality Score
- Customer service metrics and KPIs
Connect conversation quality to your FCR
See how Kaizo scores 100% of your conversations and links quality to outcomes like first contact resolution, straight from Zendesk or Salesforce.
