Discord Application Bot: Staff Applications in Private Channels

Why not just use a form link

External forms lose people. Applicants leave Discord, forget, or paste an answer from somewhere else. Staff then have to copy answers into a channel to discuss them. Keeping the whole thing inside Discord fixes both: the applicant answers where they already are, and the decision happens where your team already talks.

What the applicant sees

1. They press the Apply button on your panel.
2. The bot creates a channel only that person and your staff role can see, and asks the first question.
3. Each answer, up to 1,000 characters, is saved and the next question follows. If the bot restarts or the person takes a break, the application resumes at the next unanswered question.
4. Typing cancel stops it.
5. When they finish, the application goes to staff, and they get the decision by DM.

The private channel closes about a minute after the last answer.

What staff see

The finished application lands in the review channel with Accept and Reject buttons. Accept gives the accept role, if you set one, so a new moderator can be promoted with one click. Either decision is sent to the applicant as a DM. /application list shows recent applications by status: waiting for staff, accepted, rejected, or still being written.

Set one up

The same settings and the question list are on the dashboard under Community, then Staff Applications.

Rules that keep it tidy

• One open application per person. Pressing Apply again points to the existing channel.
• A cooldown after a rejection or cancel. It runs from 0 to 365 days and defaults to 14. The applicant is told when they can apply again.
• Several forms at once. Each has its own questions, review channel and button.
• Only open applications are offered when you post a panel.

Fewer, sharper questions get finished more often. The default set asks about age and timezone, weekly hours, moderation experience and why they want to join. Replace it with your own.

Questions worth asking

Ask about things you cannot learn from a profile. For a moderator: a hard situation they handled and what they did. For a builder: a link to work they are proud of. For an event host: how many hours they can give each week. Avoid asking for private data such as a real name or an address.

If you suspect a long answer was pasted from a chatbot, /ai check gives a heuristic score. Treat it as a hint only, ask a follow-up question, and never reject on the score alone. See the AI message check docs.

A simple hiring round

Treat applications as a short campaign instead of an always-open door. Open a form for two weeks, post the panel in an announcements channel, and close it when you have enough. When you post a panel, only open applications are offered.

1. Write five to eight questions and delete the ones you would not read.
2. Set the review channel to a private staff channel so rejected people are not discussed in public.
3. Set the accept role to a Trial role, not the full staff role, so you can watch new people before trusting them.
4. Reply to every applicant. Even a rejection DM from the bot is better than silence.

Because the bot needs permission to create channels in the category you choose, check that it can see and manage that category before you post the panel. If an applicant cannot see their channel, the staff role you set is the first thing to check.

Finally, remember that every applicant is a member who might one day apply again. A short, polite reply costs nothing and keeps the door open.

Next steps

All options are in the staff applications docs, and the staff applications guide covers how to run a hiring round. Pair it with warnings for the staff you hire, and see the ticket bot for support. Add Noxyr to start.