Pick Tickets v2 if you want the cheapest paid tier. Its site, tickets.bot, lists a free plan with 3 panels and a $2.99/month Premium that removes the panel limit. Pick Ticket Tool if you already know it and don't mind paying $8/month or $66/year per server, because claiming tickets is a Premium feature there. If free transcripts and resolution stats matter more to you, PeakBot is a third option.
Checked on each bot's own site or docs on November 3, 2026. We make PeakBot. Nobody paid to be in this post.
First: what "Tickets v2" means if you used the old Tickets bot
A lot of people searching this used the original Tickets bot and want to know where to go next. Today, tickets.bot points to Tickets v2. It is a separate bot, so you have to invite it to your server yourself. Some older comparison posts still list "Ticketsbot" with setup steps for the earlier bot. Skip those steps and follow the current docs on tickets.bot.
Whatever you move to, ticket history does not move from one bot to another by itself. Before you remove any ticket bot, export the transcripts you need to keep, and close or hand off any open tickets. That goes for Ticket Tool to Tickets v2, the other way round, or a move to something else.
How we chose
We compared the two bots on the things a support team uses every day:
- Free plan limits on the core flow: panels, claiming, closing and transcripts.
- Paid plan price, per server.
- Forms: questions a member answers before the ticket opens.
- Staff reporting: whether you can see open, claimed and resolved tickets.
We only print a limit or price when it appears on the bot's own site. Where the table says "see site", the bot doesn't publish a figure we could confirm, so read its current docs before you decide.
Panel setup
Setup follows the same pattern on every ticket bot:
- Invite the bot from its own site and give it permission to create and manage channels.
- Choose the category where new ticket channels go.
- Set your support roles so they can see new tickets.
- Build a panel: a message with a button or dropdown that members click to open a ticket.
- Post the panel in a channel members can see, then open a test ticket from an account that has no staff roles.
For Ticket Tool, our step-by-step Ticket Tool setup guide walks through its dashboard. If you're new to tickets in general, How to Set Up a Discord Ticket System covers categories and permissions in more detail.
On Tickets v2, the free plan's 3-panel limit is the number to plan around. Three panels cover something like "Support", "Reports" and "Appeals". If you want a separate panel for each game, product or language, you'll hit the limit, and the $2.99/month Premium removes it.
Forms before a ticket opens
Pre-ticket forms let staff see the problem before they say hello. Any bot that shows a pop-up form in Discord uses Discord's modal system, so they all share the same ceilings. Discord's component reference lists them:
- A question label can be up to 45 characters, and its description up to 100.
- A text answer can be up to 4000 characters, and its placeholder up to 100.
- A dropdown (string select) holds at most 25 options.
- Modals can now include user, role, mentionable and channel selects, file upload, radio groups, checkboxes and text display, not just text boxes.
If an older guide says forms are limited to five text boxes and nothing else, it's out of date. Which of these question types a bot actually offers is up to the bot, so check tickettool.xyz and tickets.bot to see what each one supports on its free plan.
Claim and close flow
Claiming means one staff member takes a ticket so two people don't answer the same member. On Ticket Tool, claiming is Premium, so on the free plan your team has to coordinate some other way, such as a staff channel. Tickets v2 doesn't list a claiming limit among the figures we could confirm, so check its docs.
For closing, look at three things on each bot: who can close a ticket (staff only, or the member too), whether a transcript is saved when it closes, and whether inactive tickets can close themselves. Those three settings decide how much tidying up your staff do by hand.
The picks
1. Tickets v2
Pick Tickets v2 if: you want a dedicated ticket bot, three panels cover your needs, and you'd like the cheapest upgrade if you outgrow them.
At $2.99/month, its Premium is the lowest monthly price of the three bots here. It's also the natural next step for former Tickets users. Read the export notes on tickets.bot before you assume any old data carries over.
2. Ticket Tool
Pick Ticket Tool if: your staff already know it, you're happy with a single-purpose ticket bot, and $8/month or $66/year per server is fine once you need claiming.
Everything in Ticket Tool is built around tickets, and plenty of setup guides cover it. The main downside is that claiming, a basic team habit, sits behind Premium. If that's what is pushing you away, our free Ticket Tool alternatives post covers more options. See tickettool.xyz for its current plans.
3. PeakBot
Pick PeakBot if: you want tickets with free transcripts and resolution stats, and you'd rather run tickets, verification and moderation from one dashboard.
PeakBot's Tickets page in the dashboard sidebar sets up either private-channel tickets or form submissions:
- Forms: form submissions are a ticket type of their own, so a member can send in an application or a report without a whole private channel being opened for it.
- Ticket types and roles: you can create custom ticket types and choose which support roles handle them.
- Resolution stats: the stats show open tickets, claimed tickets and average resolution time, so you can tell whether your staff are keeping up.
Transcripts are free. Auto-close needs a paid plan. The cheapest is Starter at $5.75/month, or $48/year, per server. The Free plan has no time limit and doesn't expire. Full details are on the Tickets wiki page.
What the others do better: Tickets v2's Premium costs less per month than PeakBot's cheapest paid plan. Ticket Tool and Tickets v2 are dedicated ticket bots, so every setting is about tickets. PeakBot covers much more than tickets. That helps if you want one bot, and it's extra clutter if tickets are all you need.
Comparison table
| Tickets v2 | Ticket Tool | PeakBot | |
|---|---|---|---|
| Free panels | 3 | See site | See wiki |
| Claiming | See site | Premium | Claimed tickets shown in stats |
| Transcripts | See site | See site | Free |
| Pre-ticket forms | See site | See site | Form submissions as a ticket type |
| Resolution stats | See site | See site | Open, claimed, average resolution time |
| Auto-close | See site | See site | Paid plan |
| Paid price (per server) | $2.99/month | $8/month or $66/year | Starter $5.75/month or $48/year |
To see how these compare with Tickety, Helper.gg and others, read Best Discord Ticket Bots in 2026.
Frequently Asked Questions
Is the original Tickets bot still something I can add?
Use Tickets v2, which tickets.bot links to now. If a comparison post lists "Ticketsbot" with a ticketsbot.net link, it is describing the earlier bot, so don't follow its setup steps.
Can I move my old ticket transcripts to Tickets v2 or Ticket Tool?
Ticket history doesn't move between different bots by itself. Export the transcripts you need before you remove a bot. Check tickets.bot for what it can bring over from the earlier Tickets bot, and plan on open tickets being closed or reopened by hand.
Does Ticket Tool have forms before a ticket opens?
Check tickettool.xyz to see which question types it supports on each plan. Whatever it offers, Discord's own limits still apply: labels up to 45 characters, answers up to 4000 characters, and dropdowns with at most 25 options.
Which ticket bot lets staff claim tickets for free?
On Ticket Tool, claiming is Premium. PeakBot shows claimed tickets in its free Tickets stats, next to open tickets and average resolution time. For Tickets v2, check its docs, since we couldn't confirm a claiming limit on its site.
Can tickets be private threads instead of channels?
That depends on the bot. PeakBot creates private-channel tickets or form submissions. For Ticket Tool and Tickets v2, check their docs for a thread option. Threads keep your channel list shorter, and channels give you more control over permissions.
Can I run two ticket bots while I switch?
Yes, as long as each bot has its own panel and its own ticket category, so members and staff can tell which bot a ticket belongs to. Once the old bot's open tickets are closed and its transcripts are exported, delete its panel so nobody opens new tickets there, then remove the bot.
