Skip to main content

How to design a ticket panel members understand

Button or topic menu, panel copy, topic names, emoji and button style: how to design a Discord ticket panel so members open the right ticket the first time.

Discord Tickets team6 min read

A ticket panel is the message people land on when something is broken, when they want to report someone, or when they just have a question. They read a few lines, see a button or a menu, and decide in seconds whether they’re in the right place. If the panel is unclear, tickets land in the wrong topic, arrive as a bare “help”, or never get opened because people DM a moderator instead.

Below: button or menu, what to write, how to name topics, common mistakes, and a ready-to-use example at the end.

Button or topic menu

The first decision is how a member opens a ticket.

  • Button — a single queue. One click and the member is in a ticket (or the intake form). Good when requests are all alike: a small server, one team.
  • Select menu — the member picks a topic first. Good when questions differ and different people handle them: reports go to moderation, billing to admins, tech issues to support.
Button Select menu
Queues One One per topic
Path to a ticket One click Pick a topic in the menu
Discord limit — Up to 25 options

Twenty-five is a technical ceiling, not a target. Past seven or eight topics, people stop reading and pick the first one that looks close. Merge similar topics and send rare cases to Other.

Tip. Genuinely separate flows, like support and staff applications, work better as separate panels in separate channels. See staff applications via tickets.

What the panel copy should say

The panel text answers three questions — when to open a ticket, what happens after the click, how soon someone replies — plus a couple of rules. It all fits in four to six lines.

When to open one. List the typical reasons and say when a ticket isn’t needed: “Gameplay questions go in #help. Open a ticket only when you need the team.”

What happens next. Spell it out: a short form, then a private channel only you and the team can see. People write more openly when they know the whole server isn’t reading.

Response times without promises. Don’t write “we reply within 5 minutes” unless you can deliver that at 3 a.m. on a Sunday. Describe reality instead: “We usually reply within a day, faster in the evening.” To find your peak hours, check the When tickets arrive chart on the Overview tab in Discord Tickets.

Rules. Two or three, no more: one question per ticket, don’t ping the team, don’t open duplicates. Link everything else to your rules channel.

Topic names and descriptions

Name topics the way members talk, not the way your team does. “Role or access problem” beats “Tier 2 support”, and “Report a member” beats “Reports”.

The description is one line under the label in the menu that says what belongs there.

Label Description
Role or access problem Didn’t get a role, can’t see a channel
Report a member Rule breaking, harassment, scams
Billing question Subscription, donation, refund
Join the team Moderation, events, design
Other Nothing above fits

Order them from most to least common, with Other last: without it, people pick a random topic and the ticket reaches the wrong people. Step-by-step setup is in the Topics section of the docs.

Emoji

An emoji helps people scan the menu, but only when its meaning is obvious.

  • One emoji per topic, not a string of them.
  • The meaning reads instantly: a wrench for tech, a flag for reports, a credit card for billing.
  • One style: standard or your server’s own, not a mix.
  • The emoji doesn’t replace the label — the topic must make sense without it.

Button style

Discord offers four button colors: Blurple, Grey, Green and Red.

  • Blurple — the neutral default.
  • Green — reads as “go ahead”, a good fit for Open a ticket.
  • Grey — fine for secondary panels, but easy to overlook.
  • Red — reads as delete or danger, so people hesitate. Avoid it for the main panel.

The label should be a verb plus an object: “Open a ticket”, “Contact support”, “Apply to the team”. Not “Click here” and not just “Ticket”. The same goes for the menu placeholder: “Choose what you need help with” beats “Select…”.

Components V2 or Content + embeds

The panel message comes in two formats.

Blocks (Components V2) Content + embeds
What’s inside Text, sections with an image, galleries, separators, containers Plain text and up to 10 embeds
Strength Flexible layout, the panel splits into clear blocks Familiar look, quick to build

For most servers the simpler format is plenty. Blocks pay off when the panel carries a lot of information: a banner on top, when to open below, rules after a separator.

In Discord Tickets you build the panel message in a preview that looks like Discord. There you also set the Panel language, which the bot uses for default labels, the form, the welcome message and its replies. Your own text isn’t translated, so keep both in the same language. The full setup is in Your first panel in the docs.

Common mistakes

  • A wall of text. Nobody reads a two-screen panel. Move long rules to a separate channel and link it.
  • No expectations on timing. The member doesn’t know how long to wait and opens a second ticket an hour later.
  • Too many topics. Fifteen options instead of five, and half the tickets go to whatever looked close enough.
  • The panel drowns in chat. If members can post in the panel channel, it’s buried within a day. Make the channel read-only.
  • The bot can’t see the channel. Starting November 16, 2026, channels where the bot lacks View Channel are hidden from it. Check permissions in the panel channel, the ticket category and the log channel.
  • Editing without updating. After changing a published panel, click Update in Discord — the message updates in place.

Example panel text

A template for a select menu with several topics. Swap in your own channels and realistic response times.

Server support

Open a ticket if:
- you didn't get a role or can't see a channel;
- you want to report a member;
- you have a billing or subscription question.

Gameplay questions go in #help - you'll get an answer faster there.

What happens next: a short form, then a private channel
only you and the team can see.
We usually reply within a day, faster in the evening.

One question per ticket. Please don't ping the team,
we see every ticket. Server rules are in #rules.

Menu placeholder: “Choose what you need help with”. If you use a button, label it “Open a ticket” and make it Green or Blurple.

What to ask in the form once a topic is picked is covered in intake form questions that work, and the full setup from scratch is in our step-by-step ticket guide.

Read next

All posts →