Discord Chatbot for Crypto & Web3 Communities (2026)

Because the community is the product's front door. Most web3 projects publish docs and a help center, but holders and new users ask in the official Discord first, often in the middle of a transaction. The questions repeat: where the official links are, how to add the network to a wallet, why a bridge transfer is taking longer than expected, which announcement is real.

That repetition creates a second problem. A busy, unanswered #support channel is exactly where impersonators wait: someone asks for help, a fake "support agent" sends a DM a minute later. Fast, correct public answers from an official bot shrink that window.

The Discord chatbot channel connects to your server through Conferbot's own Discord app or through your own bot application and token. It answers from your knowledge base and passes anything that needs a person to your team through live chat handover. It is available on every Conferbot plan, including Free.

Keep the bot to questions where your published documentation is the answer:

• Official links and addresses. The website, docs, contract addresses and supported networks, exactly as you publish them, so members stop trusting addresses pasted by strangers.
• How-to questions. Adding a network, bridging, staking or claiming, step by step from your docs.
• Common transaction questions. Why a transaction can sit pending, what a failed transaction usually means, where to check it on a block explorer, with a clear line that the bot cannot see anyone's wallet.
• Roadmap, governance and event dates. Vote windows, AMAs and scheduled upgrades, with dates shown in each member's own time zone through the Discord timestamp generator.
• Security reminders. Every answer that touches wallets can end with the same rule: the team never DMs first and never asks for a seed phrase.

Account-specific or money-specific questions are routed to staff instead. The Discord community template is a useful starting point for the public side.

No bot stops every scam, but an official support bot removes the main opening scammers use: a member asking for help and waiting. Three design choices matter.

Answer in public, quickly. Reply in a thread in the support channel rather than moving the member into DMs. Conferbot can reply in a thread, in the channel or by DM; for crypto support, threads keep the answer visible to moderators and to the next person with the same question.

Say the rules every time. Put the security rules into the answers themselves: staff never DM first, nobody will ever need your seed phrase or private key, and the only valid links are the ones in the official channels. Repetition is the point.

Make the real handoff obvious. When a member needs a person, the bot hands the conversation to your team through the Conferbot inbox and says plainly how staff will reply, so members know what a genuine contact looks like. Members can check how old an account is with the Discord account age checker, which helps spot freshly created impersonator accounts.

This pairing has stricter limits than most, and the bot should be designed around them from the start.

No keys, ever. The bot must never ask for, accept or store a seed phrase, private key or wallet password. Write that rule into the knowledge base and into the handover message, and tell members to delete any message where they posted one.

No investment advice. Price predictions, "should I buy" and yield promises are out of scope. Financial promotion rules differ by country and can apply to what a project's official channels say, so the bot should decline these questions and point to your published risk disclosures. Have your own counsel review what the bot is allowed to say about tokens.

The bot cannot see wallets or chains. Conferbot answers from your content and the conversation; it does not read balances or transactions. Questions about a specific stuck transfer, a missing airdrop or a frozen account go to staff with the details collected.

Discord's rules. Unsolicited DMs to members break Discord's developer policy, and reading channel messages needs the Message Content intent, which Discord reviews once an app passes 10,000 users. See the Message Content intent guide.

Route anything where a wrong answer costs a member money or access:

• A specific transaction, bridge transfer or claim that has not arrived.
• Account or exchange-listing problems, and anything involving identity checks.
• Reports of a scam, a fake site or an impersonator, which moderators should act on quickly.
• Partnership, listing and press requests, which belong with the business team.

Before handing over, a flow can collect the network, the transaction hash and a short description, so staff do not need to ask again. Handover to a person is included on every plan; the conversation lands in the Conferbot inbox, and the flow resumes when the agent closes the chat. A flow can also alert a private staff channel through the Discord notifications integration (Pro and up), and the human handoff entry explains the general pattern.

Most web3 servers already run a verification or token-gating bot and a moderation bot. Conferbot does not replace either: it does not verify wallets, gate roles, kick or ban, and it does not register slash commands, so it never collides with another bot's commands. Give it the support channels and a narrow permission set built with the permissions calculator.

If the bot joins but stays silent, the usual causes are the Message Content intent, a channel permission or Missing Access (50001); the Discord bot not responding guide walks through them in order.

1. Write the source of truth. Official links and addresses, how-to guides, security rules and the list of questions the bot must decline. Add them to the knowledge base.
2. Connect Discord. Use instant connect, or create your own application (see how to get a Discord bot token), enable Message Content and paste the token.
3. Choose channels and reply style. Threads in #support, mention-only in general chat.
4. Build the handover flow. Collect network and transaction hash, then hand over to staff.
5. Pin the rules. A short pinned message, built with the embed builder, saying what the bot answers and that staff never DM first.
6. Review the gaps. Check unanswered questions in the dashboard each week and update the docs before the next launch.

You can start free; see the Discord templates for ready-made flows.

Can the bot check a member's wallet or transaction?

No. Conferbot answers from your content and the conversation and does not read balances or blockchain data. It can explain where to look a transaction up and what common states mean, and for a specific stuck transfer it collects the network and transaction hash and hands the member to your staff.

Will the bot give investment advice or price predictions?

It should not, and you can make sure it does not. Add a clear rule to the knowledge base that price, buy or sell and yield questions are declined, with a pointer to your published risk disclosures. Financial promotion rules differ by country, so have your own counsel review what the bot may say.

How does an official bot help against DM scams?

It removes the wait that scammers exploit. Members get a correct public answer in a thread within seconds, every wallet-related answer repeats that staff never DM first and never need a seed phrase, and the real handover path is explained, so a stranger's DM stands out as fake.

Does it replace our verification or token-gating bot?

No. Conferbot does not verify wallets, gate roles, moderate or register slash commands. Keep your existing verification and moderation bots, and give the support bot its own channels and a narrow permission set. It only answers questions and hands conversations to your team.

Which Conferbot plan does a crypto community need?

The Discord channel, the AI answers from your knowledge base and handover to a person are available on every plan, including Free with 600 conversations. Native integrations, such as posting alerts to a staff channel or logging reports to a sheet, need the Pro plan or higher.

What if a member posts their seed phrase in the channel?

Treat it as compromised. The bot should tell the member to delete the message and move funds to a new wallet, and moderators should remove the message. Write that exact answer into the knowledge base so the bot responds the same way every time, and never ask for or store such data.