What is First Contact Resolution?

Converge Converge Team

Resolving a customer's issue in a single interaction without follow-up

What is First Contact Resolution?

First contact resolution (FCR) is the percentage of customer issues resolved in a single interaction without requiring a follow-up conversation, escalation, or callback. If a customer messages about a billing question and the agent resolves it completely in that same conversation, that counts as FCR. If the customer needs to reach out again about the same issue, it doesn't.

Measuring FCR accurately requires defining what "resolved" means for your team. Some teams count a conversation as resolved when the agent closes the ticket; others wait a set period (24-48 hours) to confirm the customer doesn't reopen or reach out again about the same issue.

Why First Contact Resolution Matters

SQM Group research found that every 1% improvement in FCR corresponds to a 1% improvement in CSAT. Customers strongly prefer getting their issue solved once rather than going back and forth. FCR above 80% is considered world-class; the industry average sits around 70-75%.

Low FCR is expensive. Each follow-up interaction costs the same as a new conversation but generates no additional value. A team with 60% FCR is effectively handling 40% more volume than necessary. Improving FCR from 60% to 80% reduces your effective workload by 25%.

First Contact Resolution in Practice

A support team analyzed their reopened tickets and found that 30% of non-FCR cases were caused by agents giving partial answers—they answered the stated question but missed the underlying problem. By training agents to ask "Is there anything else I can help with?" and to proactively address related issues (e.g., a shipping delay question often leads to a refund request), their FCR improved from 68% to 82% within 6 weeks.

Related Terms

Related Reading

Frequently Asked Questions

Industry average is 70-75%. Aim for 80%+ for standard support queries. Note that some issues legitimately can't be resolved in one interaction (bug fixes, feature requests, shipping delays), so 100% FCR isn't realistic. Track FCR by issue category to set appropriate targets.
Track tickets that are reopened or followed up within 24-48 hours of closure. Some teams also survey customers asking 'Was your issue fully resolved?' after closing. Avoid counting auto-closed tickets as resolved—only count issues the customer confirms are done.
Agent knowledge gaps (they don't know the answer and need to escalate), insufficient system access (they can't process refunds or make account changes), and partial answers (answering the surface question without addressing the root cause). Each requires a different fix.