First contact resolution: what it is and how to fix it

First contact resolution is the share of customer questions you settle in a single back and forth. One email, one chat, one call. No "let me check and get back to you." For a small business it's the most honest measure of whether your support works, because a customer who has to ask twice already thinks you're slow, even if both replies went out in ten minutes.

What first contact resolution actually measures

First contact resolution counts outcomes, not speed. A ticket only counts if the customer got what they needed from your first reply and never came back about it. Answering in four minutes with "I'll look into this" scores zero.

You'll also see the older name, first call resolution, which is the same measurement from the days when support meant a phone line. First contact resolution is the version that covers email, chat and your web form, so it's the one that fits how a small business really gets contacted.

Two things make it worth watching more closely than most other support metrics. Customers feel it directly. And it only improves when you fix something real, rather than when you work later into the evening.

How to calculate your first contact resolution rate

The formula is short:

First contact resolution rate = (tickets solved in one reply ÷ total tickets) × 100

Forty of your sixty tickets last month needed one reply. That's 67 percent. You can count this by hand for a month before you automate anything.

What counts as one contact

Decide this once and write it down, because the number is worthless if the rule keeps moving. A workable definition for a small team:

• The customer asked once and you answered once. A "thanks, that worked" reply afterwards doesn't break it.
• They didn't contact you again about the same thing inside seven days. Pick a window and keep it.
• A ticket you passed to someone else, or promised to check on, is not one-touch even if it was sorted that afternoon.

Which tickets to leave out

Some questions can never be answered in one go. A bug report isn't finished until the bug is. A refund tied to a returned parcel waits on the parcel. Exclude those categories from the count rather than letting them drag your first contact resolution rate down every month. Just be consistent about which ones you exclude, and note the rule somewhere your future self will find it.

What's a good first contact resolution rate?

According to SQM Group's benchmark research, the industry standard sits between 70 and 79 percent, with the average landing near 70. A score of 80 percent or higher is unusual, and only about 5 percent of contact centres get there.

Those figures come from large contact centres, so read them as a rough ceiling rather than a target you're failing. A shop selling one simple product will beat them easily. A software business with a complicated setup process will sit well below and be doing nothing wrong. Your own number from three months ago is a far better comparison than anyone else's average.

The same research found that each one percent gain in first contact resolution tends to arrive with roughly a one percent drop in operating cost and a similar rise in customer satisfaction. There's no mystery in that. Every repeat contact is another conversation somebody has to read, work out and answer, and the customer is more annoyed the second time.

Why a high score can be bad news

Here's the part most guides skip. A first contact resolution rate of 95 percent usually means one of two things has gone wrong.

The first is that your easiest questions are landing in your inbox at all. Where's my order. How do I cancel. Do you ship to Ireland. Those are one-touch by nature, so a queue stuffed with them flatters the score while quietly telling you your help pages are too thin.

The second is early closing. Once people are measured on one-touch rates, some of them start sending a plausible answer and marking the ticket done. The customer writes back two days later and opens a fresh ticket, which counts as its own case. The score stays lovely and the customer is furious.

So keep first contact resolution next to your repeat contact rate and your satisfaction scores. On its own it can be gamed by accident, with nobody meaning any harm.

Four ways to improve first contact resolution

Go through last month's two-touch tickets and ask why each one needed a second reply. The answers nearly always fall into four piles.

1. Give whoever answers the full picture

"Let me check your order and come back to you" is a resolution failure caused by a missing screen. If the person replying has to open three tools to see what someone bought, a good chunk of your tickets will take two rounds no matter how sharp that person is. Order details, past conversations and the customer's plan belong next to the reply box. That single change does more for first contact resolution than any amount of training.

2. Let people finish the job

The next most common cause is permission. Someone knows the right answer, knows a $12 refund is the sensible outcome, and still has to stop and ask you. Set a limit anyone can act on without checking: refunds under a fixed amount, replacements for damaged goods, one-off extensions. Write the limit down so nobody has to guess where it sits, and raise it when it turns out to be too low.

3. Write the answer down once

Read the last fifty tickets and tally the repeats. Most small businesses find five or six questions cover half the queue. Each of those deserves a proper help article, which pays twice: some customers find it and never write in, and whoever is answering can send a complete reply in one go instead of typing it from memory and forgetting the last step.

4. Get it to the right person first time

If a ticket has to change hands before it can be answered, one-touch is already gone. For a team of two or three this is mostly about having an agreed handover rule rather than clever routing software. Who takes billing, who takes the technical questions, and what happens when the one person who knows is away for a week.

Where a support bot fits in

A chat assistant moves this number in a way that's easy to overstate, so here's the plain version of how ours works.

In SupportifyGPT, hand-written rules do the finding. They work out what the person is asking, spot the ones that need a human straight away, and search your help articles for likely answers. Then a model reads those articles and writes a reply in ordinary sentences, rather than handing back a list of links.

The limit matters more than the capability. It can only answer from what your business has actually written down. If your articles don't cover something, it says so and passes the conversation to you. It can't invent a returns policy you never wrote. And if anything goes wrong it drops back to quoting the article, so a bad day makes it less useful rather than wrong.

Which means it doesn't raise first contact resolution by being clever. It raises it by making your written answers reachable at eleven at night, on a Sunday, while you're asleep. The writing is still your job. When it drafts a new article from a solved ticket, that draft waits for you to approve it before any customer sees it.

All of that is included on every plan we sell, starting at $15 a month, with no fee per answer and no ticket overages. Have a look at the full feature list, or start a free trial and have it running this afternoon.