How to Set Up Ticket Tool on Discord (Step by Step)

To set up Ticket Tool, first prepare your server in Discord: make a support role, a private tickets category and a panel channel. Then invite Ticket Tool from tickettool.xyz, log in to its dashboard, create a panel that points at that category and support role, and send the panel to your channel. Test it with an account that has no staff role before you announce it. Most setup problems come from channel permissions, not the bot.

Checked on each bot's own site or docs on 2026-11-03. We make PeakBot. Nobody paid to be in this post.

Part 1: Prepare your server in Discord

Do this before inviting any ticket bot. It works the same for Ticket Tool, PeakBot or anything else, and it prevents the two classic failures: members seeing each other's tickets, and the bot being unable to create channels.

1. Create a support role. Go to Server Settings > Roles > Create Role. Name it something like Support. Give it to the people who should answer tickets. You do not need to give it admin permissions.
2. Create a tickets category. Right-click your channel list > Create Category, name it Tickets, and turn on Private Category. Allow the Support role. This makes new ticket channels inherit a private setup.
3. Check the category permissions. Open the category's Edit Category > Permissions. @everyone should have View Channel denied. Support should have View Channel, Send Messages, Read Message History and Attach Files allowed.
4. Create a panel channel. Make a text channel such as #open-a-ticket. Members should be able to view it and read history, but not send messages, so the panel stays at the top and clean.
5. Create a staff log channel. Make #ticket-logs visible only to Support. This is where transcripts and ticket logs usually go.
6. Plan the bot's access. Whichever bot you use needs to create channels in the tickets category and set who can see them. When you invite it, keep the permissions it asks for, and make sure the category does not deny the bot's role.

Part 2: Set up Ticket Tool

Ticket Tool's own pages are the authority on exact menu names, so keep tickettool.xyz open as you go. The flow looks like this:

1. Invite the bot. Go to tickettool.xyz, click the invite option, choose your server and approve the permissions it requests. You need the Manage Server permission to add a bot.
2. Log in to the dashboard. Sign in with Discord on the Ticket Tool site and select your server.
3. Create a panel. A panel is the message with the button members press to open a ticket. Give it a name and a short description of what it is for, for example "Support" or "Report a member".
4. Point the panel at your category. Set the category from Part 1 as the place where ticket channels are created. If you skip this, tickets can land at the top of your channel list with the wrong permissions.
5. Add your support role. Select the Support role so staff are added to every new ticket automatically.
6. Set the opening message and logs. Write the message members see when the ticket opens (ask for the details you always end up asking for). Set #ticket-logs as the log or transcript channel.
7. Send the panel. Choose #open-a-ticket and send or publish the panel from the dashboard.
8. Test it. Use a second account, or ask a member without the Support role, to open a ticket. Confirm they can see only their own ticket, staff can see it, and closing it produces a log in #ticket-logs.

One thing to know before you rely on it: ticket claiming is a Premium feature on Ticket Tool, and Premium is $8/month or $66/year per server. If your staff workflow depends on one person claiming a ticket so others leave it alone, budget for that or use a role-based habit instead.

Part 3: Fixes for common problems

• "The bot can't create ticket channels." The bot's role is missing Manage Channels, or the tickets category denies it. Open the category permissions, add the bot's role and allow View Channel, Manage Channels and Manage Permissions.
• "Members can see every ticket." @everyone can view the category. Deny View Channel for @everyone on the category, then check that existing ticket channels are synced to it.
• "The button does nothing." The bot cannot see or send messages in the panel channel, or the panel was deleted and needs resending. Give the bot View Channel and Send Messages in #open-a-ticket and send the panel again.
• "Staff aren't added to tickets." The support role was not selected on that panel. Each panel can have its own roles, so check the one members are using.
• "No transcripts appear." The log channel is not set, or the bot cannot post there. Allow the bot to view and send in #ticket-logs.

Part 4: Doing the same thing with PeakBot

If you want tickets alongside welcome messages, verification, auto moderation and leveling in one bot, PeakBot's Tickets page covers the same job. If tickets are the only thing you need and Ticket Tool is already working, there is no reason to switch: a bot built only for tickets keeps your setup focused.

PeakBot's Tickets feature gives you private-channel tickets or form submissions, custom ticket types, support roles, and stats on open, claimed and average resolution time. Transcripts are free; auto-close needs a paid plan.

1. Do Part 1 above. The same category and role setup applies.
2. Add the bot and open the dashboard at peakbot.pro.
3. Pick your server and open Tickets in the dashboard sidebar.
4. Choose private-channel tickets or form submissions. Forms suit applications and reports where you want the same questions answered every time.
5. Create your ticket types (for example Support, Report, Appeal) and assign support roles to each.
6. Review the preview, then post. Tickets are configured on the dashboard rather than by a setup command, and it shows you the result before you post it.
7. Test with a non-staff account, as in Part 2.

Once tickets are open, PeakBot's ticket commands are run inside the ticket channel. The PeakBot wiki lists each one and the permission it needs. The Free plan has no time limit; paid plans are per server, starting with Starter at $5.75/month or $48/year.

How the ticket options compare on price

Frequently Asked Questions

Is Ticket Tool free?

It has a free tier that covers basic panels and tickets. Premium is $8/month or $66/year per server, and ticket claiming is one of the Premium features. Check tickettool.xyz for the current split.

Why does Ticket Tool say it is missing permissions?

The bot's role cannot manage channels or permissions in the tickets category. Re-invite it with the requested permissions, or add its role to the category with View Channel, Manage Channels and Manage Permissions allowed.

How do I make tickets private so only staff and the member can see them?

Set the tickets category to deny View Channel for @everyone and allow it for your support role. The ticket bot then adds the member who opened the ticket to their own channel.

Can I have more than one type of ticket?

Yes. On Ticket Tool you create separate panels or options for each type. On Tickets (tickets.bot) the free plan allows 3 panels. On PeakBot you create custom ticket types on the Tickets page.

Should I run two ticket bots at once?

Avoid it. Two panels with different behaviour confuse members and split your logs. Pick one, remove the other's panel, and keep a single log channel.

What is a free alternative if I hit Ticket Tool's limits?

Dyno's tickets module, including transcripts, has been free since 29 May 2026. Tickets (tickets.bot) is free up to 3 panels. PeakBot includes tickets and transcripts on its Free plan, with auto-close on a paid plan.