Custom Messages
Each category has its own intro message, closed message and optional DMs, and each panel has its own embed. This guide covers those. Every other piece of bot text, such as button labels and error messages, is under Localization.
All of these accept variables such as {{user.mention}} and {{ticket.number}}.
What you can customize
| Message | When members see it |
|---|---|
| Intro Message | First message in a new ticket, above the ticket buttons |
| Closed Message | Posted in the channel when the ticket closes |
| Direct Messages | Optional DMs when the ticket opens, closes, or someone is added. Off by default |
| Panel embed | The message members click to open a ticket |
The first three are on a category's Messages tab (Categories → a category → Messages), and the panel embed is in the panel's Embed Builder. Both editors show a live preview.
Intro message
The intro message is the first thing a member reads in their ticket, so use it to set expectations: what to include, how long a reply usually takes, and anything they can try meanwhile.
Open the category
In the dashboard, open Categories, pick the category, and go to its Messages tab.
Write the title and description
Title defaults to "Ticket Created". Description takes Discord markdown and variables.
Pick a color
Leave Embed Color empty to use the server default from Settings → Appearance, or pick a color for this category.
Save and test
Click Save Changes, then open a test ticket to check the variables filled in.
An example description:
Thanks for opening a ticket in **{{category.name}}**, {{user.mention}}.
Please describe the issue in as much detail as you can, including any error
messages or screenshots. A member of the team will reply here.
**Ticket:** #{{ticket.number}}
The intro message can use everything about the opener and the ticket, any answers a support flow collected before the ticket opened, and the results of the category's lookups, such as a linked Steam or Roblox account. See Linked accounts, lookups and bans for the full list.
Closed message and DMs
The Closed Message card replaces the default "This ticket has been closed by {{user.mention}}." notice. Leave it empty to keep the server-wide text from Localization.
The Direct Messages card has three DMs, each with its own title and message:
- When the ticket opens goes to the creator.
- When the ticket closes goes to the creator. It is separate from the ratings DM in Settings, so a member gets both if both are on.
- When someone is added goes to the person added, whether by
/add, the Add User flow step, or the dashboard.
The Variables button on each message lists exactly what it accepts. The DMs also take {{ticket.link}}, which is useful because a DM has no channel to click.
Panel embed
The panel embed is built in the Embed Builder on the panel's page: author, title, description, color, timestamp, thumbnail, image, up to 25 fields and a footer. See Embed anatomy for where each part appears.
No ticket exists when a panel is posted, so a panel can't use user or ticket variables. Its title, description and footer can use {{guild.name}}, the channel it is posted in ({{channel.name}}, {{channel.mention}}), and your custom placeholders.
An example panel:
Title: Need support?
Description: Pick the option that matches your question and a private
ticket opens for you.
**Response time:** usually within a few hours
Field: Before you open a ticket | Check #faq first (inline)
Footer: Acme Support
Color: #3498DB
Panel footers on the Free plan
Free panels show a "Powered by ticket-tool.app" footer in place of your own. On Community and Pro, the footer you write is shown.
Tips
- Keep one color across a category's panel and intro message, so the ticket reads as one experience.
- Put your logo in the thumbnail or footer icon rather than the main image, which pushes the buttons down.
- Say what each panel button is for. A member who picks the right category gets a faster answer.
- Test with a real ticket. The intro preview shows variables as you typed them, so only a real ticket shows what they fill in.