Start with the questions, not the bot
Before choosing a tool, collect the questions your team answers most often. Look at the last few weeks of support channels, onboarding messages and moderator notes. Group them into themes: access, rules, billing, setup, troubleshooting and private requests.
This list tells you what the knowledge source must contain and what should stay with a person. A bot cannot fix a question nobody has written down, and automating a sensitive request is worse than leaving it to staff.
- Which questions repeat every week?
- Which answers change often?
- Which requests need account details or a private channel?
- Which answers are already wrong or out of date?
Build one visible knowledge source
Pick a channel members can read but only staff can post in. Write one question and one answer per message where possible. Use the words members use, not internal project names.
Keep the source small at first. Ten accurate answers are more useful than a hundred copied documents. Add a link to longer documentation when the full answer does not fit in a Discord message.
Choose where the assistant should answer
Not every channel should receive an automated answer. A support channel can answer every eligible question, while a general chat channel should respond only when mentioned or when a trigger word appears. Announcements and media channels often need to stay quiet.
Write the channel map down before configuring the bot. It is easier to decide that a channel is ignored than to clean up repeated replies after launch.
Keep a human handoff path
Decide which roles should receive escalations and what the handoff message should say. Test a question the assistant cannot answer and confirm a person is actually notified.
For private conversations, use a ticket channel rather than asking members to open a DM. A private ticket keeps the context in one place and gives staff a clear place to reply.
Measure the right thing
Do not judge success by the number of bot replies alone. Look for fewer repeated questions in public channels, faster first responses and a support team that spends less time copying the same answer.
Review the knowledge source regularly. Remove answers that are no longer true and add new questions as they appear. Automation without maintenance becomes another source of stale information.
A simple rollout plan
Week 1
Write the first ten answers and map your channels.
Week 2
Enable the assistant in one support channel and test handoff.
Week 3
Review unanswered questions and add the missing answers.
Week 4
Expand to more channels only if the first channel is working.