Discord Ticket Panel Design: What You Can Change, and What Discord Decides

Everything else in a ticket system is read by somebody who is already in trouble. The panel is different: it is read by everyone who is standing at the door deciding whether to knock. It is the only support surface in your server that people look at before they have a problem, which is why it is worth more than ten minutes of attention and why it was the wrong thing to charge for.

That last part changed on 6 September 2026. Panel design used to sit behind a paid plan here, the way it still does on several other ticket bots. It does not any more, and this is what there is to design.

What can you change on a Discord ticket panel?

Short answer: the wording, the colour, two images, an author line, up to 25 named fields, up to five link buttons, the line of plain text above the post, how the categories are presented, and which of the two layouts the whole thing uses. On a free plan you can change all of it except the footer.

It helps to know that a panel is not a special object Discord understands. It is a message our bot posts and then edits in place, built from the same parts any bot has: an embed, or since this year a components container, with buttons and a dropdown attached. Every limit below is Discord's, not a tier we invented.

The fields are the part most servers underuse. A field is a small labelled block, so a panel can carry "Response time: usually under an hour" and "Before you open a ticket: check #faq" as separate readable rows instead of one paragraph nobody finishes. They cost nothing and they answer the two questions a member has while they are hovering over the button.

Classic embed, or the modern layout?

Discord shipped a second way to build a message, and a panel can use either. The classic embed is the coloured box you already know. The modern layout is one container holding blocks: text, images, a text block with a small image beside it, dividers, button rows and the category picker, in any order you drag them into.

Pick the classic embed if you want the panel to look like every other bot embed in the server, which is a real argument: familiar reads as trustworthy. Pick the modern layout if the panel is doing more than one job, for example a short welcome, then a divider, then the categories, then a row of links to your rules and store.

One caveat worth knowing before you switch a live panel. Discord's flag for the modern layout cannot be added to or removed from an existing message, so changing style reposts the panel as a new message rather than editing the old one. Anything pointing at the old message, a pin or a link you shared, points at nothing afterwards. Every other change edits in place and keeps the same message.

How should members pick a category?

Three ways, and it is a design decision rather than a category one. What the categories say and how many you should have is a separate question we answered in full; this is only how they are presented.

A dropdown is one control that stays one control no matter how many options you add, and it hides the options until pressed. Buttons put every category on screen at once, each in its own colour, which is faster to press and gets loud past about six. A list gives each category its own row with its name, description and an Open button beside it, which is the readable option when your categories genuinely need explaining. The list needs the modern layout and fits up to ten categories.

Category button colours are the cheapest signal on the panel. Discord gives four: grey, blurple, green and red. Use green for the thing you want pressed, red for the one that should give somebody pause, and leave the rest grey. Colouring everything is the same as colouring nothing.

If a design does not fit, the panel does not fail to post. The renderer steps the picker down until it fits and tells you what it did:

That fallback is deliberate. A publish an admin is waiting on should never fail because a design got one category too large, so an over-long description is clipped and an over-large picker is simplified, with a plain sentence explaining each step down.

What the bot refuses to save, and why

The most useful rules in this system are the refusals, because each one is a failure that would otherwise happen later, quietly, to somebody else.

The same principle covers the rest. An unknown design field is rejected by name instead of being dropped, because an editor that sends a value expects it to have done something. The category picker is the one block that cannot be deleted from a modern layout: remove it and it is put back at the end, because a ticket panel with no way to open a ticket is not a panel. The total is measured on what will actually be sent, not on what you typed, so the count you see is the count Discord will see.

Why your design is not in Discord yet

A saved design and a published post are different things, and this is the single most common confusion with any Discord ticket bot that has an editor.

Editing from Discord saves your changes and leaves the live post alone until you press Publish, and the editor carries a line saying the post is out of date for as long as that is true. On the dashboard, saving something that shows on an already published post updates Discord in the same action.

The bot knows the difference honestly rather than by guessing. When it publishes, it stores a fingerprint of everything the post was built from, and "is this post out of date" is that fingerprint compared against what it would render right now. Timestamps could not answer it, because a publish writes the panel in the same second it renders it. It also means a plan change counts: when a server upgrades, the footer changes, so the bot republishes its panels by itself rather than leaving a stale watermark.

If you have never pressed Publish, none of this has happened yet. That is worth checking: publishing your first panel is also what starts 14 days of Premium, with no payment method at any point, so it cannot become a charge.

What panel design cannot fix

Being straight about this is more useful than another feature. A well designed panel changes who opens which ticket and how much context they bring. It does not change how many people need help, and it cannot rescue a system that is wrong underneath.

That last one is worth separating properly, because the two get confused. Panel design changes the message the bot posts. Whitelabel changes the bot itself: its name, avatar, banner and bio in your server. You can have a fully branded panel posted by a bot still called AI Ticket Bot, and that is what a free server gets.

What it costs

Nothing, on every plan, since 6 September 2026. Colour, both images, the author line, the fields, the link buttons, both layouts, all three pickers and the per category button colours are free, including on the free plan.

The exception is the footer pair. A free server renders "Powered by AI Ticket Bot" with the bot's icon, and paid plans set their own footer text and icon. That is the whole of the plan boundary in panel design, and it is deliberately the smallest part of the post.

It is worth pausing here if panel appearance is what you are currently paying another bot for, because on several of them it is the paid tier's main content. We wrote up what switching actually involves separately, including the part where your old transcripts do not come with you.