Create a ticket panel
A panel is the embed that customers click to open a ticket. Style it, add buttons or a dropdown, optionally attach a modal - then post it to a channel.
How it works, end to end
Design and publish the panel from the dashboard. The Post action sends the saved embed to the selected channel; alternatively, use the /embed command in Discord.
Design the embed in the dashboard
Open Embeds > New embed in the dashboard. You get a live preview, form fields for each part of the embed, and reusable saved panels scoped to your server. Give each panel a clear name - that name is what you’ll type to send it later.
What a panel is made of
Every panel bundles three things:
- The Discord embed - title, description, color, author block, fields (name / value, with an inline toggle each), thumbnail, image, footer, timestamp.
- Interactive components - buttons (with the standard Discord styles and an optional emoji), a select dropdown (placeholder, min/max, up to 25 options), or an application form (a multi-button collection of question sets).
- An optional modal - up to 5 input fields that pop up before the ticket opens. Each field is either single-line or multi-line, with optional placeholder, required toggle, and min/max length.
Or send it with /embed
In your Discord server, run:
/embed name:<your-embed-name>- posts the embed in the channel you ran the command in./embed name:<your-embed-name> channel:#help- posts it in a specific channel instead.
The name field autocompletes from every embed you’ve saved on the dashboard, so you don’t have to remember exact spellings. As soon as the message is posted, the embed is live - customers can click the buttons and tickets will open.
Two prerequisites: the bot needs Send Messages and Embed Links in the destination channel, and you need Discord’s Manage Messages permission yourself to run the command. /embed also refuses to post inside a ticket channel - that’s a different surface.
Editing a live panel
When you change the embed on the dashboard, the version that’s already posted in Discord won’t pick the changes up reliably. Resend it.
- Make your edits on the dashboard and save.
- Either delete the old message in Discord first, or just run
/embedagain with the same name. Running it again posts a fresh copy with the new configuration cleanly attached.
We recommend resending after any meaningful change - it’s the only way to be sure the new configuration is the one customers interact with.
Next up
Last setup step: assign staff roles so your team can actually answer tickets.