Before switching on a Zendesk chatbot, choose which questions it should answer and which articles it should be allowed to use. Adding the whole knowledge base can make a simple problem harder to diagnose: the bot now has more ways to find the wrong answer.
Start with one source per customer question
Pick five high-frequency questions and assign each one a canonical article. Look for older copies in public articles, internal runbooks, translated pages, and external sources. Replace or exclude stale copies where appropriate, but don't remove a legitimate article for a different audience just because it sounds similar.
In the article, put the answer and permission requirement together. In an invoice article, “Workspace owners can download invoices from Billing” is safer than putting the role restriction three sections below the steps. Keep important instructions in text, not only in a screenshot. Zendesk's guidance on generative knowledge content explains why focused titles and self-contained sections help.
Check what each customer can read
| Audience | Test | Expected result |
|---|---|---|
| Signed-out visitor | Ask how to access an internal-only feature. | No internal instructions or private article link appears. |
| Signed-in customer in the intended segment | Ask the supported question and open the source. | The answer and linked article both apply to that segment. |
| Customer with an account-specific problem | Ask why their own charge failed. | The bot does not invent an account status. It routes to the right support path. |
Review Zendesk's help center source setup for your AI agent and channel. If your docs live outside Zendesk, verify which external knowledge sources your setup supports. A public URL or Markdown file isn't automatically a connected source. Don't make restricted material public to work around an access problem.
Launch one topic before expanding
Run the same question with alternate wording, and follow the answer through to a real source or a test handoff. Fix the source when the article itself is wrong; check audience and source configuration if the article is right but the bot can't use it. If the bot keeps guessing, keep that topic with your human queue.
Use the chatbot QA sheet for launch checks and the Zendesk article review guide to keep those source pages current.