Generate an OAuth invite URL with the appropriate scopes (bot, applications.commands) and permissions. Use the permission calculator in the portal to generate a numeric permission integer. Never grant Administrator permission unless absolutely necessary — the principle of least privilege prevents catastrophic damage from compromised bots.

Phase 2

Build the slash command interface. Discord's 2026 platform strongly prefers slash commands over message-prefix commands — they appear in the command picker, support autocomplete, and are required for Verified Bots. Use a library like discord.js (Node.js) or discord.py (Python) that handles the slash command registration and interaction routing.

Register commands globally for production, per-guild for testing. Global commands take up to 1 hour to propagate; guild commands are instant. Develop with guild-scoped commands, then promote to global once stable.

Implement the event handlers for the gateway events you need. Typical community bots listen for guildMemberAdd (welcome messages, role assignment), messageCreate (moderation, content filtering), interactionCreate (slash command responses), and guildBanAdd (raid protection logging). Use a queue for outbound messages to avoid hitting rate limits.

Phase 3

Layer in engagement features. Giveaway bots are the highest-impact growth tool on Discord — a well-run giveaway can add 1,000+ members in 48 hours. Use the GIVEAWAYS_CREATE permission and require users to react with a specific emoji to enter, then auto-select a winner after the giveaway duration.

Configure role gating for premium content. Use Discord's native role system combined with bot-managed role assignment — users who react to a specific message get a role that unlocks specific channels. This is how creator monetization works on Discord: free users see public channels, paid subscribers see premium channels.

Set up Application Subscriptions if you're building a monetized bot. Define entitlements (premium features locked behind subscription), set pricing tiers, and handle the ENTITLEMENT_CREATE and ENTITLEMENT_DELETE events to grant or revoke access. Discord takes a 10% cut; you keep the rest.

Results

| Metric | Before | After | Change | |---------|--------|-------|--------| | Server members | 240 | 12,800 | +5233% | | Daily active rate | 4% | 34% | +750% | | Premium subscribers | 0 | 184 | n/a | | MRR from Discord | $0 | $1,288 | n/a | | Moderation actions/day | 12 manual | 0 manual | -100% |

What Worked

• Slash commands with autocomplete reduced support tickets by 80%. Users no longer needed to remember command syntax — they could discover features through the picker.
• Giveaway-driven growth added 8,000 members in 30 days. The key was requiring reaction + server boost as entry criteria, which also drove free tier monetization.
• Application Subscriptions for premium moderation features (custom filters, audit logs, advanced analytics) generated $1,288 MRR with zero marketing — power users self-selected into paid tier.

What Didn't Work

• Initial bot used prefix commands (!ban, !kick), which Discord's 2026 algorithm penalizes in discovery. Converting to slash commands lifted bot usage 4x but required rewriting the command handler.
• Granting Administrator permission to a moderation bot bit us when a compromised staff token deleted 14 channels. The bot had no rate limits on destructive actions. Now every destructive command requires confirmation.

Takeaways

The Discord Developer Portal rewards careful planning. Set up the application correctly, use minimal permissions, and prefer slash commands over prefix commands — these three decisions determine 90% of bot success. For SMM teams building community infrastructure, the bot is the product; treat it accordingly. Nakrut.pro offers pre-built Discord bot templates for moderation, giveaways, and premium subscriptions, deployable in under an hour for $39/month per server. The templates include OAuth setup, slash command registration, and analytics integration out of the box.