Discord

The assistant can sit in your Discord server and answer there — in the channels you allow, and in direct messages. It uses the same knowledge and the same settings as the widget, and every exchange becomes an ordinary conversation, so analytics, content gaps and lead capture all work as they already do.

Set it up under Deploy → Discord.

You run the bot, not us

Discord bots are their own applications, and this one is yours. You create it, you own the token, and it appears in your server under your name and your avatar rather than ours.

That is a few more steps than pasting a script tag, and there is a reason worth knowing: reading the text of a message requires a privileged intent from Discord. On your own application you switch it on yourself. A single shared bot serving every customer would have to be reviewed by Discord once it passed 100 servers, and its name would be ours in your community.

Setting it up

1. Open Discord’s developer portal and create a New Application. Name it whatever your members should see.
2. Go to Bot in the sidebar. Under Privileged Gateway Intents, turn on MESSAGE CONTENT INTENT.
3. Still on Bot, press Reset Token and copy the token it shows you.
4. Paste it into Bot token under Deploy → Discord, turn on Answer in Discord, and save.
5. Copy the Application ID from General Information into the same page. An invite link appears.
6. Open the invite link as someone who can manage the server, choose the server, and confirm.

The step everybody misses

Step 2. Without MESSAGE CONTENT INTENT Discord refuses the connection outright, and the channel will sit there saying it needs attention. If it does, that is almost always why. Switch the intent on, then press Reconnect.

Discord shows a bot token exactly once. If you did not copy it, reset it again and paste the new one — resetting invalidates the old token, so the bot will stop answering until you do.

When it answers

Only when mentioned (the default) means the assistant replies when someone writes @YourBot how much does the course cost? and ignores everything else. That is what you want in a channel where people also talk to each other.

Every message means it answers every message in the channels you allow. That suits a channel that exists for questions, and is a poor fit for a general one: it is noisier, and every reply costs a model call.

Only these channels takes channel IDs. To get one, turn on Developer Mode in Discord (Settings → Advanced), then right-click a channel and choose Copy Channel ID. Leave the field empty to let it answer anywhere it has access, which is governed by Discord’s own channel permissions.

Answer direct messages covers one-to-one conversations with the bot, outside any channel.

The assistant never replies to another bot, and never to itself.

What a conversation is

In a channel, each person gets their own conversation. Two members asking different things in the same channel do not end up sharing a transcript, and neither sees the other’s context.

A conversation with a quiet stretch of more than 24 hours starts fresh on the next message. Discord, unlike email, has no marker that says “this is a follow-up” — the same person asking something unrelated a week later looks identical to a continuation — so the gap is what separates them.

Answers are capped at Discord’s 2,000-character limit and split across messages when they run long.

Rate limits

One member can get 15 answers an hour. Past that their messages are ignored until the hour rolls on. This is the same idea as the email channel’s cap: it stops one bored person in a public server running up a bill.

Leads

If a member types an email address or a phone number, the same extraction that runs in the widget runs here, and the lead syncs to your CRM if that is connected.

A Discord account on its own is not contact information — a user ID is not a way to reach anyone off the platform — so a Discord conversation only becomes a lead when someone actually shares a way to be contacted. This is unlike the email channel, where the sender’s address arrives with the message.

When it stops working

The connection is a socket the bot holds open, so it has no address you can test from outside. Deploy → Discord is where its state lives:

• connected — the socket is open right now.
• connecting — reconnecting, normally for a few seconds.
• needs attention — Discord refused something and said why. The message on the card is Discord’s reason, and it stays there until it is fixed.

Brief disconnections are normal and repair themselves; Discord asks clients to reconnect from time to time, and the connection resumes where it left off.

A needs attention state does not repair itself, because retrying a token Discord has already rejected would never succeed. The two causes are a token that was reset (paste the new one) and the message-content intent being off (switch it on). Press Reconnect afterwards.

Turning Answer in Discord off disconnects the bot. It stays in your server and stops responding, which is the quick way to mute it without removing it.