What Is First Contact Resolution? Formula, Benchmarks, and the Definition Problem

Key Takeaways

• The first contact resolution formula is tickets resolved on the first contact divided by total tickets, times 100. The same month of work scores differently under a 72-hour callback window than a 14-day one.
• The 70 to 79 percent industry standard comes from SQM Group, a call center company measuring customer calls by post-call survey. SQM's own data puts tech support and telcos at the bottom of the range.
• Email and web tickets have a separate standard almost nobody cites. MetricNet counts resolution within one business hour of receiving the ticket.
• A high FCR rate can be manufactured three ways. Tracking first contact resolution rate without reopen rate and repeat-contact rate beside it produces a number that improves while the experience does not.
• Helply is $1 per ticket with unlimited seats and unlimited AI. Every repeat contact is a second ticket, making FCR the one support metric that shows up on the invoice.

First contact resolution (FCR) is the percentage of support requests resolved in a single interaction, with no follow-up contact from the customer. It is calculated by dividing tickets resolved on the first contact by total tickets, then multiplying by 100.

The metric is also written as first-contact resolution and abbreviated FCR. It is closely related to first call resolution, which measures the same idea on a single phone call. SQM Group's 2025 research puts the average FCR rate across industries at 70 percent, from post-call surveys of North American call centers.

SQM adds that industries with high call complexity post the lowest FCR rates, naming tech support and telcos specifically. Low-complexity industries such as retail sit at the top of the range.

FCR measures outcomes rather than speed. First response time records how fast someone replied, while FCR records whether that reply ended the problem. A team can answer in four minutes and resolve nothing.

Three variables decide the number, and someone at your company chooses all three:

• What counts as one contact. A phone call ends. An email thread and a Slack conversation do not.
• What counts as resolved. The agent's judgment, or the customer's confirmation.
• How long the callback window runs. If the customer returns inside it, the original ticket loses its FCR credit.

Change any one of them and you report a different number for identical work.

The First Contact Resolution Formula

The first contact resolution formula is simple:

FCR = (issues resolved on the first contact ÷ total contacts) × 100

Take 1,000 tickets in a month. If 680 of them were resolved on the first contact, the FCR rate is 68 percent.

Teams go wrong on the inputs, not the arithmetic. Below is that same month scored three ways, changing nothing except the rules:

Same month, same team. A ten-point spread, produced by rules someone chose. Two companies quoting FCR rates at each other are comparing different things.

SQM Group says as much in its own guide. Internal FCR measurement turns on whether the customer calls back about the same issue within 1 to 30 days:

"However, choosing the appropriate call-back time can be difficult, and as a result, there is no standard for internal FCR measurement, making the FCR rate less accurate."

SQM sells the benchmark and says there is no standard behind the internal method.

First Call Resolution vs First Contact Resolution

First call resolution means the issue was fixed during the first customer call. First contact resolution means it was fixed the first time the customer reached out, on any channel: email, chat, Slack, portal, or phone.

Both get abbreviated to FCR, which is how benchmarks for one end up applied to the other. A rate built on phone calls gets read as a rate for every channel.

Work that arrives and ends inside one phone conversation is a different shape from a bug report needing reproduction steps. Benchmarks built on the first kind do not transfer to the second.

How Do You Measure FCR on Email, Chat, and Slack?

A customer call has a moment it ends. An email does not.

Most B2B teams give up on measuring first contact resolution at this point. The gap has a real answer.

MetricNet, the service desk benchmarking firm, publishes the standard. Jeff Rumburg, MetricNet's co-founder and managing partner, writes in his guidance on the FCR rate:

"For emails and web submitted tickets, which now account for a significant percentage of all service desk contacts, the de facto standard emerging in the industry is that resolution within one business hour of receiving a customer email or web ticket counts as FCR."

One business hour. It approximates the phone standard: resolved before the customer disengages and goes to do something else.

That gives each asynchronous channel a boundary. Channel by channel:

Slack Connect is the hard case. A thread with four exchanges over eight hours is one contact or five, depending on a rule someone has to write. Cap it at one business day and you measure resolution instead of thread etiquette.

Someone still has to mark the ticket. Rumburg names two FCR measurement methods, the first being an agent checkbox at close. The other common method is a post-contact survey sent to the customer.

These do not agree. Wikipedia's article on first call resolution puts the gap at 10 to 20 percent. Internal marking runs that much higher than external survey data.

The practical middle is agent-marked, audited quarterly against reopen data. Cheap to run, and the audit catches the drift.

FCR vs First Response Time: What Is the Difference?

First response time measures how long a customer waits for any reply. First contact resolution measures whether that reply ended the problem. They move independently, and improving one can hide a failure in the other.

A team can cut first response time to eleven minutes with canned openers and still send the customer back into the queue twice. That looks like a fast support team on a dashboard and feels like a slow one to the account. Read the pair together: fast first response with low FCR means the team is acknowledging quickly and resolving slowly.

What Is a Good First Contact Resolution Rate?

SQM Group's first call resolution guide, updated November 2025, reports these benchmarks:

• 70 percent is the aggregated average across all industries.
• 70 to 79 percent is the industry standard for a good FCR rate.
• 80 percent or higher is what SQM calls "world-class," reached by roughly 5 percent of call centers.
• 50 to 90 percent is the full range across industry call center benchmarks.

SQM is a call center company that sells benchmarking and QA software. Those figures come from post-call surveys of North American call centers, so the unit of measurement is a customer call.

SQM splits the same picture by call complexity. Industries with low call complexity, such as retail and not-for-profit, post the highest FCR rates. Tech support and telcos post the lowest.

Published ranges vary by source. SQM's guide gives 50 to 90 percent, while Verint reads the same underlying data as 39 to 91 percent.

That complexity line is the one a B2B software team should hold on to. A retail queue at 78 percent and a tech support queue at 78 percent did not do the same work.

So set the target from your own baseline. Measure for one quarter and segment by ticket type. Then aim above your own median rather than importing an average from different work.

Treat a high number with suspicion. Reported rates of 90 to 95 percent point to a measurement problem rather than excellence.

Every published figure, with its measurement method attached:

Want the same treatment for the metric next door? Our breakdown of deflection rate and what it hides runs the same audit on self-service numbers.

Why B2B Support Runs a Lower FCR, and Why That Is Correct

SQM's own finding points here: high call complexity produces the lowest FCR rates, and it names tech support directly. B2B support is a different problem. Volume is lower, stakes are higher, and the customer often knows the product better than a new hire does.

That shows up in the FCR rate. B2B tickets stall for structural reasons:

• Reproduction steps have to come back from the customer before anyone can diagnose anything.
• A confirmed bug cannot close until the fix ships.
• The decision sits with Product, Finance, or the AE who owns the commercial relationship.
• The answer depends on what that specific account's contract says.

None of those are support failures. Counting them as failures punishes the team for the engineering backlog, and everyone stops trusting the number.

The fix is an exclusion list. Four categories leave the denominator: confirmed bugs pending a release, feature requests, tickets pending customer reply, and customer-requested follow-ups.

Log them separately. You keep the volume visible without dragging the rate.

How FCR Gets Gamed

Any metric attached to performance reviews gets managed. First contact resolution has three well-worn routes, and support leads describe all of them openly:

• Ticket splitting. One job gets logged as four tickets, and each one closes on the first contact. On r/sysadmin, the standard warning about time-based metrics is that everyone opens a new ticket at each step of the job.
• Premature resolve. The agent marks it resolved after sending a workaround, before the customer has confirmed anything.
• Discouraging the follow-up. The cheapest way to protect an FCR rate is to make coming back feel like a hassle.

There is a fourth problem that is structural rather than individual. Targeting FCR and average handle time together forces agents to choose which one to miss. A 5-minute handle time target and an 85 percent FCR target are incompatible instructions.

Read handle time next to FCR, never alone. Our guide to cutting average handle time without hurting quality covers that trade-off in detail.

The defense is two guardrail metrics reported on the same dashboard:

• Reopen rate. Tickets reopened after being marked resolved. Above 8 percent, the resolve button is being pressed too early.
• Repeat-contact rate. Accounts contacting again inside the callback window about a related issue. Above 15 percent, first contacts are not ending problems.

FCR rising while reopen rate rises is a measurement artifact, not an improvement. That single pairing catches almost every version of a manufactured number.

How to Improve First Contact Resolution

Improving FCR means removing the reasons a first reply fails. Five levers do most of the work.

1. Put account context in front of the agent before the first reply. ARR, renewal date, plan limits, recent product usage, open Linear issues, Stripe billing state. Most second contacts happen because the first reply was written without them.

Loading that context automatically is the single biggest change available.

That is the job Helply was built for. It is a support platform for B2B software teams, and every ticket opens with the account already loaded. ARR, renewal date, plan limits, Stripe billing state, and open Linear issues, all on screen before anyone types.

The agent stops asking questions the company can already answer. That is where most first contacts are won or lost.

2. Close the knowledge gaps your tickets keep pointing at. This is the best-evidenced lever there is. The Consortium for Service Innovation maintains the Knowledge-Centered Service methodology.

It reports that KCS adopters see a 30 to 50 percent increase in FCR. Members also report 50 to 60 percent improved time to resolution and 70 percent improved time to proficiency.

3. Route to the person who can decide, not the person who is free. Tiered queues add a handoff before the ticket reaches anyone with authority. Every handoff is a lost first contact.

Our comparison of swarming and tiered support models covers when to switch.

4. Kill the pending-on-customer dead zone. Tickets that sit after a request for information are the quietest drag on both FCR and CSAT. Set an automatic nudge at 48 hours and a close at seven days. Support ops sees the real backlog again.

5. Feed root causes back to Product. Ten identical tickets are one bug. KCS members report a 10 percent reduction in total issues from removing root causes.

It is the only improvement that lowers contact volume instead of moving it around. Our post on reducing incoming support tickets covers the loop.

Your One-Page FCR Measurement Policy

Copy this, change the numbers to match your queue, and put it where the dashboard lives.

1. Definition. A contact is one inbound request plus every reply exchanged within the channel window below. It counts as resolved on the first contact when the original request is answered inside that window. No related contact may arrive before the callback window closes.

2. Callback window: 7 days. Long enough to catch a genuine recurrence, short enough that a new issue does not score against the original ticket. Seven days also matches most B2B working rhythms. A customer hits the same problem in next week's work, not the next hour's.

3. Channel windows.

• Email, web ticket, and portal: one business hour.
• Live chat and in-app: the session.
• Slack Connect and Teams: one business day.
• Phone: the call.

4. Exclusions. Five categories leave the denominator and get logged separately. Confirmed bugs awaiting a release, feature requests, and tickets pending customer reply. Customer-requested scheduled follow-ups, and tickets needing approval from outside support.

5. Who marks it. The assigned agent marks resolution status at close. Support ops audits a 50-ticket sample each quarter against reopen data. Where the two differ by more than 5 points, the audited number is reported.

6. Guardrails, reported together. FCR rate, reopen rate (target under 8 percent), and repeat-contact rate inside the callback window (target under 15 percent). No FCR figure is circulated without both.

7. Review cadence. Quarterly. If anyone changes a rule here, reset the trendline and note the change on the dashboard. A definition change is not a performance change.

Numbers compared across two different definitions are not a trend.

How Helply Resolves More Tickets on the First Contact

Three of the five levers above are platform problems, not training problems. Helply is a support platform for B2B software teams, built to close those three.

Account context loads on every ticket automatically, so the first reply gets written with ARR, renewal proximity, and Stripe billing state on screen. The AI assistant drafts each reply with sources and that context attached, which is where first contacts get resolved. The knowledge base writes articles from recurring ticket patterns and flags the gaps, closing lever two without a documentation project.

Support Intelligence handles the measurement side. A support lead types a question about their own resolution data and gets an answer, so auditing FCR against reopen data takes minutes.

The pricing works the same way. Helply costs $1 per ticket. That single price covers unlimited seats, unlimited agents, and every AI capability.

The floor is 250 tickets a month on a $3,000 minimum annual contract. There are no per-seat fees and no per-outcome charges. Any older per-resolution or per-draft pricing for Helply retired in July 2026.

For contrast, Zendesk Suite Professional is $115 per agent per month billed yearly. Billing follows tickets instead of headcount, so cutting repeat contacts lowers what a B2B team pays.

The Bottom Line

First contact resolution is worth measuring and only worth reporting next to its definition, its window, and its two guardrails. The team that writes the policy down gets a number that still means something in six months. The team that skips it gets a number that moves whenever someone changes a rule.

That gets harder from here, not easier. More first contacts are handled by AI every quarter. What counts as one contact, and who resolved it, now needs a written answer.

No policy closes the last gap. A team can define FCR to the letter and still lose the first contact, because the agent replied without knowing the account.

Helply closes that gap. Every ticket opens with ARR, renewal date, Stripe billing state, and product usage already loaded. The AI drafts the first reply from it.

One price covers all of it: $1 per ticket, unlimited seats, unlimited AI.

On a seat-based help desk, a repeat contact costs the vendor nothing and costs the team again in agent hours.

On Helply, every repeat contact is a second ticket. A problem solved on the first contact is a problem you never pay for twice.