A panel is the message your members click to open a ticket. Each button (or dropdown option) is a ticket type — for example "Support", "Report", "Billing" — and can carry its own label, emoji, colour and an optional application form that opens before the ticket. You build panels in the dashboard under Dashboard → your server → Panels; there is nothing to copy-paste by hand. The in-ticket actions (close, claim, transcript, reopen, delete) appear automatically for your staff, so you only configure the open buttons here.
| Option | What it does | Values |
|---|---|---|
| Panel name | Internal label used only in the dashboard to tell your panels apart. Never shown to members. | Free text |
| Title | The heading of the panel embed members see in the channel. | Free text |
| Description | The body text of the panel embed — explain what each button is for. | Free text, Discord markdown |
| Colour | Accent colour of the panel embed. Defaults to the Supreme brand colour if left blank. | Hex colour (e.g. #5865F2) |
| Layout | How the ticket types are presented — see the three layouts below. | Buttons · Dropdown · Threads |
| Open category | The Discord category where new ticket channels are created. Chosen from a dropdown — no ID copy-paste. | Category picker |
| Closed category | Optional category that closed tickets are moved to before archival. | Category picker |
| Support roles | The staff roles pinged in new tickets and allowed to claim, close, rename and escalate them. Members outside these roles cannot run staff ticket commands. | One or more roles |
| Max open tickets per user | Caps how many tickets one member can have open at once, so a single user cannot flood your queue. A per-panel override is also available. | Number (default 1) |
| Default priority | The priority stamped on tickets opened from this panel. Staff can change it later; SLA timers key off it. | Low · Normal · High · Urgent |
| SLA timers (Premium) | Target minutes for first response and for resolution. A breach raises an alert for staff — the two timers are independent. | Minutes (Premium) |
| Welcome message | An embed posted inside every new ticket — set expectations, link rules, or ask for details up front. Its accent colour is configurable. | Free text + hex colour |
| Naming template | Pattern for the ticket channel name, e.g. ticket-0042. Numbers auto-increment per panel. | Template string |
One button per ticket type, laid out in rows of five (up to 25 total). Best when you have a handful of clearly-labelled types you want visible at a glance.
A single select menu whose options are your ticket types (up to 25). Best when you have many types and want to keep the panel compact.
Same buttons as the Buttons layout, but each ticket opens as a thread instead of a channel — lighter-weight, and keeps everything under one parent channel.
| Option | What it does | Values |
|---|---|---|
| Button label | The text on the button (or the dropdown option). Optional only if you set an emoji — every button needs a label or an emoji to be valid. Trimmed to Discord's 80-character limit (100 for dropdown options). | Text, ≤ 80 chars |
| Button emoji | Shown before the label. Use a standard unicode emoji (🎫, ✅, ❤️) or a custom Discord emoji in the format <name:id> — or <a:name:id> for an animated one. A value that is not a real emoji is ignored, never breaking the panel. | Unicode · <name:id> · <a:name:id> |
| Button colour | One of Discord's four button styles. Colour is cosmetic — it does not change what the button does. | Primary (blurple) · Secondary (grey) · Success (green) · Danger (red) |
| Linked form | Optionally attach an application form. When set, clicking the button opens that form as a modal first; the member's answers are posted into the ticket the moment it opens. Leave blank to open a plain ticket. | Any of your forms, or none |
Unlike some bots, you do not configure close / cancel-close / reopen / confirm-close / delete / transcript / claim as separate buttons on the panel. Supreme Bot adds those actions automatically inside each ticket and shows them only to your support roles. That keeps the panel editor focused on the one thing you design — the ticket types members can open — while the ticket lifecycle stays consistent across every panel.
| Buttons or dropdown options per panel | 25 |
| Buttons per row (Buttons layout) | 5 (5 rows max) |
| Button label length | 80 characters |
| Dropdown option label length | 100 characters |
| Panels merged into one grouped message | Dropdown · Buttons · Stack |
| Each button needs | a label or an emoji |