How to connect Discord to AskVault

Written by Aashiq, Founder, AskVault · Reviewed by Aashiq

Last updated: May 15, 2026 · 4 min read

When Discord is the right channel

Discord is the best channel for three patterns: community-support servers where members help each other and the bot fills the gaps when no one is online, open-source projects where the bot answers documentation questions from the project's docs, and gaming or hobbyist communities with a real-time feel.

For B2B support of customers who aren't already in Discord, the website widget or WhatsApp is usually better. Discord is for communities that already live there.

Setup, step by step

Five steps total, about 5 minutes end-to-end.

Create a Discord application. Open the Discord Developer Portal at discord.com/developers/applications. Click New Application. Give it a name (this is what users see, like "Acme Help Bot"). Click Create.
Add a Bot user. In the left sidebar, click Bot. Click Add Bot. Confirm.
Copy the bot token. Under Bot, click Reset Token, then Copy. Save this somewhere safe. You only see the token once. Treat it like a password.
Enable required intents. Still under Bot, scroll to Privileged Gateway Intents. Toggle on Message Content Intent so the bot can read messages addressed to it. Save changes.
Connect to AskVault. Open the AskVault dashboard, Deploy > Discord, paste the bot token, click Connect. AskVault validates the token and generates an invite URL.

Copy the invite URL. Open it in your browser. Pick the Discord server you want the bot in. Discord asks you to approve the bot's permissions. Click Authorize.

The bot now appears in your server's member list. Test it: type @AcmeHelpBot what's your refund policy? in any channel where the bot has access.

Permissions Discord asks for

AskVault's Discord bot requests these scopes:

Send Messages. Required so the bot can reply.
Read Message History. Required so the bot can read what the user asked.
Use Slash Commands. Optional, enables /askvault in the server.
Embed Links. Optional, lets the bot include clickable source citations.
Read Messages/View Channels. Required so the bot can see incoming messages.

No moderation scopes. The bot can't ban users, delete messages, or change server settings.

Three ways users invoke the bot

Direct messages. Members can DM the bot directly. Bot replies in the DM thread.

@-mentions in channels. Mention the bot in any channel it's a member of: @AcmeHelpBot how do I reset my password?. Bot replies in-channel.

Slash commands. Once registered (automatic after install), members can use /askvault [question] from any channel. Works without inviting the bot to that specific channel.

The slash command is the lowest-friction option for big servers. Members don't have to remember the bot's name; Discord auto-completes the slash command.

Limit which channels the bot responds in

By default the bot responds anywhere it has been granted Read Messages permission. To limit it:

In Discord, open Server Settings > Roles.
Find the bot's role and edit it.
Under Channel Permissions, restrict the bot's role to specific channels.

Or in AskVault, Deploy > Discord > Channel Allowlist lets you specify exact channel IDs the bot will respond in. Useful for servers with both a public support channel and private channels the bot shouldn't see.

Group channels and thread replies

Discord threads (channel forks) are supported. The bot responds within the thread, preserving context across the conversation. Long support exchanges that would clutter the main channel can be moved to a thread without losing the bot's context.

For voice channels, the bot doesn't respond. Voice channel transcription is on the roadmap.

Identity and authentication

Discord's user identity is verified by Discord itself, so AskVault gets the verified Discord user_id on every message. For audience-based scoping (e.g., paid members see one set of docs; free members see a different set), map Discord role IDs to AskVault audience tags under Settings > Discord > Role Mapping.

This requires the guild_members.read scope, which AskVault prompts for when you enable role mapping. Business+

Limits and pricing

Discord is included on Growth and above. The Discord API has rate limits of 5 messages per channel per 5 seconds; AskVault stays well under this for normal traffic.

Each successful AI-reply on Discord counts as 1 query against your plan's monthly quota. A busy community server with 50 active questions per day uses about 1,500 queries per month.

Common pitfalls

Bot stays offline after invite. The token was reset after you copied it. Get a fresh token from the Developer Portal and update AskVault.

Bot doesn't see messages. Message Content Intent is off. Go back to the Developer Portal, Bot section, enable it.

Slash commands don't show up. Discord caches slash commands per server for up to an hour. Wait and try again, or kick + re-invite the bot.

Bot replies but the response is empty. Your AskVault workspace has no indexed content. Add a knowledge source under Knowledge Hub.

FAQ

Can the bot escalate to a human?

Yes. Enable the escalate_to_human skill. When triggered, the bot pings a designated role or channel and stops auto-responding to that thread. A human takes over inside Discord. Growth+

Does the bot work in DMs even if it's not in the user's server?

If the bot has been invited to a server the user is a member of, yes. Discord requires the bot and user to share at least one server for DMs to work.

How do I uninstall the bot?

Either kick it from the server (right-click bot > Kick) or delete the Discord application from the Developer Portal. AskVault detects the disconnection and marks the channel inactive.

Can I run multiple Discord bots in one server?

Yes. Each AskVault workspace can have its own Discord bot with a different name. Useful when a server has separate communities (e.g., "Help Bot" for support questions and "Docs Bot" for technical questions).

Will the bot count toward my server's bot limit?

Discord allows up to 5 bot accounts on Free servers and more on Premium servers. AskVault counts as 1.

Was this page helpful?