Skip to content
Comparison8 min read

Discord Ticket Bot vs Modmail: Which Support Setup Fits Your Server?

Modmail relays DMs to your staff. A ticket bot opens a private channel. Here is how the two setups actually differ and which one fits your Discord server.

Published
Author
Dani, Founder, AI Ticket Bot

What is the actual difference?

Both setups solve the same problem, which is getting a member's question to the right people without cluttering a public channel. They solve it in opposite directions.

Modmail starts in the member's DMs. The member messages the bot directly, and the bot mirrors that conversation into a staff-only channel or thread. Staff reply through the bot, and the member sees those replies as DMs. The member never enters a support area of your server, because there is not one.

  1. Member DMs the bot
  2. Bot mirrors it to staff
  3. Staff reply through the bot
  4. Member sees a DM

A ticket bot starts inside your server. You publish a panel, which is a message with a button, in a channel of your choosing. A member clicks it and a private channel appears that only they, your staff and the bot can see. Everything happens in that channel until it closes.

  1. Member clicks a panel button
  2. Private channel opens
  3. Staff and member talk there
  4. Channel closes, transcript kept

That one structural difference produces every other difference below.

Which one is better for privacy?

Modmail, clearly, and it is not close for one specific case.

Because the conversation lives in the member's DMs, nobody in your server can tell that the member contacted staff at all. No channel appears. Nobody sees a name in a member list. For a report about another member, a harassment complaint, or a moderation appeal, that invisibility is the whole point. A member who has to click a visible button to report someone will often not click it.

A ticket bot creates a channel, and even though only the opener and staff can read it, its existence is a signal to anyone who can infer it.

Which one is better once more than one person is involved?

The ticket bot, and this is where the gap is widest.

A ticket channel is a place. Staff can be added to it, a claim can be taken so two people do not answer at once, a priority can be set, and the whole thing has a beginning and an end. A DM relay has none of that structure by default, because a DM thread is a line, not a room.

Ticket channel

  • Several staff work the same request
  • Claiming stops duplicate replies
  • Categories route the request at the start
  • Closing produces a transcript
  • Panels put support where members already are

DM relay

  • One relayed thread, harder to hand over
  • No natural claim step
  • Everything arrives in one place
  • History lives wherever the bot logged it
  • Member must know to DM the bot

The entry point matters more than it sounds. A panel button sits in a channel a member is already looking at. Sending a DM to a bot is something a member has to already know your server does, which in practice means the quiet ones never do it.

What does a ticket bot actually do that Modmail does not?

Three things, in rough order of how much they change a week of staff work.

  1. 01

    Answer the repeat questions before a human reads them

    An AI layer that knows your server can handle the questions that arrive twenty times a month.

  2. 02

    Keep the record after the channel is gone

    A transcript survives the channel deletion, so a decision made in March is still readable in July.

  3. 03

    Show you what support actually costs you

    Ticket volume, which categories dominate, and who is carrying the load.

The first one is the reason most servers move. Across this bot's lifetime, more than 180,000 tickets have been handled, and about half of them closed with no human involved at all. Those are not hard tickets. They are the same handful of questions, asked by different people, forever.

How does the AI part work?

It is worth being precise, because "has AI" means very little on its own.

Per-server brain
Knowledge taught to one server, never shared with another
Deflection
A member's question answered with no staff involvement at any point
Escalation
The AI handing the ticket to a human because the next step needs one

Your staff teach the bot facts about your server. On the next ticket, it uses them. When the answer needs a person, it says so and pings the one staff role you wired, rather than everyone.

  1. member

    how do I get the supporter role?

  2. bot

    Supporter roles are assigned in #shop right after purchase. If it has been more than an hour since you bought, say so here and I will bring in the team.

  3. member

    bought it yesterday, still nothing

  4. bot

    Bringing in the team now.

  5. staff

    Maya here, checking your purchase.

Replies land in seconds. Messages are processed by our own AI platform (Nexus) and Anthropic's model API. Nothing is sent to other AI providers, and brain state stays on our infrastructure.

What does Modmail do better?

A fair comparison has to include this section, so here it is.

Modmail is free to self host, and free is not a trial. If you are running a server of a few hundred members with a handful of messages a week, a subscription is hard to justify and a relay is genuinely the right tool.

It is also simpler in a way that matters. There is one concept to explain to staff: a DM arrives, you answer it. No panels, no categories, no permissions matrix to design. Servers that tried to run a full ticket setup and abandoned it usually abandoned it at the configuration step.

And because it is open source, you can change it. If you have someone who can host and edit a bot, nothing about your support flow is anyone else's decision.

Stay on Modmail if

  • Most contact is private, such as appeals or reports
  • You get a handful of messages a week
  • You have someone who can host and maintain it
  • Paying anything at all is the blocker

Move to a ticket bot if

  • The same questions keep arriving and staff keep retyping answers
  • More than two or three people share support duty
  • You need the history after the conversation ends
  • Members are not finding support because they do not know to DM

Can you run both?

Yes, and it is the setup we would suggest for a moderation-heavy community.

The two use different entry points, so they do not fight. Point Modmail at the things that should stay invisible, which usually means appeals and reports about other members. Point ticket panels at everything else, which usually means support, purchases, bugs and questions. Members get the private route when they need it and the fast route when they do not.

If you would rather not run two bots, there is a middle path. Our AI can be attached to a ticket channel created by a different bot entirely, so an existing setup keeps its own open and close flow and only gains the answering layer.

How do you switch, if you decide to?

  1. 01

    Write down what you have

    Which channels Modmail uses, which roles can see them, and any history you want to keep.

  2. 02

    Archive the old history

    Nothing migrates between the two systems. Export before you remove anything.

  3. 03

    Add the new bot and build one panel

    One panel and two or three categories. Resist configuring everything on day one.

  4. 04

    Teach it your ten most common answers

    The refund window, where roles come from, how to report a bug. This is the step that does the work.

  5. 05

    Run both for a week

    Leave Modmail on. Watch which route members actually pick.

  6. 06

    Turn the old one off

    Only once the new route is carrying real traffic.

What does it cost?

Modmail self hosted costs you a small server bill and your own maintenance time. That is the honest floor, and for a small community it is hard to beat.

A ticket bot costs a subscription, except that ours has a genuinely free plan with the same AI on a smaller monthly budget, so the comparison can be made without paying anything. When the AI budget runs out it stops cleanly and tickets keep working manually. There is no overage bill.

Prices and limits render live from the catalog, so that page is always current in a way this paragraph cannot be.

See what the plans include

So which one should you pick?

If your support is mostly private matters and mostly low volume, stay on Modmail. It is a good tool and it is free.

If your staff are retyping the same answers, if more than a couple of people share the load, or if you need to know what happened three months later, the structure of a ticket channel starts paying for itself. And once you have that structure, the AI layer on top of it is what turns half of the volume into something nobody has to read.

Frequently asked questions

Is Modmail free?
The well known Modmail projects are open source and free to run, which is a real advantage. You supply the hosting, the uptime and the updates yourself, so the cost moves from a subscription to your own time and a small server bill. Check the specific project you are running, since hosted versions of the same idea do exist and those may charge.
Does Modmail have AI built in?
The Modmail pattern is a relay: it forwards a member DM to your staff and forwards the reply back. There is no AI layer in that pattern by default. Some forks and hosted variants add one, so check the project you actually run rather than assuming either way.
Can I run Modmail and a ticket bot at the same time?
Yes, and for a lot of servers that is the right answer. Keep Modmail for private contact such as moderation appeals and reports about other members, and use ticket panels for everything else. They use different entry points, so they do not conflict.
What happens to my old Modmail history if I switch?
It stays wherever Modmail put it, usually in the staff channels or threads it created. Nothing migrates automatically between the two systems. Export or archive anything you need before you turn the old bot off, because a bot removal is not reversible.
Which is better for a small server?
If you get a handful of messages a week and they are mostly private matters, Modmail is genuinely simpler and costs nothing to run. The case for a ticket bot gets stronger as volume rises, as more staff get involved, and as the same questions start repeating.
Do members need to know a command to open a ticket?
No. A ticket bot posts a panel with a button in a channel you choose, so opening a ticket is one click. Modmail starts with the member sending a direct message to the bot, which means they need to know that is how your server works.

See it on your own server.

Add AI Ticket Bot free, teach the brain a few of your most common answers, and watch it clear the repetitive tickets on its own.

Keep reading