GuidesUpdated 12 October 2026
How to make a ticket panel in Discord
The message members press to open a ticket: what goes on it, buttons or a dropdown, and the mistakes that leave it ignored.
What a ticket panel is
A ticket panel is a message a bot posts in one of your channels, with a button (or a dropdown) for each kind of request. Pressing one opens a private ticket channel. It is the only part of a ticket system most members ever see, so it is worth five minutes.
This is a panel built with TicketCrew, drawn the way Discord shows it:
Need help?
Pick what you need and a private channel opens with the right staff. Please open one ticket per question.
Where to put it
Give it a channel of its own, such as #support or #open-a-ticket, where members can read but not write. A panel in a busy chat channel scrolls away within the hour; a panel in a quiet channel is always the last message, which is what makes people find it.
What to write on it
- A title that is a question or an instruction, like “Need help?” or “Open a ticket”. Members scan; they do not read.
- One or two lines on what happens when they press: who will answer, and roughly when. If staff reply within a day, say so, and fewer people ping moderators.
- A rule or two at most, such as one ticket per question. A wall of rules on a panel goes unread.
One button per kind of ticket
Split tickets by who should answer them, not by topic. Support questions, staff applications and player reports usually go to different people, so each gets its own button and its own staff roles. Members of one team never see the others' tickets, and the right people are pinged when one opens. TicketCrew allows 7 kinds of ticket and 50 panels per server.
Mistakes that leave a panel ignored
- Too many buttons with labels that overlap, so members guess and pick wrong.
- No staff role on a button, so the ticket opens and nobody is told.
- Posting it in a channel where the bot cannot send messages or embed links.
- Re-posting the panel to change it. In TicketCrew, editing a published panel updates the same message, so links to it keep working.
The full reference, field by field, is under Panels in the docs.