Verify message isn’t from my custom bot
You set up your verify embed, clicked Send Message, and the Discord message shows VaultCord, a shared bot, or a webhook—not the custom bot you expected.
That’s usually normal based on how the message was sent and which bot is linked to your VaultCord server.
Why this happens
There are three common cases:
1. You’re using a shared / premade VaultCord bot
If the server isn’t on your own Discord application (custom bot), the verify message is posted by VaultCord’s shared bot. It will not use a name/avatar you made in the Discord Developer Portal.
2. The message was sent with a webhook
If Discord asked you to authorize a webhook (or you accepted the webhook step after a send failure), Discord posts the verify message as a webhook.
Webhooks often look different from a normal bot message (name/avatar/badge can look “not like my bot”), even when the webhook is tied to your bot app.
3. Your custom bot isn’t invited or can’t post in that channel
If the custom bot isn’t in the server, or is missing channel permissions, VaultCord may fall back to the webhook flow—or the send fails until permissions are fixed. Existing help: How to fix “Missing Permissions”.
What you want vs what Discord shows
Goal | What you need |
Message shows your bot name/avatar | Your custom bot linked on VaultCord, invited to the Discord server, with send permissions, then Send Message as that bot |
Message was sent via webhook | Can still work for verify; appearance is webhook-style, not identical to a normal bot chat message |
Still on a shared VaultCord bot | Message will show that shared bot, not a custom one you created |
The verify button / link can still work even if the poster name isn’t the brand you wanted. Branding is separate from verification working.
How to send the verify message as your custom bot
In VaultCord, open Bots and make sure you created/added your own Discord bot (not only a shared one).
Open Servers → your community → confirm that server is using your custom bot.
Invite that bot into your Discord server.
In the verify channel, give the bot at least:
View Channel
Send Messages
Manage Channel (as noted in the Missing Permissions guide)
In VaultCord, open your verify message / embed editor.
Select the correct channel.
Click Send Message.
If Discord opens an authorize window for a webhook, that’s the webhook method—expect webhook-style appearance unless you successfully send as the bot itself.
If it still shows the wrong name
Confirm in VaultCord which bot is attached to that server.
In Discord → Server Settings → Integrations / Webhooks, see if a webhook posted the message; you can edit that webhook’s name and avatar to match your brand.
Delete the old verify message and send again after the custom bot has permissions.
Don’t mix channels: send into the channel where members should verify.
Reload channels in the editor if a new channel doesn’t appear.
Does verification still work?
Usually yes. Members use the verify button/link. Wrong bot name on the embed is a branding issue, not always a broken verify setup.
If clicks fail, fix server Discord settings / verified role—see “Discord server isn’t setup correctly”.
Also avoid risky wording in the embed (termination/pull language)—see Secure your Discord Bot.
Still need help?
Chat icon (bottom right) on https://help.vaultcord.com/ and tell us:
You want the verify message from your custom bot
Screenshot of the Discord message (name/avatar)
Whether you use a custom bot or a shared VaultCord bot
Your server name in the dashboard