Panels
A panel is the storefront, the member's entry point: a message with a button in a channel (or a command). The panel decides how the entry looks and which categories it offers. How the ticket itself behaves — permissions, roles, texts, buttons, limits, logs — is set in categories. A server can have several panels: “Support”, “Reports”, “Sales”.
Where it is set up
| Way | What you can do |
|---|---|
| Web panel → Panels → panel | The “Categories” and “Message” tabs (the “Open ticket” button is there too); on the right — how the message will look in the channel, a link to this panel's tickets and the panel check. The name and position are in the “⋯” menu in the header. |
/ticket setup | The setup wizard: a set of request topics, the “default” panel, channel categories and a channel with a button. |
/panel … | Creating, sending, style, texts — see Commands. |
Styles
- What the member sees
- An embed with an “Open ticket” button. Press → category pick (if there are 2+) → a form or the channel right away.
- When to pick it
- The main option.
- What the member sees
- A button for each of the panel's categories; the color comes from the panel item, otherwise from the category's “Button color”. Press → the form or the channel of that category right away.
- When to pick it
- When there are only a few topics and you want to skip the pick step.
- What the member sees
- No button; the message has instructions. Tickets are opened with /ticket open [panel].
- When to pick it
- When you don't need a separate channel with a button.

Alex used /
Multi-panel
Several panels in one message: “Report | Support | Staff application”. It is created at the bottom of the “Panels” section; you need at least two panels. Pressing a button or item leads exactly where the panel’s own button leads — the panel’s categories and their settings work as usual, and the multi-panel adds nothing of its own to the ticket.
| Option | What it does |
|---|---|
| Style | “Buttons” — a button per panel, up to 25 (5 per row). “Drop-down” — one menu, an item per panel; more compact with 5+ panels. |
| Panels and order | Which panels are included and in what order. One panel can be in several multi-panels; the panel doesn't need its own message then — the check (“Needs attention” on the overview and “Check” on the panel) counts it as published. |
| Item label | Each panel in a multi-panel has its own label, emoji, button color and description (the second line in the drop-down). Empty — the panel name and the emoji/color of its “Open ticket” button. |
| Preview | At the top of the form — how the message will look in the channel: the embed, buttons or a list with items. Updates as you edit. |
| Channel | Where to publish. When set, the message is sent (or updated) on save; without a channel the multi-panel is only saved. |
| Design | Title, description, color and the other embed fields — the same editor as for the panel message. By default the title is the multi-panel's name. |
The panel’s categories
Which categories to offer in this panel and in what order. A category can get its own label, emoji, description and button color — only for this panel; the same category can be named differently in another panel. The star marks the “default” category: if there is only one category, there’s no pick and the ticket opens in it right away. Up to 25 categories. The ticket’s behavior is set by the category itself.
Message and style
The panel message’s text and embed (title, description, color, images, footer, author), the style and the channel to publish in. The preview shows the message the way a member will see it. The “Send” button in the header publishes or updates the message.
The “Open ticket” button
Emoji, label and color of the main button on the panel message. By default — 🎫 “Open ticket”, green. Only the “Button in the channel” style has it. Buttons inside the ticket are set on the category.
Copying a panel
The “⋯” menu in the panel header → “Copy”: a new panel with the original’s design and the same categories — they are not duplicated, the copy shows the very same ones. The published message and the number are not copied — you need to send the copy to a channel yourself.
Deleting a panel
- •The panel message in the channel is deleted; open tickets stay and work by their category's settings.
- •A panel that is in a multi-panel can't be deleted — remove it from the multi-panel first.
- •The panel number is not reused.
- •Categories are not deleted — they stay on the server and in the other panels they are in.
