Skip to content

Deflection rate

Adrià Castany 2 min

What is deflection rate?

Deflection rate is the percentage of questions resolved without a person getting involved, either because the customer found the answer themselves or because an automated agent closed it. It is the metric used to justify any investment in self-service or in AI.

Also called

containment rate, automation rate

Topic
Metrics
On this page
  1. Deflecting is not stopping people from writing
  2. Why it matters
  3. Calculating it without fooling yourself
  4. The ceiling depends on the type of question
  5. Signs you are measuring it wrong
  6. The formula, with an example
  7. How Intake handles it
  8. Frequently asked questions

Deflecting is not stopping people from writing

The usual trap is counting as deflected any conversation that never reached a person, including the one where the customer gave up.

A hidden contact button raises deflection rate and damages the business. The metric only means something if "deflected" means "resolved without intervention", and it is verified by the customer not coming back.

Why it matters

It is the one that translates support into money.

Multiplied by what each ticket costs, it says how much self-service saves; without that cross, it is a percentage that decides nothing. It is also the one that best detects whether an AI investment is resolving or merely placing an obstacle in front of the contact form.

Calculating it without fooling yourself

Conversations closed without human intervention and without a reopen in the following days, divided by the total conversations started.

The second condition is what stops you counting the people who gave up.

The ceiling depends on the type of question

Questions whose answer is the same for everybody deflect well with documentation.

Questions that depend on account state do not deflect with documentation however good it is, because the article does not know which plan the asker is on. In a SaaS, that second group is large, and it is what sets the ceiling.

Signs you are measuring it wrong

Deflection rate rises and CSAT falls.

Or it rises and so does the number of customers writing through another channel, such as an email to their account executive or LinkedIn. Both mean the same thing. You have not deflected, you have hidden.

The formula, with an example

Conversations resolved with no person and no reopen, divided by conversations started, times one hundred.

The figures in the example are illustrative.

  • Example. 1,000 conversations in a month, of which 350 close with no intervention and without the customer writing again, give 35%.
  • What does not count. The conversation the customer abandons with no useful answer and the one they reopen two days later.

How Intake handles it

Frequently asked questions

How is deflection rate calculated?

Conversations resolved with no human intervention and no later reopen, over total conversations. Without the reopen condition, the metric also counts whoever got tired and left.

What deflection rate is realistic?

It depends on what share of your questions can be answered from documentation and what share needs the account checked. Before setting a target it is worth classifying a hundred of your own conversations, because that split sets the ceiling, not the tool.

Are deflection and containment the same?

They are used as synonyms. "Containment" comes from the call center world and sounds like holding somebody back, which is exactly the connotation worth avoiding. The goal is resolving without a person, not preventing people from asking for one.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment