First contact resolution

Contact Center MetricsFCRalso: first call resolutionalso: FCR

In one sentence

First contact resolution is the share of customer issues fully resolved in a single interaction, with no callback, no follow-up and no second attempt, and it only holds up when it is measured across every channel rather than within one.

Last reviewed 4 August 2026

Not to be confused with Resolution rate.

Definition

First contact resolution is the share of customer issues that get fully sorted in a single interaction, with no callback, no follow-up and no second attempt.

It is widely regarded as the most useful single quality metric in a contact center, because it moves with satisfaction and with cost at the same time. It is also unusually easy to measure badly.

The measurement problem

  • Resolution can be self-reported by the agent, which overstates it.
  • It can be inferred from the absence of a repeat contact inside a window, which is more honest and forces a choice of window. Seven days is common and arbitrary.
  • It can be surveyed directly, which is accurate and expensive.
  • Channel-blind measurement is essential. A call resolved on the phone, followed by an email about the same issue, is not first contact resolution, and single-channel reporting misses it entirely.

Why it matters more than most metrics

  • Repeat contacts are expensive twice. The second contact costs money, and the customer is now annoyed.
  • It correlates with satisfaction more reliably than speed metrics do.
  • It is difficult to game without genuinely improving, unlike handle time, which can be cut by ending interactions early.

The on-site analogue

  • A website voice agent has no callback concept. The equivalent question is whether the visitor got their answer and stopped hunting.
  • The measurable proxy is whether they asked a follow-up on the same topic, or left, or converted.
  • Repeat visits to the same page after a conversation are the closest signal to a repeat contact.

Common misconception

That a high FCR means the agent was skilled. It frequently means the information was available and findable, which is a knowledge management outcome rather than a personnel one. The lever that moves it most is usually the content, not the training.

Why it matters commercially

FCR is the metric that captures whether a system actually helps, as distinct from whether it responds quickly or handles volume. That is why it belongs next to any efficiency number in a report: it is the honest counterweight to handle time and containment, both of which improve when you simply end contacts sooner.

In voice specifically

On a website there is no callback to count, so first contact resolution has to be read differently. The signal is behavioral rather than reported: did the visitor stop asking about the same thing, leave the page, or convert. A return to the same page after a conversation is the nearest thing to a customer coming back through a second door.

Where AsqVox fits

Transcripts and sentiment in the Orb dashboard are the raw material for assessing whether a conversation resolved something or merely ended. That is the difference first contact resolution is trying to catch, read from what was actually said rather than from an agent ticking a box.

Visual

Resolved, or just finished

Resolved, or just finishedOne issue, oneinteraction,marked resolvedCounted as FCRGenuinely resolvedOne interaction, then nothing for seven daysReal first contact resolutionNo repeat contactSatisfaction holdsOnly apparently resolvedSame issue returns by email three days laterCounted as FCR under single-channel reportingNot resolved, a different doorChannel-blind measurement misses it

Single-channel reporting cannot tell these two apart. Only one of them resolved anything.

Both journeys arrive at the same counter, drawn the same size on purpose. The three ways to measure resolution rank by reliability: agent self-report overstates it, absence of a repeat contact inside a window is better but needs a window (seven days is common and arbitrary), and a direct survey is accurate and expensive. The rule under all of them: measure across every channel, or you are measuring the front door only.

Statistics

Every figure carries its source and year. Vendor numbers are labelled as vendor numbers, and where no reliable figure exists this page says so rather than borrowing one.

There is no reliable current cross-industry FCR benchmark. Circulating figures trace to vendor surveys and industry association aggregates that use inconsistent definitions.

-no reliable figure

The absence is itself informative. Because definitions vary so widely, cross-company comparison is close to meaningless and internal trend is the only useful use. If a percentage is quoted at you, ask which of the three measurement methods produced it.

A call handled by a person costs roughly USD 7 to USD 12.

USD 7 to 12industry range

Widely cited industry range, 2025 - Not an audited figure. A repeat contact therefore doubles the cost of an unresolved issue, which is why FCR reads straight into money. Run a real business case on local labor cost rather than the published range.

A call handled by a voice agent costs roughly USD 0.40.

USD 0.40industry range

Widely cited industry range, 2025 - Same caveat. Treat the ratio between the human and agent figures as directional rather than treating either absolute number as precise.

Automation containment benchmarks, for context: mature deployments run roughly 70 to 80 percent, average deployments 40 to 55 percent, and rule-based systems under 35 percent.

70 to 80% mature, 40 to 55% averageindustry range

Industry-reported ranges, 2025 - Industry-reported rather than audited. Quoted here because FCR is read alongside containment: a high containment number paired with a low FCR means conversations are ending, not resolving.

Repeat-contact windows of seven days are common in practice for inferring resolution from the absence of a return contact.

7-day windowindustry range

Industry convention, 2025 - A convention rather than a research-derived figure. Because the window is a free choice, two organizations reporting FCR the same way can still produce different numbers from the same behavior.

Examples

In practice

A utility reports strong FCR from agent self-reporting. Cross-channel analysis using a seven-day repeat-contact window reduces the figure substantially, because a meaningful share of phone resolutions generated follow-up emails. The reporting method is changed and the number drops. Nothing about the service got worse. The measurement got honest, and the top follow-up reasons became the roadmap.

The everyday version

First contact resolution is whether the customer problem was actually sorted the first time they got in touch. The trap is counting a call as resolved because it ended, when the customer simply gave up and emailed you two days later instead. If you only look at the phone, that second email is invisible and the number looks great.

Usage

Who says it

  • Contact center and CX leaders, who treat it as a primary quality metric.
  • It appears in operational reporting and in vendor service level agreements, usually next to containment and CSAT.

Where it turns up

  • Next to containment, resolution rate, repeat contact rate and CSAT, together with the measurement methodology.
  • The measurement methodology clause matters more than the target number. A generous-looking FCR target under a single-channel, self-reported definition is worth less than a lower number measured across every channel.

Common misuse

  • Measuring within one channel only, so a phone resolution followed by an email counts as a success.
  • Relying on agent self-report, which overstates resolution.
  • Comparing FCR across organizations that define it differently, which produces a comparison of definitions rather than of service.

Questions people ask

What is first contact resolution?

First contact resolution is the share of customer issues fully resolved in a single interaction, with no callback, no follow-up and no second attempt. It is regarded as the most useful single quality metric in a contact center because it moves with satisfaction and cost at once, and it only holds up when measured across every channel.

How is first contact resolution measured?

Three ways, in rising order of reliability. Agent self-report, which overstates it. Absence of a repeat contact inside a window, which is more honest and needs a chosen window, with seven days common and arbitrary. Direct survey, which is accurate and expensive. All three fail if measurement is single-channel, because a phone fix followed by an email is not resolution.

Is there a good FCR benchmark?

No reliable cross-industry benchmark survives scrutiny. Circulating figures come from vendor surveys and association aggregates with inconsistent definitions, so cross-company comparison is close to meaningless. Internal trend, measured the same way over time, is the only defensible use.

What is the difference between first contact resolution and resolution rate?

Resolution rate asks whether an issue was ever resolved. First contact resolution asks whether it was resolved the first time, in one interaction, with no return. An issue solved on the third attempt counts fully toward resolution rate but not toward FCR, which is exactly why the two get conflated and why FCR is the harder number to hit.

Share this definition

Last reviewed 4 August 2026. Written and reviewed by Dhruv Dholakia, founder of AsqVox.