First Contact Resolution: Why It Matters More Than You Think
First contact resolution (FCR) is the percentage of tickets resolved in a single interaction—no follow-ups, no reopens, no escalations. It’s simple, but it’s one of the best predictors of customer satisfaction.
Why FCR matters
- Customer satisfaction — Customers don’t want to follow up. FCR directly correlates with higher CSAT.
- Efficiency — Each additional touch costs time. FCR reduces touches per ticket.
- Cost — Lower touches = lower cost per resolution. See cost per ticket.
- Agent experience — Resolving issues on first contact is more satisfying than endless back-and-forth.
Research consistently shows FCR is the #1 driver of customer effort score and loyalty.
How to measure FCR
There’s no universal definition, but common approaches:
Definition 1: Single reply
Ticket resolved with one agent reply (excluding auto-reply). Simple to measure, but strict—some issues legitimately need clarification.
Definition 2: No follow-up within X days
Ticket marked solved and no customer reply within 3–7 days. Accounts for customer verification time.
Definition 3: Customer survey
Ask “Was your issue resolved in a single contact?” after the ticket closes. Most accurate, but requires survey participation.
For the formal definition, see first contact resolution in the glossary.
What’s a good FCR rate?
Benchmarks vary by industry:
| Industry | Typical FCR |
|---|---|
| Software/SaaS | 60–75% |
| E-commerce | 70–85% |
| Telecoms | 50–65% |
Don’t chase industry benchmarks blindly—track your own FCR over time and improve from your baseline.
What drives FCR
| Driver | Impact |
|---|---|
| Knowledge base quality | Agents find answers faster |
| Agent training | Skilled agents resolve more on first touch |
| Empowerment | Agents can act (refund, credit) without escalation |
| Clear processes | Known issues have known solutions |
| Good tooling | Quick access to customer context |
What kills FCR
| Issue | Fix |
|---|---|
| Missing knowledge | Document common issues |
| Complex escalation | Simplify; empower tier 1 |
| Incomplete customer info | Better intake forms |
| Product bugs | Fix the root cause |
FCR vs speed
Don’t sacrifice FCR for speed. A fast first reply that doesn’t resolve the issue leads to:
- Customer follow-up
- More agent time
- Lower satisfaction
Speed matters, but resolution matters more. Balance first reply time with FCR.
How to improve FCR
- Track it — You can’t improve what you don’t measure.
- Identify low-FCR tags — Which issue types rarely resolve on first contact?
- Root cause — Why? Knowledge gap? Policy blocker? Product issue?
- Fix one thing — Improve docs for the #1 low-FCR tag; train agents; change policy.
- Repeat — Pick the next low-FCR tag.
FCR in your dashboard
Add FCR to your support team scorecard:
| Metric | This week | Target |
|---|---|---|
| FCR | 68% | > 70% |
Track by agent and by tag to find improvement opportunities.
FAQ
Is FCR more important than FRT?
They’re both important. A fast reply that doesn’t resolve is a waste. A slow reply that resolves is better, but still frustrating. Optimize both.
Does FCR account for reopens?
Depends on your definition. If you measure “no follow-up within X days,” reopens disqualify the ticket from FCR.
Should I track FCR by agent?
Yes—but use it for coaching, not punishment. Some agents handle harder tickets.