## TL;DR
Deflection rate is the share of customer issues resolved without a human agent: through the help center, in-product guidance, or an AI assistant. Calculate it as deflected sessions divided by total support-seeking sessions, and be honest about what counts as deflected (a resolved session, not just a page view). Improve it by fixing search first, covering the top 20 ticket drivers with great articles, and putting help where the problem happens in the product. A real 30 percent deflection with honest math beats a fake 70 percent.

## The query

```text
deflection rate: what it means and how to improve it
```

## Use this when

- Leadership asks for a deflection number
- Building a self-service or help-center strategy
- Deflection is flat and you need levers
- Auditing whether your deflection math is honest

## Not for

- Improving CSAT on agent-handled tickets
- Deciding ticket priorities
- Chatbot build or vendor selection
- Reducing handle time

## What it means

### The definition

Of all the times customers sought help, what fraction got resolved without touching an agent. Self-service success, not self-service traffic.

### Honest math

Deflection rate = sessions resolved via self-service / total help-seeking sessions. A help-center page view is not a deflection. A session that ends with no ticket filed and no repeat visit is.

### The vanity trap

Counting every page view as deflected, or excluding the tickets that self-service failed to prevent. Both inflate the number and hide the real gaps.

## Steps

### 1. Define what counts as deflected, in writing

A session counts as deflected when the customer views help content and does not file a ticket within 24 hours, or when an AI assistant resolves the session with a confirmed answer. Write it down, get agreement, never change it quietly.

Expected output: a written definition everyone reports against.

### 2. Measure the baseline honestly

Pull the last 90 days: help-center sessions, AI assistant sessions, tickets filed. Compute the rate with your definition. Expect it to be lower than the number you have been quoting.

Expected output: a baseline number with the methodology attached.

### 3. Find your top 20 ticket drivers

The tickets that could have been self-served cluster in 20 topics. List them by volume. This is your deflection roadmap, in priority order.

Expected output: a ranked list of deflectable ticket drivers.

### 4. Fix search before writing articles

Most failed self-service is failed search, not missing content. Test the top 20 queries against your help-center search. If the right article is not in the top 3 results, fix that before writing anything new.

Expected output: top 20 queries each returning the right article in the top 3.

### 5. Write or rewrite articles for the top drivers

Answer-first, symptom-titled, with the exact phrases customers use. One great article on a top driver deflects more than ten mediocre ones on edge cases.

Expected output: top-10 driver articles rewritten to the answer-first template.

### 6. Put help where the problem happens

In-product tooltips, contextual help links on error states, and proactive guidance at known friction points deflect better than any help-center article, because the customer never has to go looking.

Expected output: help embedded at the top 5 in-product friction points.

## Variant phrasings

### what is ticket deflection in customer support

The definition section above. Deflection = issues resolved without an agent, measured honestly.

### how to calculate deflection rate for support

Step 1 and 2. The definition and the baseline, with the methodology written down so the number stays comparable over time.

### how to increase self-service deflection

Steps 4 through 6. Search first, then articles, then in-product help. In that order, always.

## Why it happens

Deflection stalls because teams measure traffic instead of resolution, write articles nobody can find, and build help centers separate from the product where the problems happen. The honest math in step 1 is uncomfortable but it is the only way to know which lever actually works. Teams that fix search first typically see a bigger deflection jump than teams that write 100 new articles.

## Edge cases

- AI assistant deflection: count only sessions where the user confirmed the answer or didnt escalate. An AI that chats for 10 minutes and then creates a ticket deflected nothing.
- Forced deflection (hiding contact options): spikes the number and tanks CSAT. Customers who cant reach you dont count as self-served.
- Complex B2B products: realistic deflection is lower, 15 to 25 percent is good. Chasing 60 percent will just frustrate enterprise users.
- Seasonal spikes: measure deflection as a rolling average, not a monthly number, or launch weeks will wreck your trend line.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LxLOg2GJ8NTTJMhvgPcSxQ