What is first contact resolution?

The share of support issues resolved in a single contact — no follow-ups, transfers, or reopens within the window — the completeness partner to FRT's speed.

How is FCR measured honestly?

Reopen windows (72 hours is common), customer-confirmed resolution, transfers counted as additional contacts, and deflection measured by whether issues actually ended.

How do you improve FCR?

Agent knowledge and authority at the first touch, skill-based routing, context carried across the journey, and mining the FCR-killers list — the issue types that always take three touches are product feedback.

Growth Marketing Glossary

First Contact Resolution (FCR)

F·C·Rnoun

Solved the first time they asked — the metric that counts journeys, not replies.

Schematic — one touch, resolved

Term: First Contact Resolution
Counts: Issues solved in one contact
Pairs with: FRT — speed plus completeness
Honesty test: Reopen windows and customer confirmation

Forms & parts of speech

FCR · noun

One-touch resolution share.

"FCR at 74% meant a quarter of customers asked twice - the effort metric wearing operations' clothes."

Definition in plain terms

First contact resolution (FCR) is the share of support issues resolved in a single contact — no follow-up needed, no transfer shuffle, no reopen within the window. It is FIRST-RESPONSE-TIME's necessary partner (speed says how fast someone answered; FCR says whether the answer ended the journey) and CUSTOMER-EFFORT's operational twin: every contact after the first is effort the customer didn't owe.

The mechanics

The definitional honesty decides the number: 'resolved' needs a reopen window (an issue closed and reopened in 72 hours wasn't resolved — closure-stuffing is the metric's classic game), customer confirmation where feasible (the post-resolution 'did this fix it?' beats the agent's optimism), and channel scoping declared (chat's one-session resolution differs from email's thread arithmetic). The levers map to why second contacts happen: knowledge and authority at the first touch (agents empowered to actually fix — the escalation-required design guaranteeing second contacts), routing that lands issues on the right skill first (the CONTACT-SCORING logic applied to queues), context carried so the customer never re-explains (the CRM's job, failed whenever 'can you repeat the issue?' opens a transfer), and root-cause mining — the FCR-killers list (the five issue types that always take three touches) being product feedback wearing a support metric. The deflection trap deserves its own warning: self-service and AI-assist lift FCR's denominator games — the bot that 'resolves' by exhausting the customer into leaving counts as resolution only in the dashboard (the EXIT-SURVEY entry's polite fictions, automated), so deflected contacts need their own success measurement (did the customer's issue actually end?). Read FCR beside CSAT and effort per issue type: high FCR with low satisfaction means fast wrong answers.

When it matters

FCR matters wherever support volume meets retention economics — each second contact costs service capacity and customer patience simultaneously, and the CHURN-RISK literature keeps finding effort among defection's best predictors. It matters most as a diagnostic engine: the FCR-killers list is the roadmap's cheapest input. The discipline is reopen-windowed honest counting, customer-confirmed resolution, deflection measured by issue-ending rather than contact-avoiding, and the FRT pairing that keeps speed and completeness answering together.

Worked example. A telecom-software support org celebrates 89% FCR while NPS sags - the audit finds the number was always costume: closures counted at agent click with no reopen window (22% reopen inside three days), the chatbot 'resolving' by attrition (deflected customers whose issues survived the deflection), and transfers resetting the contact count. The honest rebuild: 72-hour reopen windows, resolution confirmed by the customer's own 'yes, fixed' (or silence past the window), bot deflection measured by issue-ending follow-up sampling, and transfers counted as the second contacts they are. FCR restates at 61% - worse and finally true - and the killers list goes to work: five issue types drive 70% of multi-contact journeys, two of them product defects support had been absorbing silently. The product fixes ship; agent authority expands on the three authorization-gated types; FCR climbs to 78% real over three quarters, with CSAT finally moving in agreement - the metric and the customers describing the same world.

Failure modes to watch. Closures counted at agent click with reopens uncounted; bots 'resolving' by exhausting customers out of the queue; transfers resetting contact arithmetic; high FCR built of fast wrong answers the CSAT pairing would have caught; and the killers list unmined while product defects masquerade as support volume.

Synonyms & antonyms

Synonyms

first contact resolutionFCRone-touch resolution

Antonyms

first response time (the speed twin)contact deflection

Origin & history

FCR grew up in the call-center era — 'first call resolution' before channels multiplied the name — and the effort-economy research of the 2010s (the Effortless Experience lineage) promoted it from operations dashboard to retention predictor, reopen windows and confirmation discipline following.

Etymology: source.

Usage trends

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Common questions

What is first contact resolution?: The share of support issues resolved in a single contact — no follow-ups, transfers, or reopens within the window — the completeness partner to FRT's speed.
How is FCR measured honestly?: Reopen windows (72 hours is common), customer-confirmed resolution, transfers counted as additional contacts, and deflection measured by whether issues actually ended.
How do you improve FCR?: Agent knowledge and authority at the first touch, skill-based routing, context carried across the journey, and mining the FCR-killers list — the issue types that always take three touches are product feedback.

Related tools & calculators

toolA/B test sample size

Resources & people to follow

referenceWikipedia — First call resolution
referenceService-operations effort research (FCR-CSAT pairing)
referenceRGM analysis — count journeys, not replies; the killers list is the roadmap's cheapest input

Curated, non-competitor resources verified per term.

Related training

modulePerformance marketing

Disciplines

Areas of marketing where first contact resolution (fcr) is a core concern:

Performance marketingGrowth strategy

Sources

trendsGoogle Trends — "first contact resolution"