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. That is why they are worth reading together. The first on its own rewards exactly the wrong behavior.
Why it matters
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.
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 data 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.
The formula, with an example
Conversations resolved at first contact divided by the total conversations in the period, times one hundred.
The figures in the example are illustrative.
- What counts. No reopen in the following days and no handoff to another person.
- Example. 400 conversations, of which 280 were resolved with no reopen and no handoff, give 70%.
