First contact resolution (FCR) is a contact center measure of how often a customer’s issue is fully resolved in the first conversation, so the customer doesn’t need to call, chat or email again about the same thing. It is usually expressed as a percentage of issues or contacts. Because repeat contacts cost money and frustrate customers, FCR is one of the measures most closely watched alongside satisfaction.
At a glance
- FCR measures resolution in one conversation, across whatever channels you include.
- There is no single standard formula; the definition of “resolved” and “repeat” decides the number.
- It is measured by customer surveys, by tracking repeat contacts, by agent disposition codes, or a combination.
- Low FCR usually points to missing information, missing authority or broken processes, not only agent skill.
- It is best read together with handle time and customer satisfaction, since each can be improved at the others’ expense.
What problem it solves
When a customer has to contact a company several times about one problem, the company pays for each contact and the customer’s opinion drops with each one. Operational measures such as wait time and handle time don’t show this: a contact center can answer quickly and keep calls short while customers keep coming back.
FCR makes repeat effort visible. A low or falling rate tells managers that something is preventing agents from finishing the job, such as a system they can’t access, a refund they aren’t allowed to approve, or a handoff to another team that drops the thread. Fixing those causes reduces volume and improves the experience at the same time, which is why FCR is often tied to customer satisfaction (CSAT) and customer effort score (CES).
How it works
Companies typically measure FCR in one or more of these ways:
Customer survey. After the contact, the customer is asked whether the issue was resolved. This reflects the customer’s view but depends on who answers surveys.
Repeat-contact tracking. The system checks whether the same customer contacted again within a set window, such as several days, possibly about the same reason. This needs a reliable way to identify the customer across channels, usually through CRM or contact center data.
Agent disposition. The agent marks the contact as resolved or not. This is easy to collect but tends to overstate resolution.
The basic calculation is resolved-on-first-contact divided by total issues. Decisions that change the result include which channels count, how long the repeat window is, whether a transfer within the same conversation still counts as first contact, and whether contacts that are inherently multi-step (such as a claim) are excluded.
Improvement usually comes from giving agents better knowledge and system access, widening what they are allowed to approve, routing contacts to the right skill the first time, and fixing the upstream causes that generate repeat questions.
When it matters for buyers
- When choosing a contact center platform, since FCR depends on how well it identifies returning customers across channels and integrates with the CRM.
- When comparing outsourcers or setting their targets; make sure both sides use the same definition.
- When handle time targets are pushing agents to end calls early, which often shows up as lower FCR.
- When building a business case for knowledge tools, average handle time (AHT) reductions or self-service, where fewer repeat contacts are part of the return.
Our contact center as a service page covers what to look for in reporting and integrations.
Questions to ask vendors
- How does your platform measure FCR out of the box: survey, repeat-contact tracking, agent disposition or a mix?
- Can we set the repeat window and choose which channels and contact reasons count?
- How do you recognize the same customer across phone, chat, email and messaging?
- Can FCR be reported by agent, team, queue and contact reason?
- Does a transfer or escalation inside one conversation count as first contact in your reports?
- For outsourcers: how do you define FCR in your contract reporting, and can we audit it?
How it differs from customer satisfaction (CSAT)
Customer satisfaction (CSAT) asks customers how they felt about an interaction. FCR asks whether the issue was actually finished. The two usually move together, but not always: a friendly agent can score well on CSAT for a contact that didn’t solve anything, and a customer can be unhappy with a policy even when the issue was resolved in one call. Tracking both gives a fuller picture of the contact center and of overall customer experience (CX).