A Discord ticket panel is the message members click to open a support ticket, shown either as one or more buttons or as a dropdown menu. Buttons work best for a handful of ticket types you want visible at a glance; a dropdown panel fits a server with many departments, since it lists every active panel in one compact menu. Both can ask a short form before the ticket opens and route to their own category and staff role. This guide covers when to use each style, how ticket forms work, routing to departments, and how to build every piece in Noxyr.
What a Discord ticket panel actually is
A ticket panel is one saved configuration: a name, an embed (title, description, color, image), a button or dropdown style, a destination category, the staff roles who get access, an optional welcome message, and an optional form. Posting the panel sends that configuration as a message in a channel. Members interact with it, a private ticket channel opens under the category you picked, and the staff roles you picked can see it.
Nothing stops you from running several panels at once, one per ticket type. "Buy a product", "Report a bug", "Billing issue" and "Staff application" can each be their own panel, with their own category and staff roles, so a billing question never lands in front of the moderation team.
Button panels vs V2 dropdown panels
Noxyr posts a panel with /sendticketpanel, which defaults to buttons, or /sendticketpanelv2, which always posts a dropdown. The difference is not cosmetic. A button panel shows its own button plus, if you link other panels to it, up to 24 more buttons on the same message (25 buttons total, five per row). A V2 panel instead pulls in every active ticket panel in the server automatically and lists them as options in one select menu, up to 125 of them, splitting into extra dropdowns of 25 options each if you have more than that.
| Button panel | V2 dropdown panel | |
|---|---|---|
| Command | /sendticketpanel | /sendticketpanelv2 |
| Which panels appear | This panel, plus any you explicitly link to it | Every active panel in the server, automatically |
| Max options on one message | 25 buttons | 125 options across up to 5 dropdowns |
| Best for | 1-5 well-known ticket types, front and center | 6+ departments, or a catalog that changes often |
| Upkeep | Re-link and re-post when you add a panel | New panels appear on their own, no re-linking |
The practical rule: if you can name your ticket types on one hand, buttons read better and look more deliberate. Past that, a wall of buttons gets cramped and a dropdown keeps the message short while still covering everything, which is also why it is the better fit for a server that adds a new ticket category every few weeks.
Ticket panels with a form: what questions to ask
Either panel style can ask a short form (a Discord modal) before the ticket actually opens. Set it with /ticketform, which opens a pop-up pre-filled with the panel's current questions so you can edit them in place. A form is optional: leave it empty and the button or dropdown option opens the ticket straight away.
Questions are typed one per line, using a small syntax:
*prefix marks a question required. Without it, the member can leave the field blank.(long)suffix switches the field from a one-line box to a paragraph box, for anything longer than a short answer.| hint textafter the question adds gray placeholder text inside the box, for example*What are you selling? | e.g. spawners.
A form is capped at 5 questions, which is Discord's own limit for a single modal, and each question label is capped at 45 characters. Good forms ask only what staff would otherwise have to ask themselves in the first reply: what the member wants, an order or username to look up, and anything staff need before they can act. A store panel might ask what they're buying and how they'll pay; a bug report panel might ask what happened and what they expected instead. Skip questions with an obvious answer (their username, which channel they used) since Discord already gives staff that for free.
Routing tickets to different departments
Multiple ticket categories in Discord come from having multiple panels, not from one panel with branches. Each panel independently sets its own destination category, staff roles, ping roles and who is allowed to open it (an optional required role, useful for a "verified buyer only" support line). Give "General Support" one category and staff role, "Billing" another, and "Staff Applications" a third, and a member's choice at the panel decides which staff team ever sees the ticket.
This is where the two panel styles diverge again. A button panel routes by which button was clicked. A V2 dropdown panel routes by which option was picked from the list, since every option is really a different panel's ID under the hood, each with its own category, roles and form. Either way, the routing logic lives on the panel, not on the message, so the same set of departments works whether you post them as buttons in one channel or a dropdown in another.
Building each one in Noxyr
Panel creation, the embed, the destination category and the staff roles are set from the Tickets page on the Noxyr dashboard. From there:
- 1. Create a panel per ticket type, each with its own category and staff roles.
- 2. Optionally set a form for a panel with
/ticketform, or from the same panel editor. - 3. Post a small number of panels together as buttons with
/sendticketpanel, picking the channel and, if you want, linking a few more panels' buttons onto the same message. - 4. Or post a full department list as one dropdown with
/sendticketpanelv2, optionally choosing which panel supplies the title, description and image for that message. - 5. Re-run either command any time; posting again updates the same message in place instead of leaving duplicates behind.
Both commands work on any panel regardless of how it was originally built, so you can start with one button panel and switch the same panels to a dropdown later, or run both styles in different channels, without rebuilding anything.
Common questions
Can I mix a button panel and a dropdown panel in the same server? Yes. Panels are independent; post some with /sendticketpanel and others with /sendticketpanelv2 in whatever channels make sense.
Does the form apply no matter which panel style opened the ticket? Yes. The form belongs to the panel, so a member sees it whether they clicked a button or picked that panel from a dropdown.
Do I need a separate category for every department? No, it is optional but recommended. Separate categories keep permissions and channel lists clean once you have more than two or three ticket types.
What happens if I add a new panel after posting a V2 dropdown? The new panel will not show up until you re-post the V2 message with /sendticketpanelv2, since the option list is built at post time.
Is any of this behind a paid plan? No. Panels, forms, linked buttons and the V2 dropdown are all part of Noxyr's free ticket system.
For the rest of the ticket setup, including staff claiming, closing and saved transcripts, see the tickets documentation and the guide to ticket transcripts. Full feature list on the ticket bot page, or add Noxyr free to build your first panel.