Customer Support & Experience

First Contact Resolution

Definition

First Contact Resolution (FCR) is one of the most important metrics in customer support, measuring the ability of a support team to fully resolve a customer's issue in a single interaction — without the customer needing to call back, reply again, or be transferred multiple times. FCR is calculated as: (Tickets resolved on first contact) / (Total tickets) x 100. An average FCR rate is 65-75% for phone support and somewhat higher for chat. Low FCR drives customer frustration (having to repeat themselves) and inflates support costs (multiple contacts per issue multiply handling time). High FCR correlates strongly with high CSAT.

Why It Matters

FCR is considered the golden metric of support efficiency because it simultaneously measures customer experience quality and operational efficiency. Each unresolved first contact generates at least one more contact (a repeat), effectively doubling the cost of that issue. More importantly, customers who have to contact support multiple times for the same issue are significantly less satisfied and more likely to churn. For AI chatbot deployments, FCR is a key metric for evaluating AI effectiveness — an AI chatbot that consistently requires customers to escalate to humans has low effective FCR.

How It Works

FCR is measured by tracking whether a customer submits a new ticket or contacts support again within a defined time window (typically 24-72 hours) about the same issue. Help desk systems can automatically flag contacts as repeat interactions when they come from the same customer with the same issue category. FCR improvement initiatives focus on: root cause analysis of common multi-touch issues, agent training and empowerment (giving agents the authority to resolve more issues), better knowledge tools (agents can find answers faster), and AI assistance (surfacing relevant solutions during customer interactions).

First Contact Resolution — Measurement and Drivers

FCR Formula

Total tickets this week

200

Resolved on first contact

156

156 / 200 × 100

= 78% FCR

Key Drivers

Agent trainingHigh
KB accessHigh
Clear escalation pathsMedium
Agent empowermentMedium

FCR by Channel

Chat
82%
Phone
76%
Email
71%

Industry benchmark FCR: 70 – 75%

Each 1% FCR improvement reduces repeat contact volume significantly.

Real-World Example

A 99helpers customer measures FCR and finds it is 52% — far below the industry benchmark of 70%. Analysis shows that 30% of unresolved first contacts fail because agents lack the authority to issue refunds above a certain threshold, requiring manager approval that delays resolution. By raising the agent refund authority limit and training agents on the updated policy, FCR improves to 71% within 30 days, reducing monthly repeat contact volume by hundreds of tickets.

Common Mistakes

  • Measuring FCR based on ticket closure rather than customer confirmation — tickets marked 'resolved' by agents often require further follow-up from the customer's perspective
  • Optimizing FCR in isolation — pushing agents to close tickets quickly without actually resolving the issue inflates FCR numbers while damaging CSAT
  • Not segmenting FCR by issue type — FCR for simple password resets should be near 100%; FCR for complex technical issues may legitimately be lower

Related Terms

Ready to build your AI chatbot?

Put these concepts into practice with 99helpers — no code required.

Start free trial →
What is First Contact Resolution? First Contact Resolution Definition & Guide | 99helpers | 99helpers.com