First Call Resolution: How to Measure It and Raise It

First call resolution, or FCR, is the percentage of customer issues that are fully resolved on the first contact, with no call back, transfer to another day or follow up needed from the customer. Because customers increasingly use chat and email, it is also called first contact resolution.

It is one of the first numbers worth checking when you review a support team. This guide covers how to measure it without fooling yourself and what raises it.

The formula

FCR = issues resolved on the first contact ÷ total issues × 100

A worked example

In one week your team handles 500 separate customer issues. Of those, 380 were resolved in a single contact. FCR is 380 ÷ 500 × 100 = 76%.

The number depends entirely on how you define "resolved" and "first". Decide both before you start counting.

Three ways to measure it

• Repeat contact tracking. Count an issue as resolved first time if the same customer does not contact you about the same issue within a set window, often several days. It is objective but needs good contact records.
• Asking the customer. Add a question to your survey: "Was your issue resolved today?" It reflects the customer’s view, which is the one that counts, but depends on response rates.
• Agent logging. The agent marks whether the issue was resolved. It is easy to collect and tends to run high.

Using two methods together gives the most honest picture. If agent logging says 90% and customers say 70%, the gap is where to look.

Why it matters

• Customers value it. Having to call back is one of the strongest causes of dissatisfaction. It feeds directly into your client satisfaction score.
• It lowers cost. Every repeat contact is work that produced nothing the first time.
• It shows where processes fail. Issues that cannot be solved in one contact usually point to missing information, missing authority or a broken handoff.

What counts as a good rate

Published benchmarks vary widely because definitions do. A team that counts only phone calls and excludes transfers will report a higher number than one that follows the customer across channels for a week. Compare against your own baseline under a fixed definition, and judge the trend.

Some issues should not be resolved on the first contact. A repair that needs a technician visit or a claim that needs documents takes more than one step. Track those separately so they do not hide the avoidable repeats.

What gets in the way

• Agents do not have the information to answer.
• Agents are not allowed to make the decision.
• Customers are transferred between teams and have to explain again.
• Pressure to keep calls short ends them before the issue is solved.
• The underlying problem, such as a confusing invoice, keeps generating the same calls.

How to raise it

1. List the top reasons for repeat contacts. Read the notes on calls that came back. A handful of causes usually accounts for most of them.
2. Build a call guide for those causes. Write the answer, the steps and the exceptions where agents can find them in seconds.
3. Give agents authority. Decide which refunds, credits and exceptions an agent can approve alone.
4. Train on the product, not the script. Agents who understand how things work can handle the question behind the question.
5. Confirm before closing. End with "Have I resolved what you called about today?" and act on the answer.
6. Fix the cause upstream. If one policy or document generates repeat calls, changing it removes them entirely.
7. Keep the same people on the account. Knowledge compounds when agents are not rotated away.

Balancing it with handle time

Average handle time measures how long contacts take. Pushing it down too hard lowers resolution, because agents end calls early. Pushing resolution up may lengthen calls slightly and still reduce total workload, because fewer customers call back. Watch both numbers together. Our guide to customer lifetime value explains why the resolution side usually deserves priority.

Pitfalls

• Counting a transferred call as resolved.
• Letting agents close tickets that customers consider open.
• Rewarding the number so heavily that agents avoid difficult issues.
• Measuring only one channel when customers move between several.

Where a dedicated team helps

Resolution rates rise when agents know the account. A shared pool reading a script can take a message. A dedicated team that works your account every day can answer the question. That is how our customer support and help desk teams are set up, and why we train on your product before the first live contact.

Frequently asked questions

What is first call resolution?

The percentage of customer issues fully resolved on the first contact, without the customer needing to follow up.

How is first call resolution calculated?

Divide the number of issues resolved on the first contact by the total number of issues and multiply by 100.

What is the difference between first call resolution and first contact resolution?

They measure the same thing. First contact resolution includes chat, email and other channels as well as phone calls.

How can you improve first call resolution?

Find the main causes of repeat contacts, give agents the information and authority to resolve them, confirm resolution before closing and fix recurring causes at the source.

About eleVAte BPO. eleVAte began in 2015 with two virtual assistants in Dumaguete City, Philippines, and is still run by its founders. Co-Founder and CEO Claire De La Pena spent almost two decades as an executive virtual assistant before building the company, which is now a 50 seat operation providing dedicated support, sales and back office teams. Meet the leadership team.

Last reviewed October 2026. This guide is general information and not legal, tax or financial advice.