The bot cannot read messages
A privileged intent was never enabled in the developer portal, or the bot was never verified for it, so MESSAGE_CONTENT is empty and every command handler sees a blank string.
Intents approved and enabled
Running on Discord?
Discord bots look trivial until a gateway disconnect eats twelve hours of commands, an intent toggle hides the messages you were building the whole feature around, or Cloudflare starts rate-limiting your webhook. We rebuild the bot, the privileged intents, and the moderation setup so the server runs the way a business needs it to.
What it is
Discord is a hybrid chat and voice platform that started as a gamer communication tool in 2015 and has grown into a general purpose community platform. Businesses now use it for user communities, developer relations, paid cohorts, support channels, and internal team chat for engineering groups.
The developer surface is a mix of a gateway WebSocket for realtime events, a REST API for reads and writes, slash commands with interaction tokens, webhooks for inbound posting, and OAuth2 for identity. Bots run against privileged intents that Discord gatekeeps once a bot passes a verification threshold, and larger bots have to shard across multiple WebSocket connections.
The honest version
No technology is all upside. This is where Discord earns its place and where it tends to cause trouble.
Sound familiar?
The Discord problems that bring people to us, and what you have once each one is fixed.
A privileged intent was never enabled in the developer portal, or the bot was never verified for it, so MESSAGE_CONTENT is empty and every command handler sees a blank string.
Intents approved and enabled
A command that calls a slow API without deferring first. Discord gives three seconds to acknowledge, and after that the interaction token is useless.
Deferred responses, no more timeouts
A loop over channels or members that fires requests without respecting the per-route and global limits, triggering 429s and then a Cloudflare 1015 ban on the webhook host.
Requests paced within limits
Channel overrides deny Send Messages or Manage Messages on exactly the channels the bot needs, usually after a role refactor nobody told the bot about.
Role and override model cleaned up
Missed heartbeats on a flaky host, a library version behind the current protocol, or sharding set up wrong so one shard carries all the traffic.
Stable gateway, healthy shards
A wave of newly-created accounts posting invite links and slurs, often during a public launch when staff coverage is thin.
AutoMod rules and raid defenses in place
Choices with the wrong value type, a nested option schema that does not match Discord's rules, or a command name that collides with an existing one.
Command tree registers cleanly
A script posting too fast to a Discord webhook, which triggers a Cloudflare rate limit against your source IP that affects every webhook you own.
Posting paced, ban lifted
What we do
Call us for one failing slash command, or hand us the whole bot and server setup.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Because MESSAGE_CONTENT is now a privileged intent. You have to enable it in the developer portal and, for bots in more than a hundred servers, get verified by Discord before they will send that data to your gateway. A newly deployed bot that worked fine in staging but sees empty messages in production is almost always missing that approval.
Call deferReply or deferUpdate immediately, then do the work, then editReply when you are done. Any slash command that touches a slow backend needs this pattern. The three-second clock starts the instant the interaction hits your service, not when you start processing it, so the defer has to be the first thing the handler does.
Yes. We configure AutoMod rules, verification gates, slowmode on public channels and a moderation bot with raid detection, then review the role and overwrite model so a single compromised account cannot post site-wide. For ongoing coverage we also set up on-call alerts to your staff when message rate spikes.
Sometimes, with caveats. Discord is excellent for synchronous community and voice, weaker for searchable long-form knowledge. If the content is meant to live forever and show up in search engines, you probably want a forum or docs site alongside Discord, not instead of it.
Usually a fan-out loop that posts to many channels at once, or a reaction-role setup that reacts faster than the per-route limit. The fix is to queue outbound requests, honor the retry_after header, and shard the work so no one route is hammered.
Estimates are on the house. Describe which bot or community issue you are seeing and we send a fixed price before work begins.
Free estimate
Tell us what the bot or community is doing wrong and we reply with a scoped plan and a price.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: