All posts
discordticket botsupportprivate threadsserver management

Discord Ticket Bot: How Ticket Systems Work and How to Set One Up

How a Discord ticket bot works, channel tickets vs. thread tickets, a no-bot option with private threads, setup steps, and what to compare.

I
InviteForge Team

Ready to track your Discord invites?

Add to Discord — FreeOpen Dashboard →

Last updated: November 18, 2026 · Category: Guide · Editorial review · About the authors

A Discord ticket bot is an app that turns support requests into private conversations. A member clicks a button, the bot opens a channel or private thread that only that member and your staff can see, and staff close it once the problem is solved. A ticket system keeps reports, appeals, and purchase questions out of public chat.

This guide explains how ticket systems work inside Discord, when thread tickets beat channel tickets, how to run a basic system without a bot, and what to compare before you pick one.

Key Takeaways

  • A ticket is a private channel or private thread. Channel tickets count toward Discord's 500-channel limit per server, as Ticket Tool's documentation states; thread tickets do not.
  • A ticket channel stays private because of permission overwrites: @everyone is denied, and the member and the support role are allowed.
  • Compare ticket bots on panel limits, transcript limits, and thread support, using each bot's own documentation.

How a Discord Ticket System Works

Ticket bots name their settings differently. This guide describes a ticket in five stages and uses Ticket Tool as its example in the setup section:

  1. A panel. The bot posts a message with a button or menu in a channel members can read.
  2. A private space. When a member clicks, the bot creates a channel or a private thread for that ticket.
  3. Staff join. Members of your support role can see the new ticket and answer.
  4. Close. Staff or the member close the ticket when the problem is solved.
  5. Transcript. The bot can save the conversation to a log channel or send it to the member.

Ticket Tool, a ticket bot started in 2019, describes the idea in its documentation (retrieved 2026-11-02): "private support channels, which we call tickets."

Channel Tickets vs. Thread Tickets

A channel ticket is a new text channel for each request. A thread ticket is a private thread inside one support channel. The difference matters as your server grows.

Channel tickets Thread tickets
What the bot creates A text channel per ticket A private thread per ticket, under one parent channel
Server limit Count toward the 500 channels a server can have Not counted toward that limit; threads have their own limits
Who can see it Whoever the channel's permission overwrites allow "those invited and those with the MANAGE_THREADS permission"
Bot permissions Manage Channels to create channels Create Private Threads, Send Messages in Threads, Manage Threads
Inactive tickets Stay until deleted Archive after 1 hour, 1 day, 3 days, or 1 week of inactivity

The 500-channel limit comes from Ticket Tool's Channel Limit error page (retrieved 2026-11-02), which says the error appears when "your server has reached the 500 channel limit Discord has per server." Its suggested fixes are deleting old tickets, switching to thread tickets, because threads have their own limit, or turning on its Storage Mode.

The visibility and archive rows come from Discord's channel documentation (retrieved 2026-11-02). It defines a private thread as "a temporary sub-channel within a GUILD_TEXT channel that is only viewable by those invited and those with the MANAGE_THREADS permission." The archive options are 60, 1,440, 4,320, or 10,080 minutes. The same page notes that servers "have limits on the number of active threads and members per thread," without giving numbers. The thread permissions are the ones Ticket Tool's thread-style page lists.

Discord's guild documentation (retrieved 2026-11-02) says creating a channel requires the Manage Channels permission.

Why a Ticket Channel Stays Private

A ticket channel is private because of permission overwrites, not because of the bot. Discord's permissions documentation (retrieved 2026-11-02) applies them in a fixed order. Server-wide permissions come first. Then channel overwrites apply in this order: @everyone, then roles, then the single member, with member-specific allows applied last.

A channel-ticket bot can use that order:

  • It denies View Channel to @everyone on the ticket channel, so regular members cannot see it.
  • It allows View Channel for your support role, so staff can.
  • It allows View Channel for the member who opened the ticket, as a member-specific overwrite.

If staff cannot see new tickets, check the support role's overwrite on the ticket category. If everyone can see them, check that @everyone is denied. The Discord audit log shows who changed a channel's permission overwrites. How to make roles on Discord shows how to make a private channel by hand, which is the same mechanism.

A Ticket System Without a Bot

For a small server, private threads can work as tickets with no bot at all. Discord's permissions documentation lists Create Private Threads, which "Allows for creating private threads," and Manage Threads, which allows "viewing all private threads."

  1. Create a support channel that members can read.
  2. Give members the Create Private Threads and Send Messages in Threads permissions in that channel.
  3. Give your support role Manage Threads, so staff see every private thread without being added. The same permission lets them delete and archive threads.
  4. Pin a message that asks members to open a private thread for each request.

This costs nothing, but you lose what a bot adds: a button, a form, a transcript, and logs. Private threads also carry an invitable setting, which the channel documentation describes as "whether non-moderators can add other non-moderators to a thread." Check it if you do not want members pulling friends into their tickets.

As a made-up example: a server of 300 members runs support through private threads for a year. When it starts selling server perks, it needs a record of each purchase question, so it moves to a ticket bot with transcripts. The private-thread setup was enough until a record was needed.

How to Set Up a Ticket Bot

The steps below follow Ticket Tool's setup guide (retrieved 2026-11-02). Other bots have their own setup pages, so follow their documentation for the exact names.

  1. Invite the bot. Ticket Tool asks you not to remove requested permissions, because "they are completely needed for the bot to function properly."
  2. Create a support role. In Server Settings > Roles, create the role that answers tickets. Ticket Tool calls it the Support Team role.
  3. Open the panel settings. Sign in to the bot's dashboard, choose your server, and open Panel Configs.
  4. Create a panel. Click Create Panel and give it a name, such as Support or Shop.
  5. Send the panel. Choose the channel for the panel. Ticket Tool suggests a read-only channel.

Then open a test ticket from an account without staff roles, and check that it cannot see other tickets. How to test a new moderation bot uses the same check with a regular account. Choose who staffs tickets with care. How to make someone a mod covers which permissions to give staff and which to keep for admins.

What to Compare Between Ticket Bots

Free plans change, so check each bot's own pages before you decide. These are the documented limits on 2026-11-02:

Ticket Tool Ticket King Discord Tickets
Free panels Not stated in the docs reviewed 10 No limit stated; no premium plan, per its site
Transcript limit 1,000 messages 1,000 messages free, 5,000 on Premium Stores ticket messages, read in a web portal
Thread tickets Premium only Not stated in the docs reviewed Not stated in the docs reviewed
Open tickets Not stated in the docs reviewed 500 by default, configurable from 1 to 2,000 Not stated in the docs reviewed
Source code Not stated in the docs reviewed Not stated in the docs reviewed Open source; you can host your own

Sources: Ticket Tool's transcript options and thread-style tickets, Ticket King's free plan limits, and the Discord Tickets site, all retrieved 2026-11-02.

Thread tickets can come with trade-offs. Ticket Tool's documentation says its /add and /remove commands do not work with thread-style tickets, and that its claiming and permission options are not compatible with them.

Beyond limits, compare what changes your team's daily work: forms that collect details before a ticket opens, claiming so two staff members do not answer the same ticket, and automatic closing of inactive tickets. Ticket King lists auto-close after inactivity as a Premium feature.

Transcripts and Privacy

A ticket transcript is a saved copy of a ticket's messages. It can hold personal details, payment questions, or reports about other members, so treat it as a private record:

  • Send transcripts to a staff-only channel, and limit who can read it.
  • Tell members in your server rules that tickets are saved, and for what purpose.
  • Delete transcripts you no longer need.

Ticket Tool's transcript options include sending a copy to the member who opened the ticket (a Premium feature) and saving to Google Drive. Pick the destinations you can control.

Where InviteForge Fits

InviteForge does not include a ticket system. Use a dedicated ticket bot for support.

If your server gives roles or prizes for invites, some tickets may be about invite counts. InviteForge's /invites command, run as /invites user:@member, shows that member's real, fake, left, and bonus invites on every plan. The net count, real plus bonus, is the number rewards use. Staff can answer "where is my reward?" with numbers instead of guesses. How to set up invite milestone roles explains how those rewards are set.

Frequently Asked Questions

What does a Discord ticket bot do?

It gives members a button that opens a private space (a channel or a private thread) shared only with them and your support staff. Staff answer there, close the ticket when the problem is solved, and the bot can save a transcript of the conversation.

Can I make a ticket system on Discord without a bot?

Partly. Members with the Create Private Threads permission can open a private thread in a support channel, and staff with Manage Threads can see every private thread. You lose the button, the transcript, and the automatic logging that a ticket bot adds.

Why does my ticket bot say the server reached the channel limit?

Channel tickets use one channel each, and Ticket Tool's documentation gives a limit of 500 channels per server. Delete old ticket channels, switch to thread tickets, or turn on Ticket Tool's Storage Mode, which recycles tickets.

Are ticket transcripts private?

They hold everything said in the ticket, so treat them as private records. Send them to a staff-only channel, limit who can read that channel, and tell members that tickets are saved.

Does InviteForge have a ticket system?

No. InviteForge tracks invites, verifies new members, and filters fake joins. Use a dedicated ticket bot for support tickets. If members open tickets about invite rewards, staff can check their invite counts with InviteForge's /invites command.

Related reading

I
InviteForge Team · Builders of InviteForge

Published by the InviteForge organization — the independent team that designs, ships, and runs the Discord invite-tracking bot day-to-day (including the anti-fake pipeline and dashboard). We operate InviteForge on our own support server, so these posts reflect how we use the product, not generic marketing copy. Reach us via discord.gg/Dm3zPk3wWf.

How we write and update these guides →

Ready to track your Discord invites?

Add to Discord — FreeOpen Dashboard →