How to Make a Discord Bot Answer Questions From Your Documents

2026-08-19 · Wallu Team · 4 min read · Tutorials

A practical walkthrough of getting a Discord bot to answer from your own documentation, including the configuration choices that decide whether members trust it.

Table of Contents

• What You Are Building
• Step 1: Get Your Documentation Somewhere Readable
• Step 2: Index It
• Step 3: Decide Where the Bot Speaks
• Step 4: Set the Refusal Behaviour
• Step 5: Test With Questions You Know Are Not Covered
• What It Costs
• Keeping It Accurate
• FAQ

What You Are Building

A bot that, when a member asks something, looks up your actual documentation and answers from

it. Not a bot that guesses. The difference is entirely in configuration, and most of the work

is deciding what the bot should do when it does not know.

Step 1: Get Your Documentation Somewhere Readable

The bot needs a source. In order of how well they work:

A live documentation site. Best option. A bot that crawls a URL stays current when you

update the page, with no further action from you.

A help centre or knowledge base. Same benefit, already structured into articles.

Uploaded files. Works, but every future edit means re-uploading. This is where knowledge

bases go to die.

If your documentation lives only in a pinned Discord message and three people's heads, that is

the actual problem, and no bot will fix it. Write it down first.

Step 2: Index It

With Wallu Assist you give it your website URL and it crawls and indexes the content itself.

Pages are split into chunks, converted to vectors and stored so they can be retrieved by

meaning rather than keyword. A member asking "how do I cancel" will match a page titled "Ending

your subscription", which keyword search would miss entirely.

If you are self-hosting, this is the embedding job you will be re-running by hand every time

the docs change.

Step 3: Decide Where the Bot Speaks

This matters more than people expect. A bot answering in every channel is the fastest way to

make members resent it.

Set a mode per channel:

• Off for off-topic, memes, and anywhere social
• Mention-only for general chat, so it helps when asked and stays out otherwise
• Answer everything for support and help channels, where every message is a question

Wallu Assist configures this per channel, so a 40-channel server can have the bot active in

three.

Step 4: Set the Refusal Behaviour

The single most important setting. When the answer is not in your documentation, the bot can

either improvise or decline.

Improvising produces fluent, confident, wrong answers about your refund policy. Turn on

knowledge-base-only mode so it answers strictly from indexed content and otherwise says it does

not know and offers a human.

Also confirm human takeover. When a moderator starts replying, the bot should go silent

immediately. Wallu Assist pauses automatically and resumes after 15 minutes of quiet, which is

configurable.

Step 5: Test With Questions You Know Are Not Covered

Everyone tests the questions they documented. Those pass. Test the opposite.

Ask something deliberately absent, phrased confidently, as a member would. A correctly

configured bot declines. A badly configured one invents. You want to discover this yourself,

before a member does.

Then ask three real questions from your support history and check the answers word by word

against the source.

What It Costs

Prices from each vendor's public pricing page, August 2026.

The relevant comparison for this job is the last two rows. MEE6, Carl-bot and Dyno do not

answer from a knowledge base, so their prices are for a different product entirely.

Keeping It Accurate

The failure mode of every documentation bot is drift. The docs change, the index does not, and

the bot keeps answering from an old version while sounding authoritative.

If your bot crawls a live site, this solves itself. If it indexes uploads, put a recurring

reminder in your calendar, because nobody remembers unprompted.

A useful habit: review the questions the bot declined to answer. That list is your

documentation backlog, generated for free. More on that in

training a bot on your website.

FAQ

How does a Discord bot read my documentation?

It crawls or ingests your content, splits it into chunks, converts those into vectors and

stores them. When someone asks a question, it retrieves the closest chunks and answers using

them as context. This is retrieval-augmented generation.

Can it answer from a website rather than uploaded files?

Yes, and it is the better option. A bot that crawls your live site stays current automatically,

where uploaded files need re-uploading after every edit.

How do I stop it inventing answers?

Enable knowledge-base-only mode, so it answers strictly from indexed content and declines

otherwise. Then test it with a question you know is not documented, and confirm it declines.

Can I limit it to certain channels?

Yes. Set a mode per channel: off, mention-only, or answer everything. Most servers want it

active only in support channels.

What does this cost?

Wallu Assist starts at $4.99/month per account, including 350 AI responses across nine

channels. Self-hosted RAG bots have no licence fee but cost hosting plus model API charges.

What happens when a moderator wants to take over?

A good bot detects the human reply and stops. Wallu Assist pauses automatically and resumes

after 15 minutes of inactivity, so you never have to tell it to be quiet.

---

Ready to give your Discord community 24/7 AI support? See Wallu Assist pricing or start with Assist