Opening context
.ticket open-message is rendered when the ticket opens and receives ticket.*, user.*, guild.*, and channel.* values supplied by that event. Missing values render as N/A; the full list is in Ticket variables.
Simple conditions, Tickets only
The opening message supports{if condition}, {elseif condition}, {else}, and {/if}. A condition can test {variable} for truth or compare {variable} == value / {variable} != value; expressions, additional operators, and nested blocks are not supported. At most one {else} is allowed, and every block must close with {/if}.
.ticket open-message
.ticket open-message {if {ticket.open} == yes}Ticket is open.{elseif {ticket.closed_automatically} == yes}It closed automatically.{else}Ask support.{/if}
Conditions are available only in the Tickets opening message; incomplete or nested blocks fail validation.
Configure and validate
.ticket open-message <message> stores text or an embed template using the same context. Test with a ticket first; incomplete syntax, invalid conditions, or unknown variables stop the template rather than executing code.
Steps
1
Choose the context
Conditions are evaluated only in the Tickets opening message; do not use them in Welcome, Auto Responder, or other templates.
2
Write simple branches
Compare a documented variable with
== or !=, optionally add a fallback branch, and do not nest conditions.3
Test the message
Open a test ticket and review the selected branch, variables, and embed before announcing the panel.