First call resolution (FCR) is a support metric that measures the percentage of customer issues fully resolved during the first contact, with no follow-up, callback, or additional ticket required. It matters because it reflects operational efficiency, agent competence, and the effectiveness of a support team’s tools and processes. Support leaders track the first contact resolution rate to spot process gaps that a satisfaction score alone cannot reveal.

What Is First Call Resolution?

The term “first call” is a holdover from phone-only support desks. Today the same idea spans every channel, so many teams say “first contact resolution rate” instead, since it covers chat, email, and messaging alongside voice. Whatever label a team uses, the question stays the same: did the customer get a complete answer the first time, or did the issue return for a second round?

The FCR Calculation Formula

The standard FCR calculation formula is simple on paper. Divide the number of contacts resolved on first contact by the total number of eligible contacts in the period, then multiply by 100 to express it as a percentage.

The formula is simple, but the number it produces is only as reliable as the definitions feeding it. Two teams can run the identical FCR calculation formula and land on different results simply because they disagree about what counts as resolved.

What Counts as a Resolution

Before any first contact resolution rate figure means anything, a team needs a written, consistent definition of “resolved.” A resolution generally means the customer’s issue was fully addressed, they confirmed or implicitly accepted the outcome, and no further action was required from either side.

A resolution typically excludes cases where the agent gave a partial answer and promised a callback, where the issue was escalated to a specialist, where the customer reached out again within a short window for the same root cause, or where a ticket closed by system timeout rather than genuine confirmation. Counting these as resolved inflates the first-contact resolution rate without reflecting real-world experience.

Practical Tips for Accurate FCR Tracking

A few practical habits keep first contact resolution rate reporting honest and genuinely useful for daily operational decisions.

• Audit a sample of “resolved” tickets each month to confirm agents and systems apply the resolution definition the same way.
• Pair the FCR calculation formula with average handle time and CSAT in the same dashboard so no single metric is read alone. This gives support teams a clearer view of first call resolution and customer retention rather than relying on one metric in isolation.
• Build reopen tracking into the ticketing system itself, since manual review is easy to skip once volume climbs.
• Give agents visibility into their own first contact resolution rate so the metric drives coaching rather than quota pressure.
• Revisit exclusion criteria annually, since channels, products, and volume shift enough to make old rules outdated.

First Contact Resolution Rate vs. AHT, CSAT, and NPS

FCR is often reported alongside average handle time, customer satisfaction score, and net promoter score, but each metric answers a different question, and none can substitute for the others. Looking at these metrics together can also support a more effective quality assurance approach for customer service by showing where support performance needs improvement.

A strong first contact resolution rate can coexist with rising average handle time, since thorough resolution sometimes takes longer. A short average handle time paired with a weak FCR calculation formula result often signals agents closing tickets too early. Reading these metrics together gives a clearer picture.

Typical FCR Benchmarks by Industry

Benchmark ranges vary by channel and industry, so context matters more than chasing one universal target. Phone support commonly lands between 70 and 75 percent for a healthy first contact resolution rate, while chat and email, involving more back and forth, often sit lower, in the 40 to 65 percent range.

Technology and telecom support, where issues run complex, frequently reports FCR in the 65 to 75 percent band. Retail support, handling routine order and billing questions, often reaches 75 to 80 percent. These figures stay directional, since organizations define “resolved” differently.

Common FCR Measurement Pitfalls

Several recurring errors quietly distort a reported first contact resolution rate. The most common is failing to track reopened tickets, so an issue that returns days later still counts as a first contact success even though the customer had to reach out again.

Another mistake is conflating FCR with average handle time, treating a fast close as good regardless of the root cause. Some teams apply inconsistent eligibility rules across channels, which skews the true first contact resolution rate.

How to Measure FCR Correctly

Building a trustworthy FCR calculation formula into regular reporting takes more than a single spreadsheet formula. These steps outline a defensible measurement process.

1. Define what counts as a resolution: document the exact conditions, customer confirmation, no further action needed, no escalation, that qualify a contact as resolved, and share that definition across every team.
2. Apply the FCR calculation formula consistently: use the same numerator and denominator logic across channels and agents every time you calculate the rate.
3. Set clear exclusion criteria: decide which contacts are ineligible, such as informational calls or system-generated pings, and apply those exclusions the same way each period.
4. Track reopened tickets over a defined window: monitor whether a “resolved” contact generates a related follow-up within a set number of days, and subtract confirmed reopens.
5. Segment results by channel and issue type: report first contact resolution rate separately for phone, chat, and email, since blending channels hides where the process breaks down.
6. Report on a fixed, recurring cadence: publish FCR weekly or monthly using the same methodology, so trends reflect real performance rather than shifting definitions.

FAQs

What is a good first contact resolution rate?

A good first contact resolution rate typically falls between 70 and 80 percent for phone support, though acceptable ranges vary by channel and industry. Chat and email often run lower due to more back and forth. Context, consistent definitions, and trend direction matter more than hitting one universal number.

How do you calculate the FCR formula manually?

Count the total contacts resolved on first contact during a period, divide that number by the total eligible contacts for the same period, then multiply the result by 100. This produces a percentage. Accuracy depends entirely on having a clear, written, and consistently applied definition of resolved.

Does FCR include chat and email, or only phone calls?

Modern FCR measurement includes phone, chat, email, and messaging channels, which is why many teams now say first contact resolution rate instead of first call resolution. The calculation logic stays the same across channels, though eligibility rules and typical benchmark ranges usually differ by channel type.

Why is FCR different from average handle time?

Average handle time measures how long a contact takes, while FCR measures whether the issue was actually closed. A short handle time can hide an unresolved issue, and a longer one can still reflect a thorough, correct resolution. Tracking both together avoids rewarding speed over accuracy.

What causes reported FCR numbers to be inaccurate?

Reported FCR numbers often become inaccurate when reopened tickets are not tracked, when exclusion rules are applied inconsistently across channels, or when contacts are marked resolved by system timeout rather than genuine customer confirmation. Any of these gaps can meaningfully inflate the reported first contact resolution rate.