First Contact Resolution

In depth

First contact resolution (FCR) measures how often a customer's issue is fully resolved in a single interaction, with no need to come back. As the formula shows, it is the number of cases resolved on first contact divided by the total number of cases, expressed as a percentage. On the phone the same idea is often called first call resolution, but the principle is identical across chat, email, and messaging.

The key word is "fully". A first contact resolution only counts when the customer walks away with their problem solved, not merely acknowledged or passed along. If the conversation ends with a promise to look into it, a transfer to another team, or a callback later, it does not qualify, however quick that first reply was.

That is what separates it from a broader resolution rate, which counts an issue as resolved whenever it is finally solved, even if that takes several exchanges over several days. It also differs from an escalation rate, which tracks the share of cases that have to be handed up to a more senior team. A rising first contact resolution rate and a falling escalation rate often move together.

What counts as a first contact resolution?

Before you can measure it, the team has to agree what "resolved on first contact" means. Most define it as an issue closed in the first interaction with no reopen and no repeat contact about the same problem within a set window, often a few days. Choosing that window matters: too short and unresolved issues slip through as successes; too long and unrelated new questions get counted against you.

The channel shapes it too. A live chat can resolve a question in one continuous session, whereas an email "first contact" might be a single reply that either answers everything or does not. Measuring FCR per channel keeps the comparison fair.

What's a good first contact resolution rate?

There is no universal figure, and a number quoted for one industry rarely transfers to another. What counts as strong depends on how complex your queries are and which channels carry them. A team fielding simple, repetitive questions can resolve most on first contact; one handling intricate technical cases will see a lower rate for entirely healthy reasons.

Because of that, your own trend is the most useful measure. Watch the rate as you close knowledge gaps and route queries better. And read it alongside satisfaction: a first contact resolution is only genuine if the customer agrees the issue was solved, so a high rate paired with steady satisfaction is the combination to aim for.