Discord Staff Application Template: Questions That Find Good Moderators

Copy and paste staff application questions for moderators, support staff and event teams, scenario questions with a scoring guide, and the setup that runs the whole thing inside Discord.

Most Discord staff applications are a form somebody copied from another server years ago. They ask for your age, your time zone and why you want to be staff, and then the owner picks whoever wrote the longest answer. The longest answer predicts exactly one thing: who is best at writing long answers.

A good application does three jobs. It filters out people who will never fit before anyone spends time on them, it shows you how a candidate behaves in situations your server actually has, and it respects the applicant's time enough that the good ones finish it. This page gives you the questions for all three, a way to score the answers, and a setup that runs the whole thing inside Discord instead of in a spreadsheet.

Every question below is under 100 characters, so it pastes straight into most application bots, Tickety included. Pick 10 to 15 of them. Nobody good finishes forty.

How to build the application

  • Start with gates, not essays. Two or three multiple choice questions up front (time in the server, availability, have you read the rules) tell you whether the rest is worth reading.
  • Ask about behaviour, not opinions. "What makes a good moderator?" gets the same paragraph about being fair and patient from every applicant. "A friend of yours breaks a rule, what do you do?" gets answers that actually differ.
  • Steal scenarios from your own server. The best scenario questions are the things that went wrong last month. Change the names and ask them.
  • Only collect what you need. You do not need a real name, a birthday or a photo. If age matters for the role, ask a yes or no question about a minimum.
  • Say how long it takes and when people hear back. Put both in the message before the first question. It lowers the number of "any update?" pings more than anything else you can do.

Section 1: The basics

Short and multiple choice where possible. These are the answers you read first, and they decide whether you read the rest.

  1. How long have you been a member of this server?
  2. Which time zone are you in?
  3. How many hours a week can you realistically give this role?
  4. Which days and times are you usually online?
  5. Are you 16 or older?
  6. Have you read the server rules and the staff guidelines?
  7. Have you ever been warned, muted or banned here? If so, tell us what happened.

Make question 1 multiple choice (under a month, one to six months, six to twelve months, over a year) and question 5 a plain yes or no. Ask the age question only if the role needs it. Question 7 is not a trap. Someone who answers it honestly and explains what changed is often a better candidate than someone claiming a clean record you can check in thirty seconds.

Section 2: Experience and motivation

  1. Have you been staff in another Discord server? Which one, and what did you do there?
  2. What is one thing about this server you would change, and why?
  3. Which channels do you spend the most time in?
  4. What would you do in your first week on the team?
  5. Why this role, and why now?
  6. Have you used moderation or ticket bots before? Which ones?

Question 9 is the most useful one in this section. A candidate with a concrete, kind suggestion has been paying attention. One who says the server is perfect is telling you what they think you want to hear.

Section 3: Scenario questions

This is the part that actually predicts behaviour. Ask four to six. If your bot has a description field under each question, use it to add detail that your server would recognise.

  1. A member posts a free Nitro link in three channels. What do you do, in order?
  2. A close friend of yours in the server breaks a rule. What do you do?
  3. Another staff member is being rude to members. How do you handle it?
  4. Two members are arguing in general and it is getting personal. Walk us through it.
  5. A member says in a ticket that they are not safe. What do you do?
  6. Twenty new accounts join in a minute and start spamming. What are your first steps?
  7. A member says your warning was unfair and keeps pinging you about it. What do you do?
  8. You are the only staff member online and a ticket needs an admin. What do you do?
  9. Someone asks you for a screenshot of a staff channel. How do you reply?
  10. A member reports someone for DMs but has no screenshots. What do you do?

What a strong answer looks like

Score each scenario from 0 to 2. A 0 would make things worse, a 1 is safe but incomplete, and a 2 is what you would want from someone who has done the job for a year. Read the totals as a shortlist, not a verdict.

ScenarioScores a 2Scores a 0
Nitro link spamDeletes the messages, times out or softbans the account, assumes it may be hacked rather than malicious, checks the other channels, logs it.Argues with the account, or bans it forever without looking.
Friend breaks a ruleApplies the same rule they would to anyone, or hands it to another moderator because of the conflict of interest.Lets it slide, or "talks to them privately" and leaves it there.
Rude staff memberRaises it privately with a senior or the owner, with examples.Calls it out in public, or ignores it.
Member not safeStays calm, takes it seriously, points to local emergency services, brings in senior staff immediately and does not try to carry it alone.Jokes, ignores it, or tries to act as a counsellor on their own.
RaidSlows or locks the channels, removes the accounts in bulk, alerts other staff, then cleans up.Bans one account at a time while the rest keep posting.
Alone with an admin ticketTells the member honestly what happens next and roughly when, leaves a note for an admin, promises nothing they cannot deliver.Closes the ticket, or makes a call above their role.

For the spam scenario, the honeypot approach in our guide to honeypot channels is a good answer to have in mind. Most link spam comes from real members whose accounts were taken over, which is exactly why a permanent ban is the wrong first move.

Section 4: Extra questions for specific roles

Support and ticket staff

  • A member opens a ticket and writes only "hello". What is your first reply?
  • You do not know the answer to a ticket. What do you do?
  • A member is angry about a purchase that went wrong. Write your first reply.
  • When is it right to close a ticket the member has not replied to?

Event team

  • Describe an event you would run here, from announcement to wrap up.
  • Only four people turn up to your event. What do you do?
  • How would you pick giveaway winners so nobody can say it was rigged?

Content creators and partners

  • Link your channel or profile.
  • Roughly how many people see your content each month?
  • What would you make for this community?

Red flags worth reading twice

  • Answers that match another applicant's word for word, or read like a generic essay that never mentions your server.
  • Scenario answers where the first step is always a permanent ban.
  • Motivation that is about the role colour, the permissions or the perks.
  • A long list of servers they moderate, with nothing specific they did in any of them.
  • Pressure: asking for a decision an hour after applying, or getting friends to vouch for them in DMs.

Running it inside Discord with Tickety

A Google Form works, but it costs you three things. You cannot be sure who actually sent it, the answers live outside Discord, and somebody has to hand out the role by hand afterwards. An application bot keeps the whole flow in your server. This is how it looks in Tickety, where applications are part of the free plan.

  1. Start from a template. In the dashboard, open Application Panels and create a panel. The template shelf has Staff Application, Moderator Application, Event Staff Application and Content Creator Application ready made, and everything in them can be changed.
  2. Decide who reviews. Pick a Review Role and a private staff channel for submissions. Each submission lands there with Accept, Deny, User History and Open Interview buttons.
  3. Paste your questions. Use Text Answer for the scenarios and set a minimum length so nobody gets away with one word. Use Multiple Choice for the basics. Free servers can ask 25 questions per panel and premium servers 100, which is far more than any application should need.
  4. Choose where people answer. Apply Method can be Discord DMs, the website, or both. The website form saves every answer as the applicant goes, which matters for long applications and for anyone whose DMs are closed.
  5. Hand out the role automatically. On the Roles tab, give a Trial Staff role on accept. It is applied whether you accept from Discord or from the dashboard.
  6. Post the panel, then apply once yourself before anyone else does.

Two features are worth switching on for staff applications in particular. Open Interview opens a ticket with the applicant straight from their submission, so the conversation before a decision happens in a private channel your team can see instead of in somebody's DMs. AI follow ups let a text question ask up to three follow up questions about the answer that was just given, which is the closest an application gets to an interviewer asking "and then what?". They spend AI credits, so put them on your two best scenario questions rather than all of them.

The full walkthrough with screenshots is in the application panel guide. If Tickety is not in your server yet, add it here; the same dashboard runs your tickets too, and our guide to setting up a ticket bot covers the first five minutes.

After you accept someone

An accepted application is the start of a trial, not the end of hiring. Give new staff a trial role with fewer permissions for two to four weeks, pair them with someone experienced, and tell them in the acceptance note what the trial involves. You can write that note when you press Accept, and set a default once so nobody forgets.

Denials deserve a sentence too. "Your application did not meet our needs" is accurate and tells the applicant nothing. One line about what would change your mind, and when they can apply again, turns a rejected applicant into someone who comes back in three months as a better candidate.

Frequently asked questions

How many questions should a Discord staff application have?

Ten to fifteen. That is enough for a few basics, a few questions about experience and four to six scenarios. Past twenty, the people who finish are the ones with the most free time, not the best candidates.

Should I ask applicants for their age?

Only if the role needs it, and only as a yes or no question about a minimum, such as "Are you 16 or older?". You do not need a date of birth to decide, and you should not be storing one.

Is Google Forms or a Discord bot better for staff applications?

A form is fine for a one off. A bot knows who applied without asking for a username, keeps the answers in Discord, lets your team accept or deny with a button and can give the role automatically on acceptance. Tickety does all of this on the free plan.

Can people apply without opening their DMs?

Yes. In Tickety, set the panel's Apply Method to Website or Both and applicants answer in their browser instead. With Both, anyone whose DMs are closed is offered the website automatically.

How do I stop the same person applying every day?

Set an Application Submission Cooldown on the panel and keep Max Pending Applications per User at 1. Cooldowns go up to an hour on Tickety's free plan and up to seven days on premium.

Copyright © 2026 Tickety.top - All Rights Reserved.