Contact centre metric

First call resolution (FCR)

Q: How is first call resolution measured?

FCR is measured by three main methods: (1) Customer survey, asking 'Was your issue resolved in one contact?' immediately after the call. Fast but subject to response bias. (2) ACD/CRM contact matching, identifying repeat contacts from the same customer within a defined window (1 day, 7 days). Objective but requires good data linkage. (3) Agent declaration, where the agent flags at close of call whether the issue was fully resolved. Subject to agent gaming. Contact matching against CRM data is the most reliable method but requires good customer identification at contact start.

Q: What is the most common cause of poor first call resolution?

The four most common root causes of poor FCR are: (1) Agent authority gaps, where agents cannot resolve the issue without escalating or transferring, which breaks the call. (2) System access gaps, where agents cannot access the information they need (account history, case notes, prior calls). (3) Knowledge gaps, where agents do not know the answer to the customer's question. (4) Process complexity, where the resolution requires actions that cannot be completed in a single call (e.g. a manual process that takes 24 hours). Authority and access gaps are the most fixable and often produce the fastest FCR improvements.

First call resolution is the percentage of contacts where the customer's issue is fully resolved in a single interaction, with no need to call back. It is simultaneously a quality metric, a cost metric, and a customer experience metric. Improving FCR reduces volume, lowers cost per contact, and increases satisfaction.

Formula and definition

FCR formula

FCR = (Resolved contacts ÷ Total contacts) × 100

Strict definition

Resolved = no repeat contact within 24 hours on the same issue. Fast to measure but misses contacts that require a 2-day process cycle.

Standard definition

Resolved = no repeat contact within 7 days. More representative of true resolution but harder to attribute to a single agent or team.

Worked example

1,000 contacts in a day · 700 with no repeat within 7 days = 70% FCR

The repeat contact rate is not the same as (1 − FCR). A 70% FCR means 30% of contacts are not fully resolved in one call. However, not all unresolved contacts produce a repeat, because some customers do not call back. The repeat contact rate typically runs at 60–70% of (1 − FCR). Measure both independently.

FCR as a staffing cost lever

FCR improvement is one of the most direct levers for reducing staffing requirements without cutting service levels. Each percentage point of FCR improvement eliminates a portion of repeat contact volume from your queue.

The FCR volume reduction model

Current repeat rate

30%

30% of contacts are customers who already called

Current FCR

70%

70% of contacts are fully resolved in one call

Target FCR

80%

+10 percentage points improvement

At 30% repeat rate and 70% FCR: 30% of volume = repeat contacts. Improving to 80% FCR reduces repeat contacts by ≈33%, removing approximately 10% of total volume. On a 100-agent operation, that is approximately 10 fewer agents needed at the same service level and AHT.

Model your FCR impact →

FCR benchmarks by operation type

Operation typeTypical FCR rangeNotes

Simple transactional (billing, account updates)80–90%High FCR achievable; issue complexity is low

General customer service (retail, e-commerce)70–80%Good FCR; clear resolution criteria

Financial services (banking, insurance)65–78%Regulatory requirements add process complexity

Broadband / telecom technical support55–70%High complexity; network faults require engineer visits

Healthcare patient services65–75%Many queries require clinical input or callback

B2B / complex sales support50–65%Multi-stage processes common; internal hand-offs frequent

These are attainable FCR rates, not theoretical maxima. Operations below the lower bound typically have agent authority, system access, or knowledge base gaps that are fixable.

How to measure FCR

Post-call survey

Medium reliability

Ask the customer immediately after the call: 'Was your issue fully resolved today?'

Pros

Fast, captures customer perception, low cost

Cons

Response bias (5–15% response rate); customers who abandon don't respond; emotional state affects answers

Contact matching (CRM)

High reliability

Identify customers who contact again within 7 days on the same reason code or issue type

Pros

Objective; no customer action required; scales automatically

Cons

Requires good customer ID linkage; depends on accurate issue tagging; multi-channel repeat harder to catch

Agent declaration

Low reliability

Agent selects 'Resolved / Unresolved' at the end of each call in the ACD or CRM

Pros

Instant; zero lag; easy to implement

Cons

Subject to gaming, as agents overstate resolution to improve scores; must be validated against actual repeat rate

Best practice: Use CRM contact matching as your primary FCR measure and post-call survey as a secondary validation. The two should track together within 5–8 percentage points. If they diverge significantly, investigate whether your issue categorisation or customer ID linkage is breaking down.

Six drivers of poor FCR

High impact

Agent authority gaps

Define authority tiers clearly. Empower agents to waive fees, credit accounts, or make decisions up to a defined threshold without escalation. Every escalation or transfer is a near-certain FCR failure.

High impact

System and data access gaps

Agents who cannot see a customer's account history, prior contacts, or case notes cannot resolve issues efficiently. Single desktop view or CRM integration is a prerequisite for high FCR.

Medium impact

Knowledge base gaps

An outdated or poorly structured knowledge base forces agents to guess or escalate. Keep it current; measure knowledge gap calls separately; treat knowledge failures as a process problem, not a performance problem.

Medium impact

Complex multi-step processes

Some issues genuinely cannot be resolved in one call (manual processing queue, third-party dependencies). Set customer expectations correctly and reduce the process cycle time: a 2-day process creates a repeat contact at day 2.

Medium impact

Inadequate ramp and training

New agents in ramp typically have FCR 10–20 percentage points below tenured agents. Track FCR by agent tenure. Accelerate knowledge transfer in the first 4 weeks of ramp, which is when the FCR gap is widest.

High impact

Transfers and escalations

Every transfer resets the contact for the customer and introduces a re-explanation overhead. Track transfer rate alongside FCR. Reduce transfers by expanding agent authority and providing knowledge support before transfer.

First call resolution questions

What is a good first call resolution rate?

FCR benchmarks: under 65% is poor; 65–75% is industry average; 75–80% is good; above 80% is excellent. The right target depends on your contact type: complex technical support typically achieves 55–65%, while simple transactional operations can achieve 85–90%. Operations using a 7-day repeat window tend to report lower FCR than those using same-day.

How is first call resolution measured?

Three methods: (1) Customer survey, asking 'Was your issue resolved?' immediately after the call. Fast but subject to response bias. (2) ACD/CRM contact matching, identifying repeat contacts from the same customer within 1 or 7 days. Objective but requires good customer identification. (3) Agent declaration, where the agent flags at close of call whether resolved. Fast but subject to gaming. Contact matching against CRM data is the most reliable method.

How does FCR affect staffing requirements?

Each 1% improvement in FCR reduces total contact volume by approximately 1–1.5%, depending on your current repeat contact rate. Improving FCR from 70% to 80% on a team with a 30% repeat rate removes approximately 10% of total volume, equivalent to roughly 10% fewer agents needed at the same SL and AHT. Use the FCR impact calculator to model your specific situation.

What is the most common cause of poor first call resolution?

The four most common root causes: (1) Agent authority gaps, where agents cannot resolve without escalating, which breaks the contact. (2) System access gaps, where agents cannot see account history or case notes. (3) Knowledge gaps, where agents do not know the answer. (4) Process complexity, where resolution requires actions that cannot complete in one call. Authority and access gaps are the most fixable and typically produce the fastest FCR improvements.