Ticket forms
Questions a ticket panel asks in a pop-up before the ticket opens, and how the answers show up.
Why a form
Without a form, every ticket starts with "hi" and staff spend the first three messages asking what it is about. A form asks up front, and the answers are posted as the first message in the ticket.
Writing the questions
/ticket form panel:<name> opens an editor with one question per line. Discord allows five inputs per pop-up, so at most five lines are used; extra lines are dropped.
- * at the start
- Makes the question required.
- | after the question
- Text after the bar is the placeholder shown inside the box, e.g. "*Order ID | e.g. NOVA-0042".
- (long) at the end
- Turns the box into a multi-line paragraph field.
- Label length
- Labels are cut at 45 characters, which is Discord's limit for input labels.
Per panel
Forms belong to a panel, so a Sales panel can ask for a product and budget while a Support panel asks for an order ID. Dropdown (V2) panels use the form of whichever panel the member picks. The same editor is on the Ticket Panels page of the dashboard.
Where the answers go
The answers are posted as an embed in the new ticket, one field per question, and are included in the transcript. If AI ticket help is on, the AI sees the answers too.
Removing all lines turns the form off; the panel then opens tickets immediately on click.