First contact resolution (FCR)

What first contact resolution means

First contact resolution (FCR) is the share of support requests that are fully resolved in a single interaction, with no follow-up contacts, callbacks, or escalations required. It is expressed as a percentage of total contacts, and "first contact" spans whichever channel the customer used, a call, a chat, an email, or a message. The defining test is simple: did the customer get a complete answer the first time they reached out, or did they have to come back?

In customer support, FCR is treated as one of the highest-signal quality metrics, because repeat contacts are expensive for the team and frustrating for the customer. An issue that takes three touches to close burns three times the agent time and quietly drives up customer effort score. A high FCR usually means the knowledge is good, the agent (or AI) is empowered to act, and customers are getting real resolutions rather than placeholders.

Why first contact resolution matters

• It is a leading indicator of loyalty. Solving an issue the first time is one of the strongest drivers of satisfaction, while a second contact for the same problem is one of the strongest drivers of churn.
• It lowers cost directly. Every avoided repeat contact is agent time not spent, so FCR feeds straight into cost-per-ticket.
• It reflects knowledge quality. Low FCR on a topic usually means the answer is missing, outdated, or hard to find, which points at a fixable knowledge gap.
• It exposes empowerment gaps. If agents have to escalate to resolve, FCR drops, which signals the front line lacks the access or authority to finish the job.
• It pairs with effort and reopens. Reading FCR next to reopen rate tells you whether "resolved" really meant resolved.

How to measure first contact resolution

A typical FCR program works like this:

1. Define a resolution. Decide what counts as resolved on first contact, usually no reopen and no related follow-up within a fixed window such as 7 days.
2. Count first-contact resolutions. Tally the issues that met that definition in one interaction.
3. Count total contacts. Tally all issues handled in the period.
4. Calculate the rate. Divide first-contact resolutions by total contacts and multiply by 100.
5. Segment and investigate. Break FCR down by channel and topic to find where repeat contacts cluster, then fix the underlying gap.

So FCR equals (issues resolved on first contact divided by total issues) times 100.

The reliable way to lift FCR is to give the first responder both the answer and the ability to act. An AI agent like eesel AI grounds its reply in your help center and past tickets and takes the action in your helpdesk in the same interaction, so simple issues close on first contact instead of bouncing. When it cannot resolve something safely, it escalates with full context attached, so the human contact still has what it needs to finish in one go.

First contact resolution in practice

The trap with FCR is gaming the definition: mark a ticket resolved, and the metric looks great until the customer reopens it two days later. That is why FCR is only trustworthy next to reopen rate and a satisfaction signal, since together they distinguish a real resolution from a premature close. Segment it hard, because a healthy blended FCR can hide one topic where every issue takes three touches. The most durable gains come from removing the reasons a second contact happens at all: better knowledge, agents (and AI) empowered to act, and clean escalations that carry context forward instead of resetting the conversation.

We go deeper on this in AI for first contact resolution.