# The best Discord ticket bots

> The best Discord ticket bots, judged on transcripts, routing and volume. Ticket Tool is the configuration specialist; Tickets Bot and Vetox lead on free.

- Canonical: https://discordbots.blog/blog/best-discord-ticket-bots
- Published: 2026-08-26
- Author: The Field Guide desk
- Competitor facts checked: 2026-08-30
- Sources:
  - dyno.gg premium page (https://dyno.gg/premium) — checked 2026-08-30
  - Ticket Tool documentation (https://docs.tickettool.xyz/) — checked 2026-08-30
  - Tickets — documentation (https://docs.tickets.bot/) — checked 2026-08-30
  - Modmail documentation (https://docs.modmail.dev/) — checked 2026-08-30
- Publication: The Field Guide, an independent site not affiliated with Discord Inc.

---
Every ticket bot does the same visible thing: a member presses a button, a private channel opens,
staff answer, the channel closes.

The differences show up at volume — a hundred tickets a week rather than five — and they are
almost always in three places: **transcripts**, **routing**, and **what happens to tickets nobody
closes**. Judged on those three rather than on install count, Ticket Tool is the configuration specialist; Tickets Bot and Vetox give the most away free.

## The three things that actually differ

**Transcripts.** When a ticket closes, is there a permanent readable record, and who can see it?
A bot that deletes the channel and keeps nothing leaves you unable to answer "what did we tell this
member in March." A bot that emails or DMs the transcript to the opener changes the support
relationship entirely.

**Routing.** With one support queue, routing is irrelevant. With billing, technical and appeals as
separate concerns, you need panels that open different categories with different staff roles
attached — and ideally escalation from one to another.

**Abandonment.** Most tickets are not closed by anyone. The member gets their answer and leaves.
Without inactivity auto-close you accumulate hundreds of dead channels, and Discord's 500-channel
limit stops being theoretical.

Everything else — button colours, embed customisation — is presentation.

## Ticket Tool — the specialist

The deepest ticket implementation available: categories, advanced panel customisation, unlimited
free panels, a web dashboard, and years of refinement on ticket workflows specifically. If your
support volume genuinely justifies a dedicated tool — a storefront, a large game community, anything
with an SLA — this is the one to beat, and general bots do not beat it on depth.

Two things worth checking before you commit to it, on the exact criteria this article opened with.
**Claiming is a premium feature** — on the free tier, any staff member can answer any ticket, and a
volunteer team cannot divide the queue among themselves without paying for it. And **Ticket Tool
stores no transcript anywhere itself, on any tier**: the HTML record lives inside Discord's own CDN,
attached to the message that generated it, so deleting that message destroys the record permanently.
There is no retention setting because there is nothing the vendor is retaining.

It is also **tickets and nothing else**. No welcome messages, no reaction roles, no automod, no
levelling, no giveaways. Running it means running it alongside whatever handles the rest of your
server.

## Tickets Bot — generous free tier

Notable for what its free tier includes: unlimited tickets, a dashboard, forms, transcripts,
support teams and claiming. Premium at roughly **$2.99 per server per month** adds statistics,
autoclose, exit surveys and whitelabelling.

Autoclose being paid matters more than it sounds, given the abandonment problem above.

## ModMail — a different model entirely

[ModMail](https://docs.modmail.dev/) inverts the flow: a member DMs the bot, and the conversation appears as a thread in your
server. The member never sees a channel; staff never leave the server.

For appeals and private reports this is better than a channel-based system, because the member is
not looking at a channel list wondering who else can see it. It is AGPL-3.0 and self-hostable, with
hosted variants around **$30 one-time per server**.

Different tool for a different job — worth knowing it exists before assuming tickets means channels.

## Dyno — tickets inside the paid tier

[Dyno](https://dyno.gg/premium) includes Tickets in its Standard plan at **$4.17/month billed $49.99/year**. Levels sit in the
same tier.

That is the calculation to make: if you were going to pay Dyno for levelling anyway, tickets come
along; if tickets are the only thing you want from it, you are paying $49.99/year for a feature
several bots give away.

## Vetox — tickets on the free tier

The free tier includes **3 ticket panels, 200 concurrent tickets server-wide, and 100 blocked
users**, with 1 active ticket per member. **Claiming is free from Starter** — any volunteer team can
divide the queue among themselves without paying, the opposite of Ticket Tool's arrangement above.
Paid tiers raise panels to 10 and then 25, and lift the per-member cap to 5.

The features that address the three real differentiators — forms and modals, ratings, **inactivity
auto-close**, DM transcripts, staff stats, priority, escalation and linked panels — unlock at the
$4.99/month Basic tier. Business-hours scheduling, a staff discussion thread and response SLAs sit
at Max.

Three things stand out against the rest of this page. **200 concurrent tickets on a free tier** is
higher than most servers will ever reach, and it is free where [Dyno](/blog/vetox-vs-dyno) charges $49.99/year for a ticket
system at all. **Claiming costs nothing**, against a specialist that charges for exactly that — [the Vetox and
Ticket Tool comparison](/blog/vetox-vs-ticket-tool) covers what else that $7.99 buys. And the
operational features that actually decide whether a ticket system survives month six — forms,
ratings, inactivity auto-close, DM transcripts, staff stats, priority and escalation — arrive at
$4.99/month, roughly a tenth of Dyno's annual price for a comparable set.

The other difference is what surrounds it. [Ticket Tool](https://docs.tickettool.xyz/) is tickets and nothing else; Vetox's ticket
system sits alongside [moderation](/blog/vetox-moderation-stack), levelling, applications, logging and the rest on the same
configuration surface, so staff permissions, log routing and member history are shared rather than
scattered across three bots that do not know about each other.

## Choosing

| Situation                          | Choice                                                |
| ---------------------------------- | ----------------------------------------------------- |
| High volume, complex routing, SLAs | Ticket Tool                                           |
| Appeals and private reports        | ModMail                                               |
| Small server, want it free         | Tickets Bot or Vetox free tier                        |
| Already paying for a general bot   | Use its tickets before adding another                 |
| Need auto-close and transcripts    | Check that specific feature's tier — it is often paid |

The single most useful thing to check before committing: **open a ticket, close it, and see what
record survives.** That five-minute test tells you more than any feature table, including this one.