Discord ticket bot
A panel with a button. Someone presses it and gets a private channel or a thread, your support role gets pinged, and when it closes you keep a transcript.
Channels or threads — you choose per panel
Three options, set when you create the panel: a private channel in a category you pick, a private thread, or a public thread. Threads keep a busy server's channel list short; channels survive longer and are easier to hand around. Different ticket types can use different ones — the choice belongs to the panel, not the server.
What you get without configuring anything clever
| Setting | Does |
|---|---|
| Support roles | Who can see and manage tickets from this panel |
| Ping roles | Who gets notified when one opens — separate from who can see it |
| Claiming | A staff member takes a ticket, so two people do not answer at once |
| Ratings | The opener leaves a score and a comment when it closes |
| Transcript on close | Posted to a channel you choose, so the conversation survives the ticket |
| Max open per user | Stops one person opening fifteen |
| Ticket name format | Your own naming, rather than a scheme you have to live with |
| Welcome message | Sent inside the ticket, so the first reply is not "what do you need?" |
| Creator can close | On or off — some teams want it, some very much do not |
Saved replies, because most tickets are the same ticket
Quick responses are stored per server and grouped into categories, so the answer to "how do I appeal" is one pick rather than something a moderator retypes forty times and gets slightly wrong on the fortieth.
Setting it up
/ticket-panel create name: Support channel_type: Private thread support_role: @StaffThat publishes the panel in the channel you run it in. Everything else — the welcome message, claiming, ratings, transcripts, the open limit — is in the dashboard afterwards, and none of it is required to get a working ticket.
What it costs
Nothing. Tickets are not a premium feature, because no feature is — paid plans raise throughput caps and nothing else. Or run it yourself under the AGPL-3.0, where the caps are whatever your hardware will take.
It is not only a ticket bot
The same bot runs staff applications, ban appeals, verification, anti-raid and giveaways — one bot to invite, one dashboard, one export if you ever leave.
Questions
Does it use channels or threads?
Either, chosen per panel: a private channel in a category you pick, a private thread, or a public thread. Different ticket types in the same server can use different ones.
Do I get transcripts when a ticket closes?
Yes. Turn on transcript-on-close and pick a channel, and the conversation is posted there when the ticket ends.
Can staff claim a ticket so two people do not reply at once?
Yes, claiming is a per-panel setting and the claimer is recorded on the ticket.
Can I stop one person opening twenty tickets?
Yes. Each panel has a maximum number of tickets one user may have open at a time.
Is the ticket system free?
Yes. Every feature is on every tier — paid plans raise throughput caps only, and you can self-host the whole bot for free under the AGPL-3.0.