First-contact resolution (FCR): what it is, how to measure it, and what a good rate looks like

First-contact resolution is one of the most useful metrics in customer service — and one of the most frequently misunderstood. It sounds simple: did you resolve the customer's issue the first time they contacted you? In practice, measuring it accurately, interpreting it correctly, and using it to improve your operation requires more care than the definition suggests.

This article explains what FCR is, how it is calculated, what benchmarks are relevant for ecommerce and technical support specifically, what drives it up or down, and how it connects to the other metrics that matter — particularly CSAT.

What is first-contact resolution?

First-contact resolution — also called first call resolution or FCR — measures the percentage of customer contacts that are fully resolved in a single interaction, without the customer needing to follow up. A contact is considered resolved at first contact if the customer's issue is addressed completely during the initial interaction and they do not need to contact you again about the same issue.

FCR measures not just whether you responded — but whether you actually solved the problem.

The distinction matters. A fast response that partially addresses the issue is not a first-contact resolution. A slow response that resolves the issue completely is. FCR is a quality metric, not a speed metric — although it is related to speed in the sense that the more capable the agent, the faster they can reach resolution.

How is FCR calculated?

FCR is calculated as:

FCR = (Contacts resolved at first interaction ÷ Total contacts) × 100

Where “resolved at first interaction” means the customer did not contact you again about the same issue within a defined window — typically 7 days.

In practice, measuring FCR accurately is more complex than calculating CSAT. You need to identify repeat contacts — contacts from the same customer about the same issue within your measurement window — and exclude them from the resolved-at-first-contact count. This requires your ticketing system to link contacts from the same customer and to tag contact types consistently enough to identify the same issue across multiple interactions.

There are two common approaches to measuring FCR. The first — and more accurate — is tracking repeat contacts in your ticketing system over the defined window. The second is surveying customers at the end of an interaction: “Was your issue fully resolved today?” Both have limitations. Ticketing-based measurement depends on consistent contact tagging. Survey-based measurement depends on customer honesty and response rates. Many operations use both as a cross-check.

What is a good FCR rate?

FCR benchmarks vary significantly by channel, contact type, and industry. A live chat FCR rate is typically higher than an email FCR rate — because live chat allows for a more complete conversation in a single interaction. A technical support FCR rate is typically lower than an ecommerce FCR rate — because technical issues are more complex and more likely to require escalation.

Ecommerce FCR benchmarks

For ecommerce customer service — order queries, returns, complaints, and product questions — a first-contact resolution rate above 85% is generally considered strong. Above 90% is excellent. Below 75% suggests significant process or knowledge gaps.

Technical support FCR benchmarks

For first-line technical support — L1, FCR rates are generally lower than ecommerce because technical issues are more complex and some contacts genuinely require escalation to a second-line specialist. A first-contact resolution rate of 85 to 95 percent at L1 is considered strong for most hardware and software products. Below 70 percent at L1 suggests either that the knowledge base is inadequate or that too many contacts are being escalated that could be resolved at first line.

The right FCR benchmark for technical support also depends on product complexity. A simple consumer hardware product should have a higher L1 FCR rate than a complex enterprise software platform. Setting FCR targets without accounting for product complexity leads to agents attempting to resolve contacts they should escalate — which produces poor outcomes even when the FCR rate looks healthy.

What drives FCR up or down?

FCR is primarily a function of three things: agent knowledge, decision-making authority, and process clarity.

Agent knowledge

The most consistent driver of FCR is how well agents know the product, the procedures, and the common failure modes. An agent who can answer a product question accurately without putting the customer on hold, process a return without checking the policy, and diagnose a technical issue without escalating to a colleague will resolve a significantly higher proportion of contacts at first contact than one who cannot. FCR is the most direct output of knowledge base quality — and therefore the most direct measure of onboarding effectiveness.

Decision-making authority

Agents who are empowered to make decisions — to approve a refund, to offer a goodwill gesture, to accept a return outside the standard policy in exceptional circumstances — resolve more contacts at first contact than agents who must escalate every non-standard decision for approval. Overly restrictive agent authority is one of the most common and most avoidable causes of low FCR. The fix is not always more knowledge — sometimes it is more trust.

Process clarity

Clear, documented procedures for every contact type reduce the number of cases where an agent is uncertain what to do and defaults to escalation. The less ambiguity in the procedure, the more confidently agents can act and the higher the FCR rate. Procedures that are unclear, inconsistent, or out of date produce low FCR even when agents are knowledgeable and motivated.

How FCR relates to CSAT and customer loyalty

FCR and CSAT are closely related but not identical. A contact resolved at first contact is likely to produce a higher CSAT score than one requiring follow-up — but FCR alone does not guarantee a high CSAT. An issue resolved quickly but handled coldly, or resolved accurately but communicated poorly, will still produce a low CSAT score.

The more important relationship is between FCR and customer loyalty. Research consistently shows that customers who have to contact a company multiple times about the same issue are significantly more likely to churn than those whose issue is resolved at first contact — regardless of how satisfied they say they were with each individual interaction. A customer who rates each interaction 4 out of 5 but contacts you three times before their issue is resolved is a churn risk. A customer who rates a single interaction 3 out of 5 but has their issue fully resolved is not.

Customers do not remember individual interactions as much as they remember whether their problem was eventually solved — and how many times they had to ask.

This asymmetry is why FCR is one of the most commercially significant metrics in customer service. It is not just an operational efficiency measure — it is a loyalty predictor. Improving FCR from 75% to 85% does not just reduce repeat contact volume by a third. It reduces churn risk for a significant proportion of your customer base.

How to improve your FCR rate

The most reliable levers for improving FCR are the same factors that drive it — knowledge, authority, and process clarity.

• Audit your repeat contacts. Identify the contact types that generate the most repeat interactions and understand why. Is the initial response inaccurate? Is the procedure unclear? Is the agent lacking the authority to resolve the issue? The answer determines the fix.
• Invest in knowledge base depth. The most common cause of low FCR is an incomplete or out-of-date knowledge base. Agents who cannot find the answer escalate or guess. Neither produces first-contact resolution. Regular knowledge base reviews — particularly after product changes, policy updates, or peak periods — maintain the accuracy that FCR depends on.
• Widen agent decision-making authority where safe to do so. Identify the non-standard decisions that agents most frequently escalate and assess whether those decisions could be made at first contact within defined parameters. Empowering agents to approve refunds up to a certain threshold, for example, removes an escalation trigger that generates repeat contacts without meaningful financial risk.
• Track FCR by contact type. An aggregate FCR rate hides the contact types where resolution is consistently failing. Tracking FCR at the contact type level identifies precisely where knowledge or process improvements will have the most impact. An 80% overall FCR rate that hides a 55% FCR rate on returns queries is not the same as a genuinely uniform 80%.