How to Set Up Modmail in Discord (DM-to-Staff Inbox) in 2026
To set up modmail in Discord, add a bot that turns member DMs into private staff threads: connect the bot, pick a staff inbox channel and support role, enable DM-to-staff routing, and every member DM opens a thread your team can reply to without revealing who is answering. PeakBot's ticket and support inbox handles this for free, so members message the bot privately and your staff reply from one organized inbox.
Modmail is the quiet workhorse of Discord support. It does not need a public help channel, a queue everyone can read, or a member feeling exposed asking a question in front of the whole community. They just DM the bot, and your staff see it in one place. This guide walks through exactly how to set that up in 2026, when modmail makes more sense than a public channel, and how it differs from a standard ticket system.
What modmail actually is (and how it differs from tickets)
Modmail is a DM-to-staff inbox. A member sends a direct message to your bot, and the bot relays that message into a private channel or thread that only your staff can see. When staff reply, the bot relays the reply back to the member's DMs. The member never leaves their DM window; staff never leave the server. It feels like a normal one-on-one conversation, but every message is logged on your side.
A ticket system is closely related but works in the opposite direction. With tickets, the member clicks a button inside your server, and the bot opens a private channel for that conversation right there in the guild. Tickets live inside the server; modmail lives in DMs. Both create a private, logged support thread your staff can manage. The practical difference is where the member starts the conversation and how visible the support entry point is.
If you want the full breakdown of the channel-based approach, our Discord ticket system setup guide covers panels, categories, and transcripts in detail.
When modmail fits better than a public support channel
Public support channels are easy to create and zero-config, but they have real downsides. Members hesitate to post sensitive issues in front of the whole community. Threads pile up and get lost. Other members chime in with wrong answers. Staff lose track of who is handling what.
Modmail solves all four:
- Privacy. A member reporting harassment, a payment problem, or a ban appeal does not want that visible to everyone. A DM-based inbox keeps it between them and staff.
- No noise. No bystanders, no off-topic replies, no "+1" spam clogging the conversation.
- One clean queue. Every conversation lands in the same staff inbox, so nothing falls through the cracks.
- A real record. Each modmail thread is logged, so you can review what was said even after the member closes their DMs.
Modmail is the better choice for appeals, reports, billing, partnership requests, and any community where members would rather not ask publicly. A public channel still works fine for low-stakes "how do I do X" questions where you want other members to learn from the answer.
Step 1: Add a bot that supports DM-to-staff routing
You do not need a separate, single-purpose modmail bot in 2026. A modern all-in-one bot can run your modmail inbox alongside moderation, leveling, and welcome messages, which means one bot to manage instead of five.
PeakBot is a free, AI-powered Discord bot that includes a full ticket and support inbox system at no cost, with no trial period. Invite it from peakbot.pro and authorize it on your server. During the invite, accept the permissions it requests — it needs Manage Channels, Manage Roles, Send Messages, Read Message History, and the ability to create threads so it can open and route support conversations.
If you would rather use a dedicated modmail-only bot, that is a valid path too. But every standalone bot you add is another login, another dashboard, and another point of failure. Folding modmail into a bot you already run for moderation keeps your stack simple.
Step 2: Create the staff inbox channel
Make a private channel where incoming member messages will land. A common naming convention is #modmail or #support-inbox.
Set the permissions so only staff can see it:
- Create a new text channel.
- Open the channel's permission settings.
- Deny View Channel for
@everyone. - Allow View Channel, Send Messages, and Read Message History for your staff role (more on that role in Step 4).
This channel is where the bot will post each new member conversation, either as a message or as a private thread. Keep it out of any category that members can browse.
Step 3: Enable the modmail inbox so members can DM the bot
Open your bot's dashboard and find the ticket or support settings. In PeakBot, head to the dashboard at peakbot.pro, select your server, and open the Tickets section. Turn on the support inbox and point it at the staff channel you created in Step 2.
Once enabled, the flow looks like this:
- A member sends a DM to the bot.
- The bot creates a new support conversation and posts it in your staff inbox.
- Staff reply inside that conversation.
- The bot relays the reply back to the member's DMs.
It is worth posting a short note in your server — in #info or #rules — telling members they can DM the bot for help. Members will not discover the feature on their own. One plain line works: "Need help or want to report something? DM @YourBot and a staff member will respond privately."
Step 4: Route replies into a private staff thread
The reason modmail scales is that each conversation gets its own private thread, so two staff are never typing over each other in the same wall of text.
Set a dedicated support staff role — for example @Support or @Mods — and grant that role access to the inbox channel. When a member opens a modmail conversation, the bot pings that role and opens a thread for the exchange. Staff reply inside the thread, and the bot handles relaying it back. Because each member gets a separate thread, your inbox stays readable even with a dozen conversations open at once.
This per-thread routing is the same private-channel logic that powers a button-based ticket panel. If you want to compare the two entry points side by side, our Discord ticket system setup guide shows the in-server button flow in full.
Step 5: Add categories, anonymity, and staff roles
Once the basic inbox works, a few settings make it noticeably better.
Categories
Let members pick what their message is about before it reaches staff: Report, Appeal, Billing, Partnership, General. Categories route the conversation to the right team and give staff instant context. In PeakBot, you set these up in the same Tickets section, and each category can carry its own staff role and its own intro message.
Anonymity
Decide whether staff replies show the individual staff member's name or just a generic "Staff" or "Support Team" label. Anonymous replies are useful for ban appeals and reports, where you do not want a specific moderator getting targeted or DMed later. Many servers keep replies anonymous by default and only reveal names when it helps.
Staff roles and permissions
Not every helper needs to see every conversation. You can scope categories so that, for instance, only your @Billing role sees billing threads, while general questions go to all of @Support. This keeps sensitive conversations limited to the people who should handle them.
Transcripts
Enable transcripts so each closed modmail conversation is saved. When a member claims they were told something, or you need to review a moderator's handling of a report, the transcript is your record. PeakBot generates transcripts for support conversations automatically.
Modmail vs tickets: which one should your server use?
They are not rivals so much as two doors into the same private-support room. Here is how to choose.
Use modmail when members are likely to want privacy from the start, when you do not want a visible "support" entry point cluttering the server, or when most contact is reports, appeals, and billing. The DM entry point feels lower-pressure, so shy members actually reach out.
Use a ticket panel when you want a clear, clickable "Open a ticket" button in a support channel, when members are already active in the server and comfortable starting there, or when you want categories presented as buttons. Tickets are more discoverable because the entry point is visible.
Use both if your server is large. Many communities run a public ticket panel for general help and keep modmail open as a private back channel for sensitive issues. Because PeakBot runs both from the same system, you are not adding a second bot to do it.
There is no wrong answer here — pick the entry point that matches how your members already behave.
Keeping support fast without a second standalone bot
The old way to run modmail was to add a separate bot that did nothing else. It worked, but it meant another bot in your member list, another permission set to audit, and another service that could go offline independently of everything else.
The cleaner approach in 2026 is to use one bot that already handles your other needs. PeakBot replaces MEE6, Carl-bot, Dyno, and TidyCord with a single bot, and its support inbox lives right alongside its other features:
- AI moderation that reads message intent and adapts per channel instead of matching a fixed keyword blocklist
- XP and leveling with message and voice activity, leaderboards, and role rewards
- Welcome messages with embeds, DMs, and auto-roles
- Unlimited reaction roles, giveaways, polls, starboard, invite tracking, and full logging
All of that is part of the 30+ features that are free with no time limit. PeakBot is currently powering 500+ Discord communities, and the support inbox is included for every server at no cost.
For most servers, the math is simple: if you are already running a bot for moderation and welcomes, turning on its modmail inbox is faster and cleaner than wiring up a separate one. You can read more about what is included on the features page or check PeakBot's pricing — modmail and tickets are in the free tier, and Pro ($8.25/month, or $69/year) adds the AI Server Builder and other extras if you want them.
FAQ
What is modmail in Discord?
Modmail is a system where members send a direct message to a bot, and the bot relays that message into a private staff inbox. Staff reply through the bot, and the response goes back to the member's DMs — creating a private, logged support conversation without a public channel.
What is the difference between modmail and a ticket system?
Modmail starts in the member's DMs and relays into a private staff thread. A ticket system starts inside the server, where the member clicks a button to open a private channel. Both create logged, private support conversations; they just differ in where the conversation begins and how visible the entry point is.
Do I need a separate bot just for modmail?
No. In 2026, all-in-one bots like PeakBot include a modmail-style support inbox alongside moderation, leveling, and welcomes, so you can run everything from one bot instead of adding a standalone modmail bot.
Can staff reply to modmail anonymously?
Yes. Most modmail setups let you choose whether staff replies show the individual moderator's name or a generic "Staff" label. Anonymous replies are common for ban appeals and reports, where you do not want a specific moderator getting targeted afterward.
Is modmail free in PeakBot?
Yes. The support and ticket inbox, including categories and transcripts, is part of PeakBot's 30+ free features with no time limit and no trial period. Pro pricing ($8.25/month, or $69/year) only adds extras like the AI Server Builder.
