Start with knowledge control

Ask where the answers come from and who can change them. A bot that learns automatically from every message sounds convenient until it repeats a joke, an outdated price or a member's personal detail.

A controlled knowledge source is easier to audit, correct and explain to your community. You should know exactly which channel or document the bot uses.

Check channel behaviour

The bot should respect where it is allowed to answer. Support channels, normal channels, media-only channels, ignored channels and ticket channels need different behaviour.

Test a mention, a trigger word, an ignored channel and a media-only channel. If the bot replies everywhere by default, you will spend more time cleaning up than you save.

Look for a real handoff path

The most important question is what happens when the bot does not know. It should hand the conversation to a human role with a clear message, not invent an answer or leave the member waiting.

If private conversations matter, check the ticket workflow: permissions, staff relay, limits and what happens when staff are offline.

Understand the limits before you pay

Read the monthly answer limit, direct-message limit and knowledge limit. Check what happens at the limit and whether a booster is available.

Confirm the number of servers covered by one subscription. If you run several communities, the total cost is not the price of one plan.

Ask about isolation and permissions

Knowledge and settings should be scoped to one server. Ask how the bot separates customer data and what Discord permissions it requests.

Administrator permission is sometimes needed for ticket creation and channel overwrites. Understand why it is requested and whether you are comfortable granting it.

Evaluate the setup and the exit

A good bot should be testable in one channel before it reaches the whole server. The dashboard should show what changed and when.

Also check how to remove it. You should be able to take the bot out of a server without losing the community's Discord content.

A short checklist

  • Can you inspect and edit the knowledge source?
  • Does it respect channel roles and ignore muted channels?
  • Can it hand off to a human role?
  • Are private tickets possible, and who can see them?
  • What are the answer, DM and knowledge limits?
  • Is each server isolated from the others?
  • Can you test in one channel before launch?
  • Can you remove the bot cleanly?