Ticket panels
Build the message members click to open a ticket, with a live preview of what they will see.
A panel is a message with a dropdown or a row of buttons. Each option is a category, and clicking one opens a ticket.
You can build panels in the dashboard or with commands. The dashboard is easier and does more; the commands work on every plan.
Building one in the dashboard
bravenbot.com/dashboard → your server → Ticket panels → Customise
Four tabs, with a live Discord preview beside them that updates as you type.
Appearance
Everything about how the embed looks:
| Setting | Notes |
|---|---|
| Panel name | Internal only. Members never see it — it is how you find the panel in the list. |
| Channel | Where the panel is posted. |
| Title and Description | The embed's heading and body. |
| Colour | Or leave it to inherit your server branding. |
| Message above the embed | Plain text posted alongside. Mentions here never ping — a panel that re-pinged @everyone every time you edited it would be a problem. |
| Author, Footer, Image, Thumbnail | Standard Discord embed parts. |
| Show timestamp | Adds the posted time to the footer. |
Options
Dropdown holds up to 25 categories behind one menu. Buttons put each category on the message itself — better for three or four, unwieldy past that. With buttons you also pick each option's colour on the category itself.
Behaviour
Who handles these tickets and how they behave:
- Support roles — who can see and claim tickets from this panel. Falls back to your server's staff roles when empty, so a panel with nothing set still works.
- Viewer roles — can read tickets but not act on them.
- Ask before closing — a confirmation step on the close button.
- Keep closed tickets — a closed ticket keeps its reopen and transcript buttons instead of vanishing.
- Open tickets per member — stops one person opening fifteen.
Embed fields
Up to 25 name-and-value pairs inside the embed. Useful for "what to include in your report" without making the description enormous.
Posting and editing
Post puts the panel in the channel. It is queued rather than instant — the dashboard hands it to the bot, which picks it up within about fifteen seconds.
After that, Save edits the message already in Discord. You do not repost, and the panel does not move or lose its place in the channel.
Editing a panel never breaks it
Braven's buttons carry no hidden state — they reference a category, and the category is looked up when somebody clicks. So you can rewrite a panel as often as you like, and one posted a year ago still works. This is also why Braven survives updates without the "This interaction failed" problem other ticket bots have.
Duplicate copies a panel, its categories and its fields into a new unposted panel — the fastest way to make a second panel that is mostly like the first.
Delete archives it. The message stays in Discord and keeps working; it just disappears from your dashboard. Nothing already opened is affected.
Doing it with commands
/panel create channel:#support title:Support
/panel category panel:1 label:General Support
/panel post panel:1/panel create prints the panel's ID, which the other two need. And:
/ticketconfig style panel:1 style:buttonsLimits
| Plan | Panels | Categories |
|---|---|---|
| Free | 1 | 3 |
| Pro | 5 | 15 |
| Elite | Unlimited | Unlimited |
Discord caps any single panel at 25 options regardless of plan.
If you downgrade, nothing is deleted. Panels over the limit stay exactly as they are and keep working — you simply cannot create another until you are back under it.