Resolution and deflection
Deflection rate counts requests that never reached the team, resolved or not.
Resolution rate counts only those that ended well. A customer who gives up on the chat lowers the team’s load and raises deflection, and should not raise resolution.
Why it matters
The same word is used to measure very different things, and a high rate can come from a generous definition.
Before comparing two vendors or two months, you need to know which conversations are counted and when one is taken as resolved. Well defined, it says how much work the AI removes and which topics still need a person.
The formula, with an example
AI resolution rate is calculated by dividing the conversations resolved by the AI by the conversations in which the AI replied, times one hundred.
The figures in the example are illustrative.
- Example. If the AI replied in 1,000 finished conversations and 620 closed without anyone on the team stepping in, the rate is 62%.
- Over the total. If another 400 conversations went straight to a person, the AI resolved 44% of everything that came in.
What counts as resolved
Each tool defines it in its own way, and there are three usual criteria.
| Criterion | Taken as resolved when | Its weak point |
|---|---|---|
| By confirmation | The customer says it was resolved | Few customers answer |
| By silence | The customer does not write again within a period | It also counts those who gave up |
| No intervention | Nobody on the team had to step in | It depends on handover working |
What to read it alongside
Resolution rate is read next to three other figures, because alone it can be inflated.
- Satisfaction on the conversations the AI resolved.
- Reopens, the customers who come back about the same thing.
- Handover rate, and the reasons conversations go to a person.
How Intake counts it
Intake counts as handled by the AI a finished conversation in which the agent gave an answer of its own, leaving out greetings and automatic notices.
It takes it as resolved by the AI if it was not handed to a person, was not assigned to anyone and nobody on the team wrote. The same definition is used in Analytics, in reports and in the weekly summary.
