Discord
Invite the CoPhrase bot into your server and map the server to a workspace — one shared platform bot, multi-party threads, no token to paste.
Discord connects by invite. CoPhrase runs one platform bot; you add it to your server, map that server (guild) to a workspace, and pick the agent that answers. There is no token to paste.
It uses Discord's official API, and the bot holds a persistent socket — so the agent is online continuously rather than waking up on a webhook.
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 each eligible human MESSAGE_CREATE event in a mapped guild channel is routed to your agent, your knowledge, your inbox. DMs, bots, webhooks, self-authored messages, and unmapped guilds fail closed.
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.
Restrict where the agent listens
Use Discord channel/category permission overwrites to expose only the support areas where the bot should participate. Discord's own permissions are the control surface here — CoPhrase doesn't keep a second allow-list to drift out of sync with them.
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 for that Discord identity. That contact is scoped to Discord — it isn't automatically joined to the same person's WhatsApp or email contact.
Server channels only
Direct messages to the bot are not accepted. A DM has no guild ID, so it cannot be safely mapped to one customer workspace through the shared platform bot — and a wrong mapping means one customer's agent answering in another customer's name. The connector fails closed outside mapped servers.
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 |
| API posture | Official Discord API; normal application policy, intent, permission, and rate-limit requirements still apply |
| Multi-party threads | Yes |
| Inbound media | Images, files, and audio |
| Streaming replies | No — the reply is delivered whole |
Things to know
Only a verified manual-owner reply pauses the agent on that thread. The Discord account must be explicitly mapped to a current user in the same CoPhrase workspace. Unmapped moderators, bots, and webhooks do not acquire human control. 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.
Related
Web chat widget
Embed the CoPhrase agent on your website with a script tag — the fastest channel to connect and the only one with no account risk.
Two routes onto WhatsApp — an unofficial linked-device session on your own number, live today, or the official WhatsApp Business API. The tradeoffs are real.