Discord
Invite the CoPhrase bot into your Discord server and map that server to a workspace — no bot to create, no token to paste.
Discord connects by inviting the CoPhrase bot into your server. You do not create a bot, you do not register an application, and you do not paste a token anywhere.
It's an official Discord integration with no ban risk, and — alongside the web chat widget — one of the two channels available first.
One platform bot, not a bot per customer
This is the part that surprises people, so it's worth being explicit.
CoPhrase runs a single Discord bot application across all customers. You invite that one bot into your server. CoPhrase then maps your server (its guild ID) to your workspace, and every message the bot sees in your server is routed to your agent, your knowledge, your inbox.
Why it works this way: making every customer register their own Discord application, configure its intents, generate a token, and paste it into a form is a terrible onboarding flow for something that should take thirty seconds. A single platform bot with a server-to-workspace mapping gets the same result with an invite link.
What about our own branded bot?
The bot that appears in your server carries CoPhrase's identity, not yours. White-labelled per-customer bots are a possible future addition, not something available today. If a CoPhrase-branded bot in your server is a dealbreaker, that's worth knowing before you connect.
Setup
Invite the bot
Start the Discord connection from CoPhrase and follow the invite link. Discord asks which server to add the bot to and shows the permissions it's requesting. You need permission to manage the server (or the "Manage Server" permission) to accept an invite.
Map the server to a workspace
Back in CoPhrase, confirm which workspace this server belongs to and which agent should answer in it. This mapping is what makes the shared bot behave like your bot — a message in your guild is only ever routed to your workspace.
Agencies running many client workspaces: map each client's server to that client's workspace, not to the agency's.
Choose where the agent listens
Decide which channels the agent participates in. A support channel, a DM with the bot, a specific category — not, usually, every channel in the server. Give the bot access only where you want it answering.
How Discord conversations work
Discord is a multi-party channel, and CoPhrase models it as one:
- A Discord channel is a thread in your inbox — with multiple participants, not a single customer.
- Every participant resolves to a contact, so the same person is recognizable if they later reach you on another channel.
- A DM with the bot is a normal one-to-one thread.
That's different from WhatsApp or Instagram, where a thread is essentially one person. In a busy Discord channel, expect the agent to be answering into a room.
Capabilities
| Connection | Persistent socket to Discord — the agent is online continuously |
| Official API | Yes |
| Ban / restriction risk | None |
| Multi-party threads | Yes |
| Inbound media | Images, files, and audio messages are read by the agent |
| Streaming replies | No — the reply is delivered whole |
Things to know
A human reply in the channel pauses the agent on that thread. If one of your moderators jumps in, the agent stops talking there. See Handoff.
Bots don't get replied to. The agent does not answer other bots, and it does not loop with itself.
Rate limits are Discord's. Discord enforces its own send rates. CoPhrase respects them; a busy channel may see replies pace themselves rather than fire instantly.