What Is First Call Resolution (FCR)?

First call resolution (FCR) — sometimes called first contact resolution — is one of the most-watched metrics in customer support and contact centers. It answers a deceptively simple question: when a customer reaches out with a problem, do you solve it the first time, or do they have to come back?

A precise definition

FCR is the percentage of customer issues resolved during a single, initial interaction, without the customer needing to follow up about the same issue. "First call" is a legacy term from phone support, but the concept now spans every channel — phone, chat, email, and self-service. The customer's perspective is what counts: if they have to reopen a ticket, call back, or escalate, the issue was not resolved on first contact, even if your agent felt the conversation went well.

How to calculate FCR

The standard formula is:

• FCR rate = (issues resolved on first contact ÷ total issues) × 100

For example, if your team handled 1,000 support contacts in a week and 720 were resolved without any repeat contact, your FCR is 72%. The hard part is not the arithmetic — it is deciding what "resolved" means and how you detect a repeat contact. Two common measurement approaches exist:

• Customer-reported FCR: a post-interaction survey asks, "Was your issue resolved today?" This captures the customer's truth but depends on survey response rates.
• Operational FCR: your CRM or ticketing system flags repeat contacts from the same customer about the same issue within a window (often 24–72 hours, or 7 days). This scales to 100% of contacts but can misclassify unrelated follow-ups.

Mature teams reconcile both. A wide gap between customer-reported and operational FCR usually means your tagging or resolution definitions need work.

Why FCR matters

FCR sits at the intersection of cost and experience, which is rare for a single metric.

• Customer satisfaction: repeat contacts are a top driver of frustration and churn. Resolving on first contact strongly correlates with higher CSAT and NPS.
• Cost efficiency: every repeat contact is duplicated handling cost. Lifting FCR a few points can meaningfully reduce total contact volume and staffing pressure.
• Agent effectiveness: FCR reflects whether agents have the knowledge, tools, and authority to actually close issues, rather than punting them to another queue.
• Process diagnosis: a low FCR for a specific topic points to a broken workflow, a confusing product area, or a knowledge gap — it is a map of where to fix things.

What counts as a "good" FCR rate?

There is no universal target, because it depends on issue complexity and how strictly you define resolution. A widely cited industry benchmark for contact centers is roughly 70–75%, but B2B and technical-support teams handling complex cases often run lower by design, while transactional support can run higher. The more useful goal is a steady upward trend in your own FCR alongside stable or rising CSAT — not a borrowed number. Beware of gaming: if agents close tickets prematurely to look good, FCR rises while customer-reported resolution falls.

How to improve first call resolution

Improving FCR is mostly about removing the reasons issues bounce back:

• Find the repeat-contact drivers. Tag and analyze why customers return. A handful of root causes usually explains most repeats.
• Strengthen your knowledge base. Agents resolve more on first contact when answers are accurate, current, and easy to find.
• Empower the front line. Give agents the permissions and decision rights to resolve common cases without escalation.
• Reduce misrouting. Getting the customer to the right person the first time is half the battle.
• Coach with real conversations. Reviewing actual calls against a consistent quality rubric surfaces the specific behaviors — discovery, clear explanation, confirming resolution — that drive first-contact closure.

Where conversation analysis fits

FCR is reported from your helpdesk or CRM, but the why behind it lives in the conversations themselves. This is where call-review tooling complements your support stack. MeetGrade records and transcribes Zoom, Google Meet, and phone calls, then scores them against custom checklists you define — so a quality lead can review, for instance, whether the agent confirmed the issue was fully resolved before ending the call. Its AI coaching highlights recurring gaps across a team, and conversation metrics make patterns visible at scale. For sales-oriented teams that also track call quality, the same approach links day-to-day coaching to outcomes. Used alongside your ticketing system's FCR reporting, it helps turn a single number into specific, fixable behaviors.

FCR in context

FCR is most powerful when read next to its neighbors: average handle time (AHT), CSAT, and overall ticket volume. Optimizing FCR in isolation can backfire — for instance, agents may extend handle time to force a resolution. Track them together so you understand the trade-offs and protect the customer experience while you tighten efficiency.

First call resolution rewards getting it right the first time, which is exactly what customers want. Reporting tools tell you your rate; reviewing the actual conversations tells you how to raise it. If your team wants to connect FCR coaching to what is really happening on calls, exploring a call-analysis tool like MeetGrade is a reasonable next step.