Skip to main content

Staff applications through Discord tickets

How to take moderator and helper applications through tickets: a dedicated panel, an application form, who reviews, replying to candidates and close reasons.

Discord Tickets team6 min read

Recruitment often starts with a “DM me if interested” post. A week later the admins have dozens of scattered messages, half the candidates never got an answer, and nobody remembers who approved whom. Tickets fix this without external forms or spreadsheets: the candidate fills in a form, gets a private channel with the people who decide, and the outcome is recorded as the close reason.

Why tickets beat DMs and public channels

  • Privacy. A ticket channel is visible only to the opener and the topic’s roles. Candidates do not read each other’s answers, and a rejection is not public.
  • One queue. Every reviewer sees applications in one place and in the panel’s log channel.
  • Same questions for everyone. Candidates are easy to compare.
  • Room for a conversation. You can ask follow-ups or run a short text interview right in the ticket.
  • A recorded outcome. The close reason is the decision: Accepted or Rejected: ….

A dedicated panel or a topic in your support menu

Dedicated panel Topic in the support panel
Where it lives Its own channel, e.g. #apply-for-staff One option in the shared menu
Who can close, limits, cooldown Its own Shared with support
Quick close reasons Only for applications Shared by every topic of the panel
Log channel Its own Shared with support

We recommend a dedicated panel: advanced settings and quick close reasons apply to the whole panel, and applications need stricter rules than support — only reviewers close, and a reason is required. A server can have up to 3 panels.

Pick the trigger by the number of positions:

  • Button — one position. A single queue, and the member goes straight to the form.
  • Select menu — several positions. Each topic is a position (Moderator, Helper, Event host) with its own form, welcome message and admin roles, so event host applications can go to your event team.

Applications can open as private channels in a dedicated category or as private threads. A thread is locked on close and stays as an archive; a channel is either deleted or kept read-only. Leave deletion off: if someone reapplies, you can compare with their previous application.

Who reviews: topic roles

Admin roles — only the people who make the call, for example Admins and Senior Moderator. These roles get access to the topic’s tickets, a mention when one opens, and the right to close. Regular moderators usually do not need access: the candidate may become their colleague.

Blocked roles — who cannot apply. For example, the Moderator role (already on the team) or a newcomer role if you only recruit from active members.

Tip. Default staff roles from Settings are added to every new topic. Check the applications topic’s roles by hand so your whole support team does not end up in it. More on splitting access in support team roles and access.

Sample application form

Question Field type Settings
How much time can you give the server? Single choice: Under an hour a day, 1–3 hours, More than 3 hours Required
When are you usually online? Dropdown, multiple picks: Morning, Afternoon, Evening, Night Required
Moderation experience? Where and how long? Text, paragraph Required, min 50 characters
How would you handle a fight in chat? Text, paragraph, placeholder: One member insults another, who insults back Required, min 50 characters
I have read the rules and requirements Checkbox Not required, a confirmation

The scenario question is the most useful: it shows how the person thinks and is hard to answer with a template. Experience and availability work as filters; the checkbox is a nudge to read the rules. More examples by field type in intake form questions.

With a single button and several positions you would need a Single choice field for the role — and five fields run out fast, so one topic per position is usually better.

Welcome message

{opener}, application #{number} is under review.
We will reply here in this channel — please do not send it again to admins in DMs.

With one topic per position, add {topic}: Application for {topic}. Form answers are added to the ticket when Include the intake answers is on.

Advanced settings for the panel

Setting Value Why
Who can close Admins only The candidate cannot close it before a decision
Require a close reason On Every decision is recorded
DM the opener why it was closed On The candidate learns the outcome even without checking the channel
Max tickets per member 1 Counts all of the member’s open tickets on the server: someone with an open support ticket can apply once it’s closed. Use 2 if that gets in the way
Cooldown between tickets, seconds 86400 No more than one application a day
Channel name apply-{username} You see whose application it is

The cooldown tops out at one day. If people can reapply only after, say, a month, state it in the panel text and the rejection reason. /ticket ban is too blunt for this: the ban role blocks tickets everywhere on the server, support included. When it does fit is covered in spam protection: limits, cooldowns and bans.

Reviewing and replying

  1. Click Claim under the welcome message. Claimed by … appears, so other reviewers know who owns it.
  2. Read the answers and ask follow-up questions in the ticket if needed.
  3. Discuss the candidate in a staff-only channel, not in the ticket — the candidate sees everything posted there.
  4. Decide and close the ticket with a reason.
  5. Give the accepted candidate the team role the way you normally assign roles.

Quick close reasons

Quick reasons work when only admins can close and a reason is required — the settings above cover both. A set for applications:

  • Accepted
  • Accepted on probation
  • Rejected: not enough experience
  • Rejected: availability does not fit
  • Rejected: incomplete form
  • Rejected: recruitment closed

Up to 5 reasons show as radio buttons in the close form, 6 or more as a dropdown, always followed by Other, where the admin’s text becomes the reason. With the DM setting on, the candidate reads exactly this wording — write reasons you are comfortable sending.

What you see in Discord Tickets

On the Tickets tab, each application has a card with who opened and closed it, when, first response, duration and close reason — effectively a recruitment log. On Overview, By topic shows applications per position over 30 days. Topic and role setup is in the Topics section of the docs; limits and closing rules are in Rules, limits and closing.

Checklist

  • A dedicated panel in its own channel, one topic per position.
  • Topic admin roles limited to decision-makers.
  • Current staff in blocked roles.
  • A form of up to 5 fields with a scenario question.
  • Admins-only closing, required reason, reason sent to the candidate by DM.
  • One open ticket per member (counted per panel), one-day cooldown.
  • Accepted and Rejected: … reasons worded so you can send them as is.

Read next

All posts →