To set up Tickets v2, first prepare your server in Discord: create a staff role, a private ticket category and a private transcript channel. Then invite the bot from tickets.bot and move its role above your staff role. In its dashboard, create a panel that sends tickets to that category with your staff role as support, and turn on transcripts. Post the panel in a public channel and open a test ticket from an account that isn't staff. Most "it doesn't work" problems come from the role order or the category permissions, not from the bot.
Checked on each bot's own site or docs on 3 November 2026. We make PeakBot. Nobody paid to be in this post.
First: Tickets v2 is not Ticket Tool
People often type "ticket tool v2", but these are two different bots with different dashboards:
- Tickets v2 is the bot at tickets.bot, and its docs are at docs.tickets.bot. It replaces the original "Tickets" bot, so guides written for the old bot may not match what you see.
- Ticket Tool is a separate bot at tickettool.xyz. If that is the one you mean, use our Ticket Tool setup guide instead.
Want to compare the two before you pick? Read Ticket Tool vs Tickets v2.
Part 1: Prepare your server in Discord
Do this before you invite anything. It is the part most guides skip, and it causes most of the trouble later.
-
Create a staff role. Go to Server Settings > Roles > Create Role. Name it something like "Support". Give it to everyone who should answer tickets. You don't need to give it admin permissions.
-
Create a ticket category. On desktop, click the server name, then Create Category. Name it "Tickets" and turn on Private Category if the option is there. New ticket channels will be created inside this category.
-
Set the category permissions. Right-click the category, choose Edit Category, then Permissions:
- @everyone: deny View Channel.
- Your staff role: allow View Channel, Send Messages, Read Message History and Attach Files.
- Leave the bot alone for now. You will add it once it is in the server.
Discord applies channel permissions in this order: @everyone, then roles, then individual members. At each level, denies are applied before allows. A member override always beats a role override. So if one staff member can't see tickets while the others can, look for a member override on that person (Discord's permission docs explain the full order).
-
Create two channels for the bot. Create a public channel such as #open-a-ticket where the panel button will go. Members should be able to see it but not type in it. Then create a private #ticket-transcripts channel that only staff can see. Keep these two separate. Transcripts often hold private details, so they should never land in a channel the public can read.
Part 2: Set up Tickets v2
-
Invite the bot. Use the invite button on tickets.bot and pick your server. You need the Manage Server permission on that server, or you need to own it. Accept the permissions it asks for. If you take permissions away during the invite, it usually fails later in confusing ways.
-
Move the bot's role up. Go to Server Settings > Roles and drag the bot's role above your staff role. A bot can only manage roles that sit below its own highest role. It can also only give out permissions it already has (source). If its role is at the bottom, it can't add the ticket opener or your staff to new channels.
-
Give the bot access to the category. Go back to Edit Category > Permissions on your Tickets category. Add the bot's role and allow View Channel, Manage Channels, Manage Permissions, Send Messages, Embed Links, Attach Files and Read Message History. Do the same on the transcripts channel (View Channel, Send Messages, Attach Files).
-
Open the dashboard and create a panel. Log in to the Tickets v2 dashboard from tickets.bot with the same Discord account you used to invite the bot, then pick your server. Create a panel and set:
- the channel to post it in (#open-a-ticket),
- the category new tickets go into (Tickets),
- your staff role as the support team,
- the button text and the message members see.
Menu names change between versions. If a label doesn't match, the official docs have the current wording. On the free plan you get 3 panels. Premium is $2.99/month and removes that limit.
-
Turn on transcripts. In the dashboard settings, point transcripts at #ticket-transcripts. Check the docs for which transcript options your plan includes.
-
Post the panel and lock down commands. Send the panel to #open-a-ticket. Next, open Server Settings > Integrations and click Manage next to the bot. When you add a new app, every member can use its commands unless the developer set defaults. Limit the staff-only commands to your staff role here.
-
Test it from a non-staff account. Use an alt account or ask a friend without the staff role. Click the button. You are checking three things: a channel appears in the Tickets category, the opener and your staff can see it, and other members can't. Close the ticket and make sure a transcript shows up in #ticket-transcripts. If any of those fail, see the fixes below.
Common mistakes and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Button does nothing or errors | Bot can't create channels in the category | Step 7: allow Manage Channels and Manage Permissions on the category |
| Ticket opens but staff can't see it | Staff role isn't set as support on the panel, or a deny override on the category | Add the role in the panel settings and check the category overrides |
| One staff member can't see tickets | A member override on that person | Remove it in the category's Permissions |
| Opener can't see their own ticket | Bot role is too low to add them | Step 6: move the bot role up |
| No transcripts | No transcript channel set, or the bot can't post there | Step 9 and the channel permissions in step 7 |
| Tickets stop opening on busy days | Discord's limit of 50 channels per category | Close old tickets, or route a second panel to a second category |
A Discord server also holds at most 500 channels in total. Very busy servers should close tickets quickly rather than leaving them open for weeks.
How PeakBot does tickets
If you'd rather manage tickets in the same place as your welcome messages, auto moderation and roles, PeakBot has tickets built in. A dedicated ticket bot like Tickets v2 is a good choice if tickets are all you need and you like its low Premium price. PeakBot makes more sense if you want one dashboard for the whole server.
To set it up:
- Do steps 1 to 4 above. The Discord side is the same for any ticket bot.
- Add PeakBot from peakbot.pro and pick your server (the getting started page walks through it). Move its role above your staff role.
- In the dashboard, open Tickets in the sidebar. Create your ticket types, choose private-channel tickets or form submissions, and add your support roles.
- Transcripts are on the Free plan. Auto-close for idle tickets needs a paid plan (Starter is $5.75/month per server).
- The Tickets page also shows stats on open tickets, claimed tickets and average resolution time.
There is no setup command. You do the whole setup on the dashboard, which shows you the result before you post it. You run the ticket commands inside a ticket channel, and they are listed on the Tickets wiki page. For a bot-neutral overview of ticket design, such as how many types to offer and who should handle them, see how to set up a Discord ticket system.
Frequently Asked Questions
Is Tickets v2 the same as Ticket Tool?
No. Tickets v2 is at tickets.bot and Ticket Tool is at tickettool.xyz. They have separate dashboards, plans and docs. Ticket Tool Premium is $8/month or $66/year per server, and ticket claiming is a Premium feature there. Tickets v2 Premium is $2.99/month.
Why can't my support team see the ticket channels?
Check three things in this order. Is the staff role added as support on the panel? Is the bot's role above the staff role? Does the category have a deny on View Channel for that role, or a member override on one person? Fixing the role order and the category overrides solves most cases.
Why isn't my server showing up in the Tickets v2 dashboard?
Make sure you logged in with the same Discord account that has Manage Server on that server. Also confirm the bot is actually in the server: look for it in the member list. If it isn't there, invite it again from tickets.bot. Then log out of the dashboard and back in so it refreshes your server list.
How do I resend the ticket panel if I deleted the message?
Open the panel in the Tickets v2 dashboard and send it to the channel again. Deleting the Discord message only removes the post. You can find the current button for resending in the official docs.
Where do ticket transcripts go?
They go to whatever channel you set as the transcript channel in the dashboard. Use a private, staff-only channel, and keep it separate from the public panel channel. If no transcripts appear, check that the bot can view, send and attach files in that channel.
Why did the bot stop opening tickets when we got busy?
The most likely reason is Discord's limit of 50 channels per category. When the category is full, new ticket channels have nowhere to go. Close finished tickets, or add a second category and route a second panel to it. On the Tickets v2 free plan, that second panel counts toward the 3-panel limit.
