The One Metric That Predicts Everything Else

First contact resolution (FCR) measures whether a customer's issue was resolved in their first interaction with support. No follow-ups. No "let me get back to you." No "can you try this and let me know?"

One question. One answer. Done.

FCR is the strongest predictor of customer satisfaction in support. A customer whose problem is solved on first contact rates their experience 25-30% higher than one who needs multiple interactions — even if the total resolution time is the same.

How to Calculate It

FCR Rate = (Tickets resolved in one interaction / Total tickets) × 100

"One interaction" means the customer contacted you once and didn't need to follow up. If they emailed, got a response, and never emailed about that issue again — that's first contact resolution.

If they emailed, got a response, then emailed again saying "that didn't work" — that's NOT first contact resolution.

What's a Good FCR Rate?

• Industry average: 70-75%
• Good: 75-80%
• Great: 80-85%
• Exceptional: 85%+

If your FCR is below 65%, something is broken. Either your responses aren't solving problems, your team lacks the authority/tools to resolve issues, or your product has systemic issues that require back-and-forth to diagnose.

Why FCR Matters More Than Response Time

Response time gets all the attention. "We respond in under 5 minutes!" Great. But if the customer has to come back three times to get their issue resolved, fast responses don't matter.

Customers would rather wait 30 minutes for a response that solves their problem than get an instant response that says "let me look into this" followed by 2 days of back-and-forth.

This doesn't mean response time doesn't matter — it does. But FCR matters more. Optimize for resolution quality first, then speed.

What Kills FCR

1. Lack of authority. If your support team can't process refunds, change plans, or access account data without escalating, FCR drops. Every escalation is a failed first contact.

Fix: give your support team (or your automation rules) the authority to resolve the top 80% of issues without approval.

2. Bad auto-responses. An auto-response that sends a link to your FAQ instead of answering the question directly fails FCR. The customer has to click, search, read, and maybe still not find their answer.

Fix: auto-responses should answer the question directly, not redirect to another page. Link to docs as supplementary information, not as the primary answer.

3. "Let me check on that." Responses that promise to follow up instead of resolving immediately. Sometimes unavoidable for complex issues, but it should be the exception, not the default.

Fix: equip agents with the tools and information to resolve during the conversation. Customer data, order history, and account details should be visible alongside the ticket.

4. Multi-step troubleshooting. "Try clearing your cache. Did that work? OK, try a different browser. Did that work? OK, let me escalate." Each step is another interaction.

Fix: bundle troubleshooting steps into one response: "Try these in order: 1) clear your cache, 2) try a different browser, 3) try incognito mode. If none of these work, reply and I'll escalate to engineering with your browser details."

How Automation Improves FCR

Automated responses have an unfair advantage for FCR: they answer the question completely in one shot. There's no "let me check" or "I'll get back to you." The auto-response either solves the problem or escalates to someone who can.

Password reset? Send the reset link. Done. FCR. Order tracking? Send the tracking number. Done. FCR. Pricing question? Send the pricing details. Done. FCR.

Auto-resolved messages have near-100% FCR because the system either resolves it or escalates it — it never sends a half-answer.

For a team with 60% automation and 75% FCR on human-handled tickets, the blended FCR rate is:

• 60% auto-resolved × 98% FCR = 58.8%
• 40% human-handled × 75% FCR = 30%
• Blended FCR: 88.8%

Automation doesn't just save time. It directly improves your most important quality metric.

Tracking FCR

Simple method: A ticket is "first contact resolved" if the customer doesn't contact you about the same issue within 7 days. Track this in a spreadsheet or your support tool's reporting.

Better method: After resolution, ask the customer: "Was your issue fully resolved? Yes/No." If they say yes and don't follow up, it's FCR. If they say no or follow up, it's not.

With automation: Auto-resolved messages can include a "Did this answer your question?" thumbs up/down. Thumbs up = FCR. Thumbs down = escalate to human (and mark as non-FCR).

Review your FCR weekly. If it's dropping, find out which ticket types are causing repeat contacts and fix the root cause — either better auto-responses, better agent training, or product fixes.