Chart your ticket volume by subject and the shape is always the same: a long tail, and a very fat head. The head is twenty questions. They arrive every day. They were answered in the documentation two years ago.
The reason they keep arriving isn't that customers are lazy. It's that finding the answer in a help centre requires knowing the vocabulary your docs use, which is a thing customers learn after they've solved the problem, not before.
Search is the wrong interface for a question
A user's problem sounds like: "my webhook isn't firing when someone updates a record."
Your documentation calls it: "Configuring event subscriptions and delivery retries."
Search matches keywords. The user typed none of the right ones. So they search, find nothing useful, and open a ticket, and an engineer replies with a link to the exact page search failed to surface.
That gap is the entire problem, and it's a language problem rather than a content problem. A model that reads your docs and answers in the user's own words closes it directly.
What deflection actually looks like
User: my webhook isn't firing when someone updates a record Bot: Update events need to be subscribed to explicitly. Creation events are on by default but updates aren't. In Settings → Webhooks, check that
record.updatedis enabled for that endpoint. If it is and you're still not seeing deliveries, the delivery log under the endpoint shows failed attempts and response codes, which usually points to the cause.
That's a ticket that never opened. The user was unblocked in fifteen seconds instead of four hours, which is also a better experience than the ticket would have been.
Measuring the deflectable share honestly
Before you build anything, categorise a month of tickets by how they were resolved, not what they were about. You'll typically find three groups:
Resolved by linking a doc. Fully deflectable. This is usually a much larger share than anyone expects.
Resolved by explaining something not documented. Deflectable once the doc exists, and the fact that it doesn't is the actual finding.
Resolved by looking at the account. Not deflectable, and shouldn't be. These need system access and judgement.
That third group is what your engineers should be spending their day on, and it's currently competing for attention with the first group.
The hallucination boundary
The failure mode that matters in SaaS is a bot confidently describing a feature you don't have.
It's worse than a wrong answer elsewhere, because the user acts on it. They go looking for a setting that doesn't exist, waste twenty minutes, and open a ticket that's now harder to resolve because they're annoyed and half-convinced the feature exists and is broken.
Two configurations prevent this. First, restrict answers strictly to indexed content, no general-knowledge filling in of gaps. Second, make "I don't know, let me get someone" a first-class, non-embarrassing response. A bot that admits uncertainty is trusted. A bot that improvises isn't, and once users stop trusting it they stop using it and you've built nothing.
Onboarding is where it pays best
Deflection is the obvious win. Activation is the bigger one.
New users abandon during setup, quietly, at the first thing they can't work out. They don't open a ticket. They're not invested enough yet. They just stop.
A bot sitting in your onboarding flow catches exactly those moments. "Where do I find my API key?" "Do I need to verify the domain first?" "What permissions does the integration need?" Each of those, answered instantly, is an activation that would otherwise have silently failed.
Map your activation funnel and the largest cliff is often a single step. DNS verification, or something equally unglamorous. The docs cover it. Nobody finds the docs. Answering that one question in-flow can move activation further than a quarter of redesign work.
Pre-sales is a third channel
The same bot on your marketing site answers the pre-sales questions that currently go to a form: does it integrate with X, what's in each plan, is there an API, how does pricing work at volume, is there SSO.
Those questions arrive from evaluators doing research outside your sales team's hours, and the ones that go unanswered turn into a competitor evaluation. Capturing them (with an offer to book a demo) converts research traffic into pipeline.
Standing it up
Point it at your docs, help centre, changelog, and marketing site. If your docs are in a repo, that's fine. What matters is that the content is reachable and current.
Then configure three things: answer only from indexed content, escalate anything account-specific to a human immediately, and never speculate about roadmap or unreleased features.
How you'll know it landed
Ticket volume in your top-twenty subjects, before and after. That's the direct number.
But also track the questions the bot couldn't answer. That list is the most honest documentation backlog you will ever get. Written by your users, in their own words, ranked by frequency.