First Contact Resolution (FCR)

First contact resolution (FCR) is the percentage of customer issues resolved in a single interaction, on the first call, chat, or message, without the customer needing to follow up or be transferred. It is one of the most valued metrics in customer support, because resolving an issue the first time is both more efficient and far more satisfying for the customer.

FCR captures something customers care about deeply: getting their problem solved without repeating themselves, waiting for callbacks, or being bounced between agents. A high FCR means issues are handled cleanly the first time; a low one means customers endure the frustration of multiple contacts for a single problem.

What first contact resolution measures

FCR is the share of issues fully resolved within the first interaction, divided by total issues. The key word is resolved, and first: the customer's problem must be genuinely solved, and solved without a second contact, transfer, or follow-up. An issue that appears handled but generates a callback the next day is not first contact resolution, which is why FCR is measured alongside repeat-contact and reopen rates to keep it honest.

Why FCR matters

• Customer satisfaction. Few things satisfy customers more than getting it sorted the first time; FCR correlates strongly with satisfaction.
• Efficiency. Resolving in one interaction avoids the cost of repeat contacts and transfers.
• Loyalty. Customers whose issues are resolved quickly and cleanly are more likely to stay.
• Quality signal. FCR reflects whether agents (or AI) are equipped to actually solve problems.

FCR and related resolution metrics

FCR is a specific, demanding form of resolution: it is resolution rate with the added condition of "in one interaction." It connects to deflection rate (issues resolved without an agent) and to handle time, though importantly FCR should not be sacrificed for speed.

Each metric measures a distinct thing, which is why they are read together:

The tension to watch is FCR versus average handle time: pushing agents to end interactions fast can lower FCR (rushed, incomplete resolutions that generate callbacks), while genuine first-time resolution sometimes takes a little longer up front but saves the repeat contact entirely. Optimizing for true FCR usually beats optimizing for raw speed.

How FCR is improved

FCR rises when agents and systems are equipped to resolve issues on the spot: good knowledge access, the authority and tools to act (not just escalate), and routing that gets the customer to someone (or something) able to help the first time. AI plays a growing role, a capable customer agent that can actually take actions can resolve many issues in one interaction, raising FCR, provided it escalates cleanly when it cannot.

Common FCR mistakes

• Counting false resolutions. Marking an issue resolved that generates a callback inflates FCR and hides failure.
• Sacrificing FCR for speed. Rushing interactions to cut handle time produces incomplete resolutions and repeat contacts.
• Under-empowering agents. Agents who can only escalate, not act, cannot achieve high FCR.
• Ignoring the customer's view. FCR should reflect the customer's problem being solved, not just a ticket closed.

First contact resolution measures whether a customer's issue is genuinely solved in a single interaction, a metric that captures both efficiency and satisfaction better than almost any other in support. Improved by equipping agents and AI to actually resolve, not just deflect or escalate, and protected from being sacrificed for raw speed, it is a hallmark of support that genuinely works.