First call resolution is one of the most closely watched metrics in contact centre operations. It tells you, in a single number, whether your agents are equipped to close the loop on a customer issue in one contact — or whether customers are coming back because something was left unresolved. This guide covers the definition, the formula, documented benchmarks, and practical tactics for improving FCR without sacrificing other key metrics.

What Is First Call Resolution?

First call resolution (FCR) — also called first contact resolution when applied across channels — is the percentage of customer contacts that are fully resolved on the initial interaction, without the customer needing to call back, follow up, or be transferred to a different team to reach a conclusion.

"Resolved" has a specific meaning in FCR measurement. A contact counts as resolved if:

• The customer's issue, question, or request was addressed completely during that call.
• No callback or repeat contact about the same issue occurred within the measurement window (commonly 7 to 30 days).
• The customer did not need to be escalated to a supervisor or a different team after the call ended.

What counts as "the same issue" requires a consistent definition before you can track FCR reliably. Many teams use a combination of CRM tagging and repeat-call detection to flag likely re-contacts. Without that consistency, FCR scores are not comparable across periods.

FCR is considered one of the top contact centre KPIs because it sits at the intersection of two things that matter to both operations and customers: efficiency (fewer contacts per issue means lower cost) and quality (customers who get their issue resolved the first time are more satisfied). It is also a leading indicator — improving FCR tends to move customer satisfaction and cost-per-contact in the right direction simultaneously.

How to Measure FCR

There is no single universally agreed measurement method for FCR. The three most common approaches are described below. Each has different data requirements and produces slightly different numbers, so choose one method and apply it consistently.

Formula

FCR (%) = (Calls resolved on first contact ÷ Total calls handled) × 100

Method 1: Post-call survey

At the end of the interaction, ask the customer a single question: "Was your issue fully resolved today?" (yes / no). Calculate the percentage of yes responses. This method captures the customer's own perception of resolution, which is the most commercially meaningful measure. Its limitation is survey response rate — if only a fraction of customers respond, the sample may not represent all calls.

Method 2: Callback tracking

Flag any customer who contacts you again within a defined window (e.g., 7 days) about the same issue. Calls that do not trigger a repeat contact within the window are counted as resolved. This method uses telephony and CRM data rather than surveys, so it covers all interactions. The challenge is accurately identifying repeat contacts — the same customer may call from a different number, or contact via a different channel.

Method 3: Repeat contact analysis

Pull contact history per customer and identify contacts where the same reason code or topic appears more than once within the measurement window. Contacts without a matching follow-up are counted as resolved. This is well suited to teams with structured call-reason tagging in their CRM. It requires consistent use of reason codes by agents, which often needs to be enforced through training and QA.

Worked example

In a week, your team handles 1,000 calls. Post-call surveys are completed by 400 customers. Of those, 300 say their issue was fully resolved. Meanwhile, callback tracking shows 80 of the 1,000 calls resulted in a repeat contact within 7 days.

• Survey-based FCR = (300 ÷ 400) × 100 = 75%
• Callback-based FCR = ((1,000 − 80) ÷ 1,000) × 100 = 92%

The gap between these two figures is common, and it is informative. The survey asks whether the customer felt resolved; the callback method measures whether they called again. Combining both provides the most complete picture: a high callback-based FCR alongside a lower survey-based FCR suggests calls are being closed but customers leave uncertain about whether their issue is truly resolved.

FCR Benchmarks

The industry average for first-contact resolution is generally cited in the range of 70–75% across contact centre research. That means roughly one in four to one in three contacts requires a follow-up interaction before the issue is fully closed.

This range should be treated as a general orientation rather than a hard target. FCR varies significantly by:

• Industry. Technical support, healthcare, and financial services tend to have lower FCR because issues are inherently more complex. Retail and simple billing queries tend to score higher.
• Contact type. Inbound voice typically scores lower than digital self-service channels for simple queries; the inverse may be true for complex issues where voice allows faster clarification.
• Measurement method. As the worked example above shows, survey-based and callback-based FCR can diverge substantially for the same operation.
• Definition of "resolved." A 7-day window and a 30-day window will produce different FCR numbers for the same team.

Comparing your FCR to a published industry average is less valuable than tracking your own rate over time and understanding why it moves in either direction.

Why FCR Matters

Customer satisfaction

There is a consistent relationship between FCR and customer satisfaction scores. When a customer's issue is resolved on the first contact, the experience is perceived as lower effort and higher quality — both of which drive CSAT and NPS upward. The reverse is also true: each additional contact required to resolve an issue erodes satisfaction, often disproportionately. A customer who calls three times about the same issue is likely to leave that series of interactions as a detractor regardless of how individual calls were handled.

Cost reduction

Every repeat contact about the same issue represents a cost with no corresponding value delivered. If a contact costs a fixed amount to handle and 25% of your volume is repeat contacts, you are spending a quarter of your contact-handling budget re-solving issues that should already be closed. Improving FCR by even a few percentage points reduces total contact volume, which flows directly into cost-per-contact and staffing requirements.

Agent morale

Agents who can resolve issues on the first call experience more positive interactions and less frustration. Repeat-contact calls often start adversarial — the customer is already frustrated from their previous contact — which creates a harder working environment. Teams with high FCR tend to report higher job satisfaction, which in turn supports lower attrition. This is a less frequently cited benefit of FCR improvement, but the operational cost of agent turnover makes it significant.

How to Improve First Call Resolution

Improving FCR requires understanding why calls are not being resolved on the first contact. The tactics below address the most common root causes.

1. Skills-based routing

Routing the right call to the right agent is the single most reliable way to increase FCR. When a customer with a billing dispute reaches a technical support agent, or a complex product question lands with a new agent in their first week, the probability of first-contact resolution drops sharply. Skills-based routing matches the call type, language, product line, or customer tier to agents whose skills and knowledge align — increasing the chance that the first agent to handle the call is equipped to close it.

2. Agent empowerment and authorisation

One of the most common causes of low FCR is an agent who identifies the resolution but lacks the authority to execute it. If an agent needs supervisor sign-off to issue a refund under a certain amount, waive a fee, or make a policy exception, that call is not resolvable on the first contact without the supervisor being present. Reviewing escalation policies and expanding agent authorisation thresholds within defined boundaries is often a fast path to FCR improvement.

3. Knowledge base quality and accessibility

Agents who cannot quickly find accurate, up-to-date information during a call will either guess, put the customer on hold repeatedly, or promise to call back — none of which support first-contact resolution. A well-structured internal knowledge base, integrated directly into the agent desktop and searchable in real time, reduces handle time and improves answer accuracy simultaneously.

4. Root cause analysis of repeat contacts

Pull a sample of repeat contacts and categorise them by issue type, the agent who handled the first call, the call reason code, and the channel. Patterns usually emerge quickly: a specific product generates a disproportionate share of repeat contacts, a particular process step is confusing customers, or a subset of agents consistently has lower FCR than peers. Addressing the systemic cause is more effective than coaching individual calls.

5. IVR design and self-service routing

An IVR that routes calls incorrectly is an FCR problem before the agent answers. Customers who navigate an IVR tree and reach the wrong team face immediate re-routing or transfer — both of which depress FCR. Auditing your IVR against actual call reason data and simplifying or restructuring menu options to match how customers describe their issues (not how the business categorises them internally) can lift routing accuracy and, with it, FCR.

6. AI agent assist with real-time prompts

AI agent-assist tools analyse the conversation in real time and surface relevant knowledge base articles, suggested responses, compliance prompts, and next-best-action guidance while the call is still in progress. For agents handling a wide variety of issue types, or for new agents who have not yet built deep product knowledge, this real-time support increases the probability that the right answer is given during the call rather than after a callback.

7. Post-call analysis and quality monitoring

Reviewing calls where FCR failed — either through survey feedback or repeat-contact flagging — creates a feedback loop that surfaces training gaps, process failures, and knowledge base deficiencies. Structured post-call analysis should be part of your QA process, not a separate exercise. When FCR data is linked to call recordings and transcript analysis, patterns become visible that would otherwise require manual sampling across thousands of calls.

For a broader view of how these tactics fit into contact centre operations, see our guide to call center metrics.

FCR vs AHT: The Relationship

Average handle time (AHT) measures the total time an agent spends on a contact, including talk time, hold time, and after-call work. FCR and AHT are related metrics, but they can pull in opposite directions — and understanding that tension is important before making changes to either.

The straightforward case is that resolving an issue on the first call takes more time per call than a quick interaction that does not fully close the issue. An agent who spends an extra two minutes confirming all aspects of a customer's query are addressed, explaining the resolution clearly, and ensuring nothing is left open will have a higher AHT than an agent who answers the initial question and ends the call. The first agent achieves higher FCR; the second generates a lower AHT but higher repeat-contact volume.

When teams are rewarded primarily on AHT, agents have an implicit incentive to keep calls short — which can depress FCR. The reverse is also possible: an agent who over-explains or spends unnecessary time on resolved calls inflates AHT without improving FCR.

The practical approach is to monitor FCR and AHT together, not in isolation, and to look at cost per resolution rather than cost per call. A team with a 20% higher AHT but a 15% higher FCR may be handling fewer total contacts and spending less per resolved issue than a team optimised purely for call speed. For more on handle time measurement and trade-offs, see our guide to average handle time.

Frequently Asked Questions