Channel routing
Decide which channels the bot watches and how it picks what to answer.
The model
DuggAI thinks about Discord in two layers: servers (one or more Discord servers connected to your project) and watched channels (the channels the bot reads in each server). Set the watched channels in the dashboard under Settings → Integrations. An empty list means the bot listens in every channel it can see.
Picking watched channels
Good candidates:
#help,#support,#questions#installation,#bugs- Any channel that's implicitly "ask the team"
Skip:
#announcements— read-only, no questions- Off-topic / community channels you don't want answered
How the bot decides to reply
Two paths get the bot to answer. An explicit @-mentionalways engages it, even in a channel that isn't on the watched list. In a watched channel, the bot also auto-engages on real questions: a lightweight classifier checks whether an un-tagged message is an actual support question before it replies, so general chatter in a busy channel doesn't trigger it.
Escalation
When the bot escalates, it pings the support role you set during install (default @support). It replies in a thread under the user's message either way, so each question stays self-contained.
Multi-server setups
A common pattern: one server is your public community, one is for paying customers. Connect each server to the same project and set its watched channels independently.
Conversation history
Every Discord thread the bot touches shows up in your Inbox & history. Your team can read the full thread there; replies the bot posts go out under the bot's identity so users see one consistent voice in Discord.