Ticket inputs
When a member opens a ticket, Clarify shows them a short form. The fields on that form are the inputs you enabled for the category. Ask for exactly what your team needs — an order number, a description, the channel a problem happened in — and every ticket arrives complete.
Inputs are server-wide: you create an input once and enable it in any category that needs it. Editing it changes it everywhere it is used.
Creating an input
In a category's Setup Inputs section, click Create new input. The editor walks through four parts:
Type
Text input, Selection, File upload, Channel select, Role select or User select. Switching the type keeps what still applies (the required flag, and placeholder and limits between the select types).
General
A Name — shown when reusing the input in other categories, and the label members see for every type except text inputs, which have their own label. Required decides whether the ticket can be submitted without an answer.
Settings
The options of the chosen type, listed below.
Preview
The field as Discord will render it. Save is available once every rule below is met.
To change an input later, use the ✎ button next to it in the Active inputs list. The 🗑 button deletes an input for the whole server; it is only offered while the input is not enabled in the category you are looking at.
Input types
Ready-made module inputs
When an integration is active, it offers pre-built inputs that capture exactly the value it can look up. They appear in the Active inputs list with a Module badge, cannot be edited, and turn the member's answer into a lookup card on the ticket instead of a plain field.
| Integration | Inputs |
|---|---|
| Stripe | Stripe Order ID, Payment Intent ID, Charge ID, Checkout Session ID, Customer ID, Customer Email, Subscription ID, Invoice ID |
| Tebex | Tebex Transaction ID, Tebex Subscription Reference, Tebex Basket ID |
| Patreon | Patreon Member ID, Patreon Email |
| Data connectors | The inputs a connector declares; managed by the connector |
Where the answers go
- The ticket's opening card lists every regular answer as a field, so your team sees the context from the first message.
- The first five answers are available as
%tag_input_value_01%…%tag_input_value_05%in the category's messages; the first five text answers also in the thread name. - Answers can feed connector queries as the value of a query input.
- Changing a category's inputs only affects new tickets; open tickets keep the answers they were created with.
Tips for good forms
Ask for the least you can
Every extra field is friction. Trim to the essentials and let staff ask follow-ups in the ticket.
Use a Selection to route
A single "What do you need?" dropdown sorts tickets faster than a paragraph of free text.
Pair IDs with lookups
Running Stripe, Tebex or Patreon? Enable the matching ready-made input and your team gets the full record automatically. Better still, let a connector fill it in with auto-detect.
Mind the five
Ready-made inputs share the five slots with your own. A form that needs more is a sign the category should be split.
Related
Categories
Create and manage ticket categories — each with its own forum, questions, thread naming, messages, connector queries and auto-assignment.
Panels
Build a creation panel — the message with a button per category that members click to open a ticket — and post it into a channel with /generate-creation.