No live feed of your server
A bot can ask Discord to send it every message as it’s posted, and many do. ModMailBot asks for none of it. It stays connected only so it shows as online.
The difference
Where the conversation goes
Most modmail bots
- Members send the bot a direct message (DM), and it reads every one.
- Staff replies are copied into the member’s DMs.
- The conversation is split between DMs and your server.
ModMailBot
- Members press a button to open a ticket. The bot never reads DMs.
- Staff reply in a private ticket channel.
- The whole conversation stays in your server.
Privacy by design
What we chose, and why
No copies of your messages
Some bots save a copy of every conversation for themselves. We never store what anyone writes in a ticket or a form. When a ticket is done, its saved copy goes to your staff-only archive channel, not to us.
No Administrator
Administrator lets a bot see and change everything in your server, and many bots ask for it. ModMailBot asks for six permissions and uses every one. It only gives itself access to the channels it sets up.
Only the right people see a ticket
Each ticket is its own channel, not a forum post that everyone in the forum can read. Only the member and the staff you choose can see it, and junior staff never see senior tickets.
Easy to leave
Remove the bot and your server’s data is deleted from our database after 30 days, or right away if you run /data delete first. Either way, you keep your ticket channels and saved chats. Our backups follow the 3-2-1 rule (three copies, two kinds of storage, one off-site), are encrypted, and are gone within 90 days.
Nothing hidden
We keep your settings and short records, like when each ticket opened and closed. The privacy policy lists it, and we name the companies that process it for us.
Good to know
Not the same as other bots called Modmail
Several Discord bots are called Modmail. ModMailBot is a different bot, and we run it for you, so there’s nothing to download or host.
Get started
Private support in five minutes
Add the bot, then run /setup.