Discord staff application template
Two five-question templates, for staff applications and roleplay whitelists, that fit Discord's form limit, and how to take them as tickets.
Staff application
How old are you?*
What time zone are you in?*
Have you moderated a server before?*
Why do you want to join the team?*
A Discord form holds up to 5 questions, and each question's label up to 45 characters. So a staff application has to pick its questions well, and leave the rest for the conversation.
Staff application template
| Question | Field |
|---|---|
| How old are you? | Text input |
| What time zone are you in? | Text input |
| Have you moderated a server before? | Paragraph |
| Why do you want to join the team? | Paragraph |
| Two members argue in chat. What do you do? | Paragraph |
The last question is a scenario on purpose: how someone handles a real situation tells you more than a list of past roles. Give the paragraph answers a minimum length, such as 100 characters, so a one-line answer can't be sent.
Whitelist application template
For a roleplay server, such as on FiveM, the form checks that an applicant has a character and knows the rules:
| Question | Field |
|---|---|
| Character name | Text input |
| How old are you? | Text input |
| Roleplay experience | Paragraph |
| Character backstory | Paragraph |
| I have read the server rules | Checkbox |
The checkbox shows up in the ticket as ✅ or ❌, so reviewers see at a glance who says they read the rules. A minimum length on the backstory, such as 300 characters, filters out low-effort applications.
Take applications as tickets
With a ticket bot, each application opens a private channel where the applicant and your reviewers can talk it through. In the dashboard:
- On the Tickets page, add a Staff application category to your panel.
- In its General tab, pick only the roles that review applications as its Support team, so other staff don't see them.
- In its Form tab, give the form a title and add the questions. Each one has a label, a short description shown under it, and settings for required, paragraph and length.
The answers are posted at the top of the ticket when it opens. Forms for other categories work the same way.
What if you have more than five questions?
Put the rest in the category's Welcome message, in its Opening tab. It's posted in the ticket as soon as it opens, so the applicant answers there. Keep the questions that filter people out in the form, and the ones that start a conversation in the ticket.
Decide and keep a record
Bring in another reviewer with /add if you want a second opinion. Write the decision in the ticket, then close it: the applicant can still read it, but no longer write in it. With transcripts on, every application is saved, so you can look back when someone applies again.