What Is First Contact Resolution (FCR)? How to Measure and Improve It

Few things frustrate a customer more than explaining the same problem twice. First contact resolution (FCR) measures how often you avoid that: the share of customer issues that are solved in the very first contact, with no reopening, follow-up or repeat message needed.

It's one of the few support numbers that tracks quality and cost at the same time. Customers get what they came for sooner, and your team handles one conversation instead of three.

What first contact resolution means

An issue is resolved on first contact when the customer gets a complete answer or fix during their first conversation with you, without having to write again about the same thing.

Two details matter in practice:

• A "contact" is one conversation. In live chat or Telegram, that's the conversation from the customer's first message until it's resolved.
• "The same issue" needs a time window. A customer who comes back three weeks later with a new problem isn't a failure. Most teams count a repeat within a fixed window (24 hours, 3 days or 7 days) as "not resolved on first contact".

The formula

FCR (%) = issues resolved on first contact ÷ all issues × 100

For example, if 500 customers contacted you this week and 380 of them never needed to come back about the same issue, your FCR is 380 ÷ 500 × 100 = 76%.

Before you start tracking, decide what counts as a miss and write it down:

Whatever rules you choose, keep them constant. A trend line only means something if the definition never changes.

What is a good FCR rate?

Industry surveys often quote about 70–75% as an average and 80% or more as excellent. Treat those numbers as orientation, not as targets:

• Simple, repetitive questions (order status, opening hours) should score much higher than complex ones (payment disputes, technical faults).
• Your own trend matters more than anyone else's benchmark. Compare this month with last month.
• Aiming for 100% is a mistake. Some issues legitimately need follow-up, and chasing the number pushes agents to close conversations too early.

How Hodhod measures FCR

Open Reports → KPIs and look for the card "FCR · first contact resolution". Its tooltip describes it as the share of resolved conversations that did not need to be reopened.

Behind the card, Hodhod compares two numbers for the period you select: how many conversations were resolved, and how many reopenings followed. A conversation is reopened when a customer writes again in a resolved conversation (Hodhod usually reopens it automatically) or when an agent reopens it.

Keep two things in mind when you read the number:

• It's an account-level estimate. It compares reopenings with resolutions in the same period; it doesn't trace each conversation individually.
• It doesn't see customers who start a brand-new conversation about the same problem, and a customer's "thanks!" in a resolved conversation also counts as a reopening. Use the number as a trend, and for repeat contacts open the customer's profile to see their conversation history.

Read it next to the other cards on the same page (resolved conversations and time to resolution) and next to customer satisfaction (CSAT) to see whether resolving faster and resolving right are going together.

8 ways to improve first contact resolution

1. Find out why issues come back

Look at reopened conversations and repeat contacts and ask what they have in common: the same product, the same shift, the same unclear answer? If you label conversations by topic, Reports → Labels shows which topics generate the most contacts.

2. Ask for what you need before the conversation starts

Many follow-ups happen because the agent lacked something: an order number, an email, a screenshot. Collect it up front with a pre-chat form or an input step in a chatbot flow, validated so that a typo doesn't send everyone back and forth.

3. Give agents authority and clear rules

If every refund or exception needs approval, the first contact can't finish the job. Write down what agents may decide alone (refund limits, replacements, goodwill gestures) and what needs escalation.

4. Make answers complete

A good answer includes every step, a link and what to expect next. Canned responses written once and reviewed by your best agent keep that quality consistent across the team.

5. Confirm before you resolve

Ask "Does that solve it?" and resolve the conversation once the customer says yes, or after a clear waiting period. Resolving too early is the most common reason a conversation comes back.

6. Hand over with context

When an issue does need another person, add a private note, label the conversation and assign it to the right agent or team, so the customer never has to repeat themselves. For requests that really need days, turn the conversation into a ticket with a priority and a deadline, and tell the customer what happens next.

7. Fix the cause, not just the symptom

If one topic generates a large share of your contacts, the best fix may be on your website, in your product or in your FAQ. Update your chatbot's answers when you do.

8. Review reopened conversations every week

Fifteen minutes with a handful of reopened conversations tells you more than any report. Look for patterns, share the best replies and make one change per week. The weekly review in 10 customer support KPIs is a good place to add this.

Common mistakes

• Closing conversations quickly to lift the number. If FCR rises while CSAT falls, customers aren't being helped.
• Measuring without a time window. "The same issue" needs a clear definition.
• Comparing channels or products as if they were the same. Compare like with like.
• Looking at FCR alone. Read it together with CSAT and resolution time.

Want to see these reports on your own conversations? Request a free demo.

Frequently asked questions