## TL;DR
Deflection that hurts CSAT is usually deflection that hides the humans, not deflection that answers the question. The safe way to deflect more: find the searches customers already run that return nothing useful, fix those articles first, and surface them where the customer is already looking. Measure per article, and roll back anything whose CSAT dips. Good deflection feels like a fast answer, not a locked door.

## The query

```text
how to improve deflection without hurting CSAT
```

## Use this when

- Leadership wants fewer tickets but customers complain about self-service
- Deflection rate is flat despite a big help center
- A chatbot was added and CSAT dropped
- You need to cut volume without cutting the humans

## Not for

- Writing chatbot conversation flows
- Justifying headcount reductions
- Auto-closing or auto-resolving tickets
- Building a help center from zero

## Steps

### 1. Find the searches that fail today

Pull help-center search terms with high volume and zero clicks on results, plus the top ticket categories that already have articles. That gap is your deflection backlog.

Expected output: a ranked list of ten to twenty searches and categories to fix first.

### 2. Fix the articles before you promote them

Rewrite each target article to the copyable template: verdict first, steps with checks, still-stuck closer. Promoting a bad article just teaches customers that self-service doesnt work.

Expected output: every backlog article rewritten and agent-approved.

### 3. Put answers where customers already look

Surface the fixed articles in the ticket form, in the product where the error happens, and as suggested replies. Dont make the customer go find the help center.

Expected output: article views rising from surfaces outside the help center.

### 4. Measure deflection per article, not in aggregate

Track tickets avoided per article and the CSAT of customers who viewed it. Aggregate deflection hides the articles that deflect by frustrating people.

Expected output: a per-article dashboard with deflection and CSAT side by side.

### 5. Roll back anything that dips CSAT

If an article's viewers rate lower than ticket-filers on the same issue, pull it from the suggested surfaces and fix it. One bad article poisons trust in all of them.

Expected output: a standing rule, not a one-time cleanup.

## Ready-to-use deflection check

```text
Before promoting any article to a deflection surface:
[ ] Verdict in the first three lines
[ ] Steps have checks, one action per step
[ ] "Still stuck" closer names what to send us
[ ] Two agents agree it answers the ticket
[ ] CSAT of viewers tracked separately from filers

Promote only when all five boxes check out.
```

## Variant phrasings

### increase self-service resolution rate safely

Fix failing searches first, promote second, measure per article. The order matters.

### reduce ticket volume without hurting satisfaction

Deflection is an answer-quality problem before it is a placement problem.

### help center deflection best practices

Per-article metrics and the rollback rule. Aggregate deflection numbers lie.

## Why it happens

Most deflection efforts start with placement, pushing customers toward self-service, while the articles themselves still fail. Customers learn that self-service is a maze and start every future issue with "just get me a human," which tanks both deflection and CSAT. Answer quality has to come first or the funnel works backwards.

## Edge cases

- High-emotion issues (billing disputes, outages): dont deflect these at all. A human first is the right call.
- Low-volume complex issues: deflecting these isnt worth the article maintenance. Let them be tickets.
- Logged-out users who cant reach in-product help: the ticket form suggestions are your surface there.
- Seasonal spikes: temporary deflection surfaces are fine, but keep the per-article CSAT check running during the spike.

## Provenance

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