A good Discord ticket panel tells members what tickets are for, what to have ready and how fast to expect a reply, then gives them one obvious thing to click. Below are copy-ready panel messages for common ticket types, followed by layout advice for buttons, select menus and intake questions.
What every panel needs
- A clear title, such as "Need help?" rather than "Tickets".
- One or two lines on what it's for.
- What to have ready, like an order number or a screenshot.
- Expected reply time. Even "usually within a few hours" cuts down on pings.
- One button or menu option per ticket type, labeled with a verb.
Panel message templates
General support
## Need help?
Open a ticket and our support team will reply as soon as they can,
usually within a few hours.
**Before you open one:** check the FAQ channel, and have any screenshots ready.
-# Please don't DM staff for support. Tickets keep everything in one place.Button: Open a ticket
Reports
## Report a member
Seen someone breaking the rules? Tell us privately here.
Include **who**, **what happened** and **a message link or screenshot**.
Reports are only visible to the moderation team.Button: Report a member
Appeals
## Appeal a punishment
Think a warning, timeout or jail was a mistake? Open an appeal.
Tell us what happened and why you think it should be reversed.
A staff member who wasn't involved will review it.Button: Start an appeal
Store or billing
## Order and billing help
Questions about a purchase? We'll sort it out.
Have your **order number** and **the email you paid with** ready.
Never post card details or passwords.Button: Get billing help
Partnerships
## Partner with us
Want to collaborate? Tell us about your community.
We'll ask for your server's invite, size and what you have in mind.Button: Request a partnership
One panel, several ticket types
## How can we help?
Pick the option that fits best. Not sure? Choose General support.
🛠️ **General support** - questions and problems
🚩 **Report** - rule breaks and safety concerns
⚖️ **Appeal** - challenge a punishmentUse one button per option, or a select menu with a description for each.
Buttons or a select menu?
| Buttons | Select menu | |
|---|---|---|
| Best for | 1 to 5 ticket types | 5 or more ticket types |
| Options visible | All at once | After opening the menu |
| Per-option description | No | Yes |
| Discord limit | 5 buttons per row | 25 options per menu |
Ask the right questions up front
Intake questions save a round of back-and-forth. Keep them to what staff need to start:
- Support: What do you need help with? What have you tried?
- Reports: Who are you reporting? Paste a message link or attach a screenshot.
- Appeals: What was the punishment? Why should it be reversed?
- Billing: What's your order number?
Discord forms hold up to five questions, so pick the ones that matter.
Design tips
- Match your server's colors. Pick the panel's accent with the Discord color picker.
- Keep the panel channel read-only, so the panel stays at the bottom.
- Label buttons with verbs: "Open a ticket", not "Ticket".
- Add opening hours if you don't have staff around the clock.
- Test as a member, not as an admin, before announcing it.
Build a panel in Better Tickets
In Better Tickets, each ticket type is a category with its own staff roles and questions. To make the panel, open the message builder, write the message, add a Buttons/menu block and point each button or menu option at a category. You can preview it live, send it as the bot or as a webhook, and edit the same message later.
Ticket questions can be short or long text, numbers, select menus, user, role or channel pickers, or file uploads, so a report form can ask for a screenshot directly. If your team keeps hours, a category's schedule blocks new tickets outside them and shows a message you write. The quickstart gets a first panel live in about five minutes.
Frequently asked questions
What is a Discord ticket panel?
The message members click to open a ticket. It usually has a short explanation and one button or menu option per ticket type, such as Support, Report or Appeal.
What should a ticket panel say?
What tickets are for, what to have ready, how long a reply usually takes, and what not to use tickets for. Two or three short lines are enough.
Should I use buttons or a dropdown on a ticket panel?
Use buttons for up to four or five ticket types, because every option is visible. Use a select menu when you have more, or when each option needs a description.
How many ticket types should a panel have?
As few as you can. Most servers do well with two to four. Each extra option makes members stop and wonder which one to pick.
Where should I put the ticket panel?
In a read-only channel that's easy to find, such as #support or #help, and consider a second one under your rules.