FCR — First contact resolution

First contact resolution is the percentage of questions resolved in the first interaction, without the customer having to write again and without the conversation passing to another person. It is the metric that best summarises whether the team has what it needs to answer within reach.

What is first contact resolution?

First contact resolution is the percentage of questions resolved in the first interaction, without the customer having to write again and without the conversation passing to another person. It is the metric that best summarises whether the team has what it needs to answer within reach.

Also: FCR · first touch resolution

It is not the same as answering fast

You can have an excellent first response time and a terrible first contact resolution: just reply immediately asking for more details. The two metrics together say something neither says alone; the first without the second rewards exactly the wrong behaviour.

Why it matters

What changes in a SaaS

Every extra contact multiplies the cost of a case and the effort for the customer. Raising this metric is the most direct way to lower cost per ticket without touching volume, and it is nearly always achieved by giving access to the data rather than adding people.

Ilustración de barras crecientes en los colores de Intake

First contact resolution in detail

  • How it is calculated

    Conversations resolved with no reopen and no handoff, divided by the total. The definition of "resolved" has to stay the same across the whole period, or the series cannot be read.

  • Why it drops

    Nearly always for the same reason: whoever is answering does not have the fact they need in front of them. If answering requires opening another tool, asking a colleague, or asking the customer for something already in the system, the first reply is not going to resolve.

  • How to raise it

    By putting the account context on the same screen where the reply is written, allowing the most common actions to run without leaving the conversation, and documenting the cases that repeat. All three attack the same problem: the distance between the question and the data.

Questions about first contact resolution

What is a good first contact resolution rate?

It depends heavily on how complex the product is, so comparing it across companies says little. What is actionable is segmenting by question type: if billing questions resolve at first contact far less than the rest, there is a missing piece of data right there.

Does it count as first contact if an AI agent answers?

If the case is resolved and the customer does not come back, yes: the metric measures the experience, not who typed. If the agent answers and the customer rephrases, that is not resolution, it is one more contact.

Related terms

A term on its own is only half understood. These come up in the same conversation.

Try it without dropping what you use