What is first contact resolution (FCR)?

First contact resolution (FCR) is a customer service metric that measures the percentage of customer issues resolved on the first interaction, without the customer needing to follow up or re-open the same issue. It is tracked operationally — not by survey — by comparing the number of cases closed on first contact to the total number of cases received over the same period.

FCR is one of the most direct efficiency signals in a contact center. Where CSAT tells you whether customers were satisfied and NPS tells you whether they would recommend the brand, FCR tells you something more concrete: did the team actually solve the problem the first time someone asked?

This page covers what FCR measures, how it differs from first call resolution, how to calculate the FCR rate, what a good rate looks like, how FCR relates to CSAT and other CX metrics, where the metric is useful and where it falls short, how to improve it, and a short FAQ.

FCR in one sentence

FCR is the share of customer interactions that end with a fully resolved issue — no callback, no follow-up email, no reopened ticket.

What FCR actually measures

FCR is an operational metric. It measures the effectiveness of a support team's resolution process, not how customers felt about it. A customer can have a perfectly pleasant interaction with an agent and still have to call back tomorrow because the problem was not actually fixed — that counts as an FCR miss. A customer can have a terse, businesslike interaction and get their issue resolved in four minutes — that is an FCR success.

This is what makes FCR different from satisfaction metrics. CSAT, NPS, and CES are perception-based: they ask customers to describe how they felt. FCR is outcome-based: it asks whether the issue went away. The two sets of data are related — unresolved issues reliably produce low satisfaction scores — but they are not the same measurement.

FCR is also channel-agnostic. It applies equally to phone calls, chat sessions, emails, SMS threads, and social DMs. Any channel where a customer contacts support with a problem counts.

First contact resolution vs. first call resolution

"First call resolution" and "first contact resolution" are often used interchangeably, but they are not the same thing.

First call resolution is the narrower, older term. It originated in call center operations and refers specifically to phone calls. A high first call resolution rate means most callers get their issues resolved on the first phone call.

First contact resolution is the modern, channel-inclusive version. It applies the same logic across every support channel — phone, chat, email, messaging, social — and reflects the reality that most customers now use multiple channels to reach support. Because first contact resolution covers the full channel mix, it is the standard most contact centers and CX programs use today.

For organizations that still measure first call resolution as a phone-specific KPI, FCR can coexist alongside it: first call resolution tracks voice channel performance; FCR tracks the full operation.

How to calculate FCR

The FCR formula is straightforward:

FCR = (number of cases resolved on first contact ÷ total number of cases received) × 100

Both figures should be pulled from the same time window — the same day, week, or month.

A few practical notes on counting:

What counts as "resolved on first contact" varies by organization. Common approaches include: the agent marks the conversation as resolved and no follow-up contact is initiated on the same issue within a defined window (24 hours, 48 hours, or 5 business days are common); or a post-interaction survey asks the customer whether their issue was fully resolved.

Some cases should be excluded. Bug reports that depend on an engineering fix, order issues pending a carrier update, or complex cases that genuinely require follow-up are sometimes removed from the FCR denominator. If these cases cannot theoretically be resolved on first contact, including them pulls the rate down artificially.

Multi-channel journeys complicate the calculation. A customer who starts a chat, abandons it, and calls back an hour later may be counted as two contacts or one conversation, depending on how the platform defines a "contact." Make sure the definition is consistent over time so the trend line is meaningful.

Worked example: A support team receives 1,200 contacts in a week. 900 of them are closed without any follow-up on the same issue. FCR = (900 ÷ 1,200) × 100 = 75%.

What is a good FCR rate?

According to the Service Quality Measurement (SQM) Group, the industry benchmark is 70 to 79 percent. An FCR rate of 80 percent or higher is considered world-class, and only about 5 percent of contact centers reach that level consistently.

Those benchmarks carry a caveat: FCR is strongly shaped by channel mix, industry, and issue complexity. A team that handles primarily complex technical issues will have a structurally lower FCR than one that handles mostly order status questions. A team with a high proportion of email contacts will naturally have lower FCR than one that is phone- or chat-heavy, because asynchronous channels require more back-and-forth exchanges.

The most useful FCR question is not "are we above 70%?" but "is our FCR improving, and do we understand why?"

FCR and related metrics

FCR belongs to the same CX dashboard as CSAT, NPS, and CES, but it measures something different from all three.

The shortest way to keep them straight: FCR is about outcomes, CSAT is about feelings, NPS is about the relationship, CES is about the friction. Each answers a question the others cannot.

The most telling relationship is FCR ↔ CSAT. SQM Group's research consistently shows that for every 1 percent improvement in FCR, customer satisfaction improves by roughly 1 percent. Unresolved issues generate follow-up contacts, and follow-up contacts generate frustration. Improving FCR is one of the most reliable ways to move a CSAT number.

For a deeper read on how these metrics fit into a broader contact center program, see the Gladly guide to contact center metrics for modern CX teams.

Strengths of FCR

It is tied directly to operating cost. SQM Group's research shows that a 1 percent FCR improvement reduces operating costs by roughly 1 percent, because every avoided follow-up contact frees agent time. No other standard CX metric has that kind of direct cost line.

It is outcome-based, not perception-based. FCR measures what happened, not how the customer described it afterward. That makes it harder to game and more resistant to survey bias than satisfaction metrics.

It correlates with employee satisfaction. Agents who resolve issues on first contact deal with fewer frustrated repeat callers. SQM Group's data shows employee satisfaction rises roughly in line with FCR — and in some cases faster. A team with a high FCR tends to have a better working environment.

It motivates the right behaviors. An agent optimizing for FCR is an agent who thinks about root-cause resolution, not just closure. They ask clarifying questions, verify the fix before they hang up, and look for the "why" behind the issue rather than the fastest escape.

Limitations of FCR

Consistency is hard. There is no industry-standard definition of "first contact" or "resolved." One organization's 80% FCR may be calculated differently from another's 75%, making benchmarking across companies unreliable unless the methodology is specified.

It does not capture quality. A customer whose complex issue is rushed through with a technically "resolved" outcome but left feeling confused has still generated an FCR success. FCR tells you the issue did not come back; it does not tell you whether the resolution was actually good. Pairing FCR with CSAT and CES gives a more complete picture.

It can be gamed. Agents who know FCR is tracked may close cases prematurely, talk customers out of follow-ups, or mark issues as resolved before they actually are. Watch for FCR that trends upward while CSAT trends downward — that pattern usually points to gaming.

High FCR is not always a good sign. A high FCR rate driven by simple, repetitive contacts may indicate that self-service options are inadequate. If customers are calling to ask questions that a well-built knowledge base should answer, the FCR is high for the wrong reason.

How to improve FCR

Route to the right agent. FCR degrades when contacts land with agents who are not equipped to handle them. Skills-based routing — matching the customer's issue to the agent with relevant expertise — is one of the highest-leverage FCR levers. Platforms that use conversation history and topic data to route intelligently tend to have structurally higher FCR than those that rely on manual queue selection. For more on how Gladly approaches this, see the People Match reporting on FCR by agent.

Give agents full context. A significant share of repeat contacts happens because agents lacked the information to resolve the issue the first time. A unified customer profile — purchase history, prior conversations, channel history — means an agent walks into a contact already understanding the situation rather than spending the first two minutes collecting it.

Invest in self-service for repeatable issues. Contacts that hit the queue with questions answerable by an FAQ, a help article, or a chatbot are both high-FCR contacts and lower-complexity contacts. Deflecting those to self-service (where they can be resolved near-instantly) raises both FCR and agent availability for complex issues. See the Gladly guide on contacts per order for a framework on identifying which issues to deflect first.

Track FCR by agent and by topic. Aggregate FCR conceals a lot. An agent-level or topic-level view usually reveals that FCR is high in some areas and poor in others — which is actionable in a way that a blended number is not. The Gladly native FCR by Agent report is designed for exactly this.

Verify resolution before close. Agents who close contacts without confirming the issue is fully resolved create follow-up contacts that show up in the next day's queue. Building a verification step into the close routine — "is there anything else about this that isn't resolved yet?" — is low-cost and measurably effective.

AI and FCR

AI changes the FCR picture in two ways: by resolving more contacts autonomously, and by making agents more effective on the contacts they handle.

On autonomous resolution, AI handles Tier 1 contacts — order status, returns, password resets, account updates — quickly and without handoffs. When an AI model resolves one of these contacts without requiring a follow-up or transfer, it contributes positively to FCR performance. That raises the overall FCR average and also concentrates human agent time on the contacts that actually require expertise.

On agent effectiveness, AI surfaces relevant knowledge base content, customer history, and suggested responses during a live interaction, which means agents spend less time searching and more time resolving. The result is fewer cases where an agent closes the contact without the answer — which is the most common source of FCR misses.

The measurement implication: teams running AI alongside human agents should track FCR separately for AI-handled contacts and human-handled contacts. Blending them produces a misleadingly high aggregate number and obscures whether the human FCR is actually improving.