Canonical: https://botbento.com/usecases/validate-support-answers-against-documentation-before-replyi/
Format: Markdown representation of the public HTML page.

# Validate support answers against documentation before replying

[Support](https://botbento.com/usecases/support/) · Intermediate

Catch invented features and logs before a customer sees them

An AI bot helps a support team draft replies that stay grounded in the available product documentation. It checks each claim, flags missing evidence, and routes uncertain or high-impact questions to a human instead of filling gaps with plausible details.

## Quick answers

**What does it do?** Catch invented features and logs before a customer sees them. Result: Grounded reply or human escalation.

**What does it need?** Tools: Chat, Docs, Notes. Intermediate: some setup. The prompt includes an approval step.

**How do I run it?** When something happens: Support question arrives. Copy the prompt below into a bot in BotBento.

## How it works

1. When something happens: Support question arrives
2. Then: Check claims against documentation
3. Result: Grounded reply or human escalation

## Prompt to start with

```text
You draft support replies grounded in the provided documentation. For every question, identify the specific claim or instruction, cite the document section you used, and mark anything you cannot verify. Never invent features, log locations, event names, or interface paths. If documentation is missing or conflicting, ask for clarification and recommend escalation to a human. Draft replies only; sending any message, contacting a customer, making a payment, or deleting records must wait for the user's explicit approval.
```

## Tools it uses

Chat, Docs, Notes

## Works with

BotBento

## Tags

support, documentation, quality, escalation

## Source

[Tell HN: Twilio support replies with hallucinated features](https://news.ycombinator.com/item?id=45748570) — Hacker News · checked 2026-11-13

Summarized in our own words. Any results described there are the authors’ own, not measured by BotBento.

Verified 2026-11-13: passed every automated gate and a second-model review (kimi-code/k3.1-pro). Automated, not human review. [How verification works](https://botbento.com/usecases/verification/)

By BotBento Editorial · Added 2026-11-13 · Updated 2026-11-13 · [Suggest a correction](https://botbento.com/contact/)

## Related use cases

- [Answer questions from product documentation](https://botbento.com/usecases/docs-question-answering/) — Answers from your docs, with a link to the exact page.
- [Persistent customer context for support conversations](https://botbento.com/usecases/persistent-customer-context-for-support-conversations/) — Track user preferences and interaction history across support chats
- [Resolve a stuck billing account and escalate a blocked invoice](https://botbento.com/usecases/resolve-a-stuck-billing-account-and-escalate/) — Collect invoice evidence, draft support requests, and track escalation paths for a billing block
