Skip to content
20% off + 25% more tokensSee prices

BlogGuides

Discord Modmail Bot: How to Use It, and How to Add AI

A Discord modmail bot turns a member's DM into a private staff channel. How members and staff use it, anonymous replies, and how to let AI answer modmail.

Dani, Founder, AI Ticket Bot

7 min read

Modmail is the quiet way to reach a server's staff: no button, no ticket channel for anyone to notice, just a DM. Below is how members and staff use it, and what changed in October 2026 for servers that want AI answers.

What is a modmail bot on Discord?

A bot that turns a member's direct message into a conversation with your staff. The member writes to the bot, and the bot carries messages both ways.

  1. Member DMs the bot
  2. Bot opens a staff channel
  3. Staff reply through the bot
  4. Member gets the reply as a DM

That is why modmail is popular for reports and appeals: nobody can see that a member got in touch. A Discord ticket bot works the other way round, with a button that opens a private channel the member is part of.

How do you use modmail as a member?

Send the bot a direct message. Everything else happens in that DM.

  1. Find the modmail bot

    Servers usually name it in the rules or info channel

  2. Send it a direct message

    Click its name and press Message. Put what happened, names and screenshots in your first message

  3. Pick the server, if asked

    A bot you share several servers with may ask which one the message is for

  4. Keep your DMs open

    Staff replies arrive as DMs from the bot, so it must be allowed to message you

  5. Reply in the same DM

    Everything you send goes to the same conversation until staff close it

If replies never arrive, check your privacy settings: a bot cannot message someone who turned off DMs from server members. Cannot send messages to this user shows how to turn them back on.

How do staff answer modmail?

In the channel the bot opens, with its commands. Each new conversation gets its own channel, or a thread on some bots, in a category only staff can see. The member's messages appear there, usually with their name and avatar.

Names change from bot to bot, and not every bot has all of them, but these are the usual jobs:

The usual modmail bot commands

Reply
Sends your message to the member as a DM
Anonymous reply
The same, with your name hidden
Note
A comment only staff can read
Saved reply
Sends a prepared answer to a common question
Close
Ends the conversation, often after a short delay, and keeps a log
Contact
Starts a conversation with a member who has not written in
Block
Stops one person from opening new conversations

On many modmail bots, a message typed without a command stays between staff. Handy for discussing a case, and an easy way to forget to send the answer. Read the help command before your first shift.

Many modmail bots also offer a web page for closed conversations, often called a log viewer or dashboard. The history lives there, since the channel is usually removed at close.

Can modmail replies be anonymous?

Yes, from staff to member. Not the other way. An anonymous reply reaches the member under a team label instead of a moderator's name. That helps when the answer is a warning or a refusal, and one moderator should not carry it alone.

The member is not hidden from staff on a normal modmail bot. The channel shows who wrote, because staff need to know who they are answering.

Ticket panels can do the same. In AI Ticket Bot, /ticket reply posts a message as "Staff". Anonymous staff replies covers where the name is hidden and where your team still sees it.

When is modmail better than a ticket panel?

When the conversation is private and rare. A panel wins once several people share the work.

Modmail fits when

  • The matter is private, like a report or an appeal
  • A few messages arrive each week
  • Nobody should see that a member asked
  • Your members already know to DM the bot

A ticket panel fits when

  • Several staff work the same request
  • The same questions arrive every day
  • You want a transcript and stats afterwards
  • Members need a button to find support

Plenty of servers run both: modmail for reports, a panel for everything else. The full side by side is in ticket bot vs modmail.

What makes a good modmail bot?

There is no single best one, so check these before you pick.

What to check in a modmail bot

  • Who keeps it online: you, if you host it, or its makers, if they do
  • Anonymous replies, for answers that should come from the team
  • Saved replies, for the questions that repeat
  • Logs you can read after a conversation closes
  • Blocking, so one person cannot flood your staff
  • For AI answers: a channel per conversation, and forwarding of other bots' messages

Most modmail bots are free to start. Open source ones cost a small server and someone to keep them updated. Hosted ones save that work, and some charge for extras. Adding our AI is free too: /ticket connect works on every plan, Free included, within a smaller AI budget. Pricing has the figures.

Can an AI answer modmail?

Yes. If you already run a modmail bot, AI Ticket Bot can answer the member's messages in the modmail channel. Since the October 2026 release, /ticket connect recognises a modmail bot on its own. There is nothing to switch on.

  1. Member DMs your modmail bot
  2. It posts the message in a staff channel
  3. Our AI answers in that channel
  4. Your modmail bot forwards the answer
  1. Add AI Ticket Bot

    Give it the View Audit Log permission, so it can tell which bot made a channel

  2. Connect your modmail bot

    Run /ticket connect and pick it, or add it under Settings, Other bots on the dashboard. You need Manage Server

  3. Let it into the modmail channels

    It tries to add itself to each new one. If it cannot, a DM tells you what to grant

  4. Set a ping role

    The role pinged when the AI hands a conversation to a person

  5. Teach it your answers

    Same AI, same training as your own tickets

Every new conversation your modmail bot opens is then picked up. The AI reads what the member wrote, embeds included, and answers in seconds. Anyone who types in the channel counts as staff, and by default the AI goes quiet once one of them writes, as in a ticket. That is the Pause when your team steps in switch.

/ticket connect lists each connected bot with its status: working, cannot see its tickets, or modmail. Per bot you set the ping role and categories to ignore, or disconnect it. You get one DM when the first conversation is picked up, with a button to ignore its category if it is not support, and one more if modmail shows up later or the AI cannot see that bot's channels.

What does the member see when the AI answers?

Only what your modmail bot sends them. Check this before anything else.

Modmail bots often forward only replies sent with their reply command. Then the AI's answer stays in the staff channel, where staff can read it and the member cannot. Look for a setting that forwards other bots' messages, or ask the bot's makers.

What the AI cannot do in modmail

The honest list.

Good fit

  • Answers the member's messages in seconds
  • Recognises a modmail bot by itself
  • Works on every plan, including Free

Not the right call

  • The member sees the answer only if your modmail bot forwards bot messages
  • No transcript and no staff stats from us for these conversations
  • Closing stays with your modmail bot
  • Needs View Audit Log and access to the modmail channels
  • A hand-off pings only the role set for that bot, and nobody if none is set
  • Modmail that runs in threads, or posts members' messages through a webhook, is not picked up

We store no messages from these conversations, so your modmail bot's logs stay the record. Answers use your server's AI budget, the same as your own tickets.

Two smaller gaps: conversations already open when you connect are not picked up, and an automatic notice your modmail bot posts, such as a closing countdown, can be read as the member's words.

Frequently asked questions

Send the bot a direct message. A modmail bot posts what you write in a private channel only staff can see, and staff replies come back to you as direct messages from the bot. Keep direct messages from server members switched on in your privacy settings, or the replies cannot reach you.

The names differ between bots, but the usual jobs are the same: reply, reply anonymously, leave a note only staff can read, send a saved reply, close the conversation, start a conversation with a member, and block someone. On many modmail bots a message typed in the channel without a command stays between staff. The bot's help command lists its own names.

On many modmail bots, yes. An anonymous reply reaches the member under a team label instead of the moderator's name. It works one way only: the member is not hidden from staff, because the channel shows who wrote.

Yes. Most modmail bots are free to start. Open source ones cost only the server you host them on and the time to keep them updated, and hosted ones save that work, with some charging for extras. Adding AI Ticket Bot's AI to a modmail bot is free too: /ticket connect works on every plan, including Free, within that plan's smaller AI budget.

Yes. Add AI Ticket Bot, give it the View Audit Log permission, and run /ticket connect on your modmail bot. It recognises a modmail bot on its own, reads the messages that bot posts for the member, and answers in the modmail channel from what your staff taught it. Closing and logs stay with your modmail bot.

Because your modmail bot only sends the member what it is set to send, and modmail bots often forward only the replies staff send with their reply command. Look for a setting that forwards messages from other bots, or ask its makers. Until then the AI's answer stays in the staff channel, where your staff can still read it.

See it on your own server.

Add the bot free, teach it a few of your most common answers, and watch it clear the repeat tickets on its own.

Free plan, no card. Premium is free for 14 days once your tickets are live.