Discord Ticket Threads vs Channels: Which Ticket Mode to Pick

A ticket bot can open each ticket as its own private channel, or as a private thread inside one channel. Both keep the conversation private. They differ in what Discord counts, who can see the ticket, and what happens when it moves or closes.

What is the difference between ticket channels and threads?

A channel ticket is a new channel in a category. A thread ticket is a private thread under one text channel. Everything below follows from that.

Do ticket threads count toward the channel limit?

No. That is the main reason to use them. A server holds 500 channels and a category holds 50. In channel mode every open ticket uses one of each. A thread is not a channel, so a thread panel never fills either.

If tickets already stopped opening, start with a full ticket category or the 500 channel limit. Clearing old tickets fixes it today. Threads stop it coming back.

Threads have a ceiling too, 1,000 active per server, but a thread quiet for 7 days is archived and stops counting.

Who can see a ticket thread?

The people in the thread, and anyone with Manage Threads in its channel. This is the biggest difference, and it is Discord's rule, not the bot's.

In channel mode, access is set on the channel, and the staff permissions you give each role decide who gets it. In thread mode those role rules do not apply. The member is added when the thread opens. Staff get in one of two ways:

• The bot mentions their role in the thread. Discord adds every member of a mentioned role to a private thread. The ping on new tickets is off by default, so without it staff without Manage Threads first join when the AI hands the ticket over. How staff pings work has the six moments a role is pinged.
• They hold Manage Threads in the channel the threads open under, so they see every thread there.

The second rule applies to members too. If they cannot see the channel threads open under, the bot refuses the ticket and names the channel. Let members view it and deny them Send Messages, so it stays quiet. Adding someone to a ticket covers the same trap from the staff side.

What changes for claims and transfers?

In channel mode, both change who can see the ticket. In thread mode, neither does.

A claim on a channel ticket can move it to the claimer's category and hide it from roles without See claimed tickets (private claimed tickets explains it). Deleting empty claim categories is channel mode only too.

A transfer on a channel ticket moves it under the new category and swaps the old team's access for the new one's. On a thread ticket the notice is posted, but the thread never moves and nobody gains or loses access. If hand-overs must change who can read a ticket, use channel mode.

Anti-DM protection, which delays a new ticket so scam accounts cannot tell whose it is, is channel mode only as well.

What happens when a ticket closes or goes quiet?

A channel is deleted. A thread is kept, but emptied of members.

A closed channel ticket is deleted and the transcript is the record. A closed thread ticket gets a close summary with the transcript button, then the bot removes the member and anyone added who is not staff, and archives and locks it. Staff can still read it in Discord, and nobody can revive it by typing.

An open thread that sits quiet for 7 days is archived by Discord and drops out of view while the ticket is still open. A new message reopens it, and the bot wakes it first when staff press a button or run a ticket command in it.

What does the member see, on desktop and on a phone?

In both modes, a private space that only they and your staff can read. The bot mentions the member in the first message of the new ticket, so the notification takes them straight to it on the Discord app or on a computer.

In channel mode the ticket is a new channel in their list. In thread mode it is a thread under the channel they pressed the button in, or the one you chose. Either way it disappears from their view at close.

For staff on phones, a channel list is easier to scan than a long thread list. If your team works from phones and you use threads, turn on the ping for new tickets.

Which ticket mode should you pick?

Start from the shape of your server.

Busy servers often mix: a high-volume support panel on threads, a small appeals panel on channels. Running support for a large server goes further into that split.

How do you switch a panel between channels and threads?

Change one setting on the panel. Free on every plan.

The change applies to new tickets. Tickets already open stay as they are until they close.

Where each mode falls short

The honest list.

Channels are more precise, threads hold more. Pick per panel, not for the whole server.