A customer reports a bug. Your agent asks for more details. The customer replies the next day. The agent tries to reproduce it, fails, and asks for a screenshot. The customer sends one two days later. The agent finally identifies the issue and provides a workaround. Total resolution: 4 contacts over 5 days.

If the agent had asked for the details and screenshot upfront, this could have been 1 contact in 1 day. Every additional contact cost the company $5 to $12 in agent time and cost the customer patience they'll remember next renewal.

First Contact Resolution (FCR) measures how often you resolve issues on the first try. It's one of the most important support metrics because it directly correlates with customer satisfaction, cost, and loyalty.

What FCR Means

FCR = tickets resolved in a single contact / total tickets resolved.

A "contact" varies by channel. For phone, it's one call. For email, it's one email exchange (customer sends, agent resolves). For chat, it's one chat session.

The measurement sounds simple. In practice, it's tricky because of edge cases. If the customer reopens the ticket two weeks later with a new issue, does the original ticket still count as FCR? (Yes, it should.) If the agent says "resolved" but the customer comes back in 24 hours about the same issue? (No, that's not FCR.)

Most teams use a "reopened within 72 hours" rule: if a ticket is marked resolved and the customer contacts again about the same issue within 72 hours, the original resolution doesn't count as FCR.

Benchmarks by Industry

These numbers come from industry surveys and benchmarks (SQM Group, MetricNet, HDI). They represent averages. Top-performing teams in each industry are 5 to 10 points higher.

SaaS / Software: 65 to 75%. Software issues are complex. Many require reproduction, debugging, or engineering involvement. Multi-contact resolution is common for technical bugs.

E-commerce: 70 to 80%. Most e-commerce queries are transactional (order status, returns, refunds) and can be resolved in one contact with the right tools. Product questions and shipping issues are usually straightforward.

Telecom: 55 to 65%. Telecom has complex billing, technical issues that require field technicians, and legacy systems that make information hard to find. FCR is notoriously low in this industry.

Financial Services: 60 to 70%. Compliance requirements, security verification, and complex account structures make first-contact resolution harder. Simple balance inquiries score 90%+, but complex disputes bring the average down.

Healthcare: 60 to 70%. Similar to financial services. Simple scheduling questions resolve easily, but insurance, billing, and clinical questions require multiple touches.

Hospitality / Travel: 65 to 75%. Booking changes and cancellations are usually straightforward. But complex itinerary changes, compensation for service failures, and loyalty program issues require back-and-forth.

If you're below the low end of your industry benchmark, there's room for improvement. If you're above the high end, you're doing something right.

Why FCR Matters Financially

Each follow-up contact costs money. Agent time is the obvious cost: $5 to $12 per additional contact depending on agent salary and handle time.

But the hidden cost is bigger. Customer satisfaction drops 15% with each additional contact required to resolve an issue (SQM Group data). By the third contact, satisfaction has fallen by nearly half compared to first-contact resolution.

Low FCR also drives up total ticket volume. If 500 tickets per month require an average of 1.5 contacts (instead of 1.0), that's 250 additional contacts. At $8 per contact, that's $2,000/month in unnecessary cost. Over a year: $24,000.

Improving FCR from 65% to 80% on 500 monthly tickets saves roughly 100 follow-up contacts per month. That's $800/month or about $10,000/year. Plus happier customers.

How to Improve FCR

The most effective FCR improvement doesn't require new tools or technology. It requires asking better questions upfront.

Gather all needed information in the first contact. If resolving a billing issue requires the customer's account email, transaction date, and amount, ask for all three in the first response. Don't ask for the email, wait for a reply, then ask for the transaction date.

Supp's AI classification helps here. When the system classifies a message as "billing dispute," it can prompt the agent with "gather: account email, transaction ID, dispute amount." The agent asks for everything upfront instead of piece by piece.

Give agents authority to resolve without escalation. If 20% of tickets get escalated because the agent doesn't have authority to issue a refund over $50, raise the limit to $100. Each avoided escalation is a potential FCR save.

Build runbook entries that include resolution steps, not just classification. An agent who knows how to resolve a billing discrepancy (not just identify it) resolves it in one contact.

Pre-populate information. If the customer contacts through your app or widget, the system already knows their account, recent orders, and subscription status. Don't ask them for information you already have.

FCR for AI-Handled Tickets

AI has a natural FCR advantage for the tickets it handles well. If the classification is correct and the automated response resolves the issue, FCR is 100% on that ticket. There's no follow-up, no back-and-forth, no information gathering.

AI FCR rates for simple intents (password reset, order status, business hours) typically run 85 to 95%. For medium-complexity intents (billing questions, feature guidance), 60 to 75%.

When AI can't resolve on first contact, the quality of the handoff matters. If AI gathers the right context before handing off to a human, the human has a better chance of resolving in their first response. AI as an information-gathering layer improves overall FCR even for tickets that need human resolution.

Track AI FCR separately from human FCR. If your AI FCR drops below 80% on intents it's supposed to handle, either the classification is wrong or the automated response doesn't actually resolve the issue. Both are fixable.