Solved in one touch — the completeness metric that speed metrics can’t fake.
First contact resolution. First contact resolution (FCR) is the percentage of support issues fully resolved in the customer’s first contact, with no follow-up message, transfer or repeat conversation needed. First contact resolution measures completeness where response-time metrics measure pace: a team can reply quickly and still fail FCR by replying incompletely.
The whole metric hinges on how you define “resolved on first contact,” and there is no single standard. Most teams count a failure when the conversation is reopened, or when the same customer starts a new conversation about the same issue within a chosen window — seven days is common. Others ask the customer directly, with a one-line “was your issue resolved today?” after the conversation.
The non-obvious consequence: the window and the same-issue rule change the number materially. A 3-day window flatters everyone; a 30-day window with loose issue-matching punishes everyone. Neither is wrong — but comparing your FCR to anyone else’s, or to your own past under a different definition, is comparing different measurements that happen to share a name. Fix the definition first, in writing, then trend it.
Every failed first contact is paid for twice — once in the repeat work for your team, once in the accumulated effort for the customer, who now has to re-explain and wait again. FCR is also the natural counterweight to speed targets: pushing handle time down tends to push resolution completeness down, because the fastest possible reply is a partial one. Teams that track FCR beside their speed metrics catch that trade before customers do.
FCR rate formula. FCR rate = (issues resolved on first contact ÷ total issues) × 100. Count a reopened conversation, or a new contact about the same issue inside your chosen window, as a first-contact failure. An FCR rate of 75 means three of four issues needed exactly one conversation.
To move the rate, study the failures, not the successes: pull the conversations that came back and ask what the first reply was missing. The usual culprits are answers that resolve the stated question but not the next obvious one, and replies sent without checking the account context. Complete first answers are also where drafting help earns its keep — an AI copilot that reads the whole thread before drafting tends to include the follow-up the customer was about to ask.
Give your customers faster answers and your team their evenings back.
Desktop and mobile. Free for solo.