Skip to main content

Intake forms: what to ask before a ticket opens

How to build a Discord ticket intake form: up to 5 fields, the right field type for each question, and ready-made sets for payments, bugs, reports and more.

Discord Tickets team6 min read

The slowest ticket starts with “Hi, I have a problem”, followed by several messages of finding out which one. An intake form fixes that before the ticket exists: the member clicks the button, Discord shows a window with your questions, and the ticket is created only after they submit. Your team opens the channel already knowing what it is about.

Below: principles, field types, and ready-made question sets for common topics.

Why use an intake form

  • A useful first reply. Staff skip the clarifying round and go straight to checking the order or reproducing the bug. More on why that matters in our piece on first response time.
  • Fewer empty tickets. The form is a light filter: someone who clicked just to see what happens will close the window instead of creating an empty channel.
  • Comparable data. When the problem type is picked from a list instead of typed freely, tickets are easy to sort and review.
  • A personal welcome. Answers can go into the channel name and the bot’s first message — see below.

Principles of a good form

Five fields is a ceiling, not a target

A Discord modal holds up to 5 fields. That is a platform limit, not a goal. Most topics need two or three questions — every extra field is one more reason to close the window and post in general chat.

Ask only what the first action needs

The test: what will staff do with this answer? If nothing, drop the question. “How did you find us?” helps nobody in a payment ticket. Anything else can be asked later in the conversation.

Required vs optional

Make a field required only if work cannot start without it: the order number, the bug description, the person being reported. Make everything required and people start typing “-” and “no” — you get less useful information, not more.

Choices beat free text

If the answers fall into a known set — platform, problem type, payment method — let people pick. Keep free text for describing what happened. Picking is faster for the member and unambiguous for the team: “PC”, “pc”, “computer” and “desktop” collapse into one option.

Placeholders and length

The placeholder shows the expected format: “e.g. 10482” or “What you did, what you expected, what happened”. A minimum length filters out answers like “broken” — 20–30 characters is a reasonable floor for a problem description. A maximum keeps short answers short where you need a number or a username.

Keep questions short — “Order number”, not “Please provide the number of your order”. Explanations go in the placeholder.

Tip. Never ask for passwords, card details or email codes in the form. If the topic is about payments, add a Static text field reminding people your team never asks for that.

Which field type for what

Field type Use it for Example question
Text — short Short answers: number, username, ID Order number
Text — paragraph Describing a situation Describe the problem
Dropdown Picking from a long list, multiple picks allowed if you want Which game mode?
Single choice A few mutually exclusive options, all visible Platform
Checkboxes Ticking everything that applies What have you tried?
Checkbox A confirmation I have read the FAQ
Pick members Naming a person without typos Who broke the rules?
Pick roles Which role is needed or broken Which role is missing?
Pick channels Where it happened; the list can be restricted Which channel?
Static text An explanation with no answer Attach screenshots in the ticket

Static text takes up a slot too, and at least one field has to accept an answer.

Ready-made question sets

Payments and orders

  1. Order number — Text (short), required, placeholder “e.g. 10482”.
  2. What happened — Single choice: Item not received, Payment error, Refund, Other.
  3. Details — Text (paragraph), optional.
  4. Static text: We never ask for passwords or card details.

Bug report

  1. Where is the bug — Dropdown: Website, Bot, Game, Other.
  2. Steps to reproduce — Text (paragraph), required, minimum 30 characters, placeholder “1. Opened… 2. Clicked… 3. Saw…”.
  3. What you expected — Text (paragraph), optional.
  4. Platform — Single choice: PC, Mobile, Browser.

Screenshots and recordings are easier to attach once the ticket is open — say so in the welcome message.

Member report

  1. Who broke the rules — Pick members, required.
  2. Where it happened — Pick channels, optional.
  3. What happened — Text (paragraph), required.
  4. Message link — Text (short), optional.

For setting up a dedicated report topic with strict closing rules, see member reports through private tickets.

Game or server question

  1. Question is about — Dropdown: Rules, Roles, Events, Gameplay, Other.
  2. In-game name — Text (short), optional.
  3. Your question — Text (paragraph), required.
  4. Checkbox: I checked the FAQ and pinned messages.

Applications

Works for staff recruitment, partnerships or event sign-ups.

  1. Which role — Single choice: Moderator, Helper, Event host.
  2. Experience — Text (paragraph), required, minimum 50 characters.
  3. Time you can give — Single choice: Under an hour a day, 1–3 hours, More than 3 hours.
  4. Checkbox: I have read the rules and requirements — a confirmation, not required.

The whole recruitment flow is covered in staff applications through tickets.

Using answers in the channel name and welcome

The {field:Question} placeholder inserts the answer to the question with that exact text. For the payments set above:

  • channel name: order-{field:Order number} — the channel list shows which order each ticket is about;
  • welcome message:
{opener}, thanks for reaching out.
Order: {field:Order number}
We will check the payment and reply here. Feel free to attach a receipt.

Two caveats. The text inside the braces must match the question — rename one, update the other. And the channel name template applies to the whole panel, while each topic has its own form: if you use {field:…} there, keep that question in every topic of the panel, or stick to {topic} and {counter}.

No need to repeat every answer in the welcome: the bot posts them in the ticket when Include the intake answers is on (the default). One or two placeholders are enough.

How it works in Discord Tickets

In the dashboard, each topic of a panel has its own intake form, edited right in the modal preview — exactly as members will see it, with required, placeholder and length set per field. Step-by-step with video: the Intake form section of the docs, and placeholders for the first message in Welcome message.

Checklist

  • 2–4 fields, not 5 just in case.
  • Every question serves the first action your staff will take.
  • Only what blocks the work is required.
  • Where answers are known in advance — a choice, not text.
  • Text fields have a placeholder and a sensible minimum length.
  • No questions about passwords or payment details.
  • Questions used in {field:…} match the form text exactly.

Read next

All posts →