What is First contact resolution?
First contact resolution measures the share of customer issues resolved during the first interaction across any supported channel, without repeat contact.
- Aliases
- First contact resolution technology, first call resolution
Why is first contact resolution important across support channels?
First contact resolution measures whether the customer’s issue is solved without another interaction, regardless of whether the first contact began in voice, chat, email, or messaging.
- Reduces repeated explanations across channels.
- Signals effective knowledge, routing, and ownership.
- Lowers total service workload per issue.
- Reflects customer effort more broadly than phone-only resolution.
How First contact resolution works
- Define which contacts and channels are eligible for the calculation.
- Mark a contact resolved only when the customer’s underlying issue is completed, not merely when the interaction closes.
- Look for repeat contacts, reopened tickets, transfers, or unresolved dependencies during a fixed window.
- Report customer-confirmed and operationally inferred resolution separately when both are available.
First contact resolution in action
A customer calls to correct an invoice. The agent updates the charge and closes the call, but the account is not actually credited until a back-office task finishes. The interaction counts as first-contact resolution only if the task completes and the customer does not need to return within the defined window.
How First contact resolution is measured or evaluated
Use a stable formula and representative production data. Track the following measures together:
- first contact resolution: eligible issues resolved on the first contact divided by eligible issues
- repeat-contact rate within the measurement window
- reopen and transfer rate
- customer-confirmed resolution score
- resolution by intent, channel, and ownership team
Limitations, risks, and common failure modes
- Closing a ticket is not proof that the issue was resolved.
- Short follow-up windows inflate the rate for problems that recur later.
- Excluding complex contacts can make performance look artificially strong.
- Pressure to improve FCR can discourage appropriate follow-up or specialist escalation.
FCR depends on a defensible definition of issue identity, resolution, and time window. Publish those rules with the metric.
First contact resolution vs. first call resolution
First contact resolution covers the first interaction across channels. First call resolution is the voice-specific version and should use the same underlying resolution logic.
What teams should consider when using or implementing First contact resolution
- Create intent-specific resolution criteria and evidence.
- Deduplicate related contacts across phone, chat, email, and tickets.
- Choose follow-up windows that match the lifecycle of each issue.
- Audit samples against customer outcomes and back-office completion.
- Do not reward agents for avoiding necessary follow-up.
Sources
Related terms
- Average wait timeUnderstand Average wait time and its role in better customer experience. See how teams measure it, interpret results, and improve performance.
- Call deflectionUnderstand Call deflection and its role in lower live-agent demand. See how teams measure it, interpret results, and improve performance.
- Cost per resolutionUnderstand Cost per resolution and its role in service economics. See how teams measure it, interpret results, and improve performance.
- Escalation rateUnderstand Escalation rate and its role in automation gap detection. See how teams measure it, interpret results, and improve performance.
- Speech analyticsUnderstand Speech analytics and its role in better call outcomes. See how teams measure it, interpret results, and improve performance.
- Average speed of answerUnderstand Average speed of answer and its role in queue responsiveness. See how teams measure it, interpret results, and improve performance.
