Why FCR is the metric under the metrics

First Contact Resolution — the share of tickets resolved in a single interaction, with no back-and-forth and no reopen — is the closest thing support has to a master metric. A high FCR pulls three other numbers in the right direction at once: cost drops (fewer touches per ticket), CSAT rises (customers hate repeating themselves), and customer effort falls. When FCR moves, almost everything else follows.

The catch is that it's easy to measure dishonestly. Close a ticket fast and badly and your FCR looks great — until the customer reopens it two days later, furious. So measure FCR net of reopens: a ticket only counts as first-contact-resolved if it stays closed.

Realistic benchmarks

There is no universal "good" FCR number, because it depends entirely on your ticket mix. A team fielding mostly password resets will run far higher than one fielding deep technical integrations. Rough ranges that hold up across B2B SaaS support:

  • Below 50%: something is structurally wrong — usually missing agent knowledge, no knowledge base to lean on, or aggressive escalation.
  • 60–70%: typical for a healthy team with a mixed ticket load. A reasonable target for most.
  • 75%+: strong, and usually the sign of a mature KB plus agents empowered to actually resolve rather than route.
  • Above 85%: either genuinely excellent — or you're measuring it loosely. Audit your reopen rate before you celebrate.

Don't chase a number you read in a vendor's marketing deck. Measure your own FCR for a month, segment it by ticket type, and set your target one tier up from where you actually are.

Segment before you act

A blended FCR number hides everything actionable. Break it down by ticket type and the picture sharpens immediately: your "how do I export my data" tickets might resolve first-contact 95% of the time while your "billing dispute" tickets sit at 30%. Those are two completely different problems, and the blended average tells you to fix neither.

This is exactly the kind of analysis that pays off when you track the metrics that matter instead of drowning in a dashboard. FCR by ticket type is one of the few cuts that consistently changes a decision.

The tactics that actually move FCR

Put knowledge in front of the agent, mid-ticket. The single biggest FCR killer is an agent who has to go find an answer. Surface the relevant KB article on the ticket itself. An AI assist that suggests the matching article — or drafts a first reply grounded in your real KB — closes the knowledge gap that forces a second touch.

Empower agents to resolve. FCR collapses when front-line agents can't issue a refund, extend a trial, or reset a config without a manager's approval. Every "let me check with my team" is a guaranteed second contact. Push authority down to where the ticket lands.

Collect the right information up front. Half of all second contacts are just the agent asking for the detail the customer should have provided initially. A service catalog that captures the right custom fields per request type — account ID, environment, error message — means the agent has what they need on the first read.

Use AI triage to route it right the first time. A misrouted ticket is a multi-touch ticket by definition. Auto-classifying type, priority, and team on creation gets the ticket to someone who can actually resolve it, instead of bouncing it through a handoff.

Resolve the question behind the question. The highest-leverage FCR habit is answering what the customer will ask next, not just what they did ask. "Here's how to reset your API key — and here's how to rotate it on a schedule so this doesn't recur." One thoughtful reply beats three terse ones.

Watch the failure mode

The danger with any FCR push is that you incentivize agents to close rather than resolve. Always pair FCR with two guardrails: the reopen rate (closing badly shows up here) and CSAT (rushing shows up here). An FCR number rising while reopens climb isn't progress — it's the metric being gamed. Read all three together, or don't trust any of them.