Panels overview

What panels are and how members use them.

A panel is the message Ticket King posts in your server that members interact with to open a ticket (or submit an application).

Other parts of the bot, such as settings, logs, transcripts, and customization, support what panels do.

A finished panel as it appears in a Discord channel

The anatomy of a panel

Every panel has three layers:

1. The embed(s)

The visible card members see. Title, description, color, optional image, thumbnail, footer. Up to 10 embeds per panel (Discord cap). You design these in the panel editor's embed sub-panel.

→ Edit the embed

2. The interactive components

What members click. Three flavors:

Buttons. One per action a member can take. A panel holds up to 5 rows of up to 5 buttons, so up to 25 buttons in total.
Select menus (dropdowns). The member picks from a list. One select menu fills a whole row, and each can hold up to 25 options. Good when you want a single tidy list rather than many buttons.
Link buttons. Open a website for the member instead of opening a ticket.

A panel can use up to 5 component rows total. Each row is either up to 5 buttons OR a single select menu.

3. The options

Each button (and each select-menu entry) is an option. Each option has its own per-option settings: category, support roles, welcome message, form, and so on.

This is the most important concept: every option is independently configurable. Whether an option is a button or a select-menu entry, each one can open tickets in a different category, with a different support team, with different form questions. A single panel can hold many options across its rows, so one panel can route members to several different ticket types.

The two kinds of panel

Ticket panel

Clicking a button (or picking a select option) opens a ticket channel or thread, optionally after the member fills in a short form.

Pick this for general support, bug reports, or role requests, anywhere you want a conversation as soon as the member acts.

Application panel

Clicking the button opens a pop-up form. The submission goes to your reviewer queue and no channel is created. Your team approves or denies it, with automatic role grants on approve.

Pick this for staff applications, partner applications, or role applications.

→ Applications overview

Panel limits

Free: up to 10 panels per server.
Premium: unlimited panels per server.
Templates: 1 free, 25 premium per server.

→ Panel limits

When to create one panel vs many

Better when: every flow belongs in the same channel and reads as part of the same offering.

"Open a Ticket" panel with buttons for 🐛 Bug Report, ❓ Question, 💡 Suggestion, 🤝 Partnership.
Each button can still go to its own category, with its own support role, with its own form.

This is the most common pattern.