Discord application rejection message templates
Ten rejection messages to copy, and how to say no so that a good applicant comes back and a bad one doesn't argue.
- Free plan
- Free Premium trial
Copy these messages
Replace the words in brackets. They work for staff, team, partnership or member applications.
- Thanks for applying to [server]. We've decided not to move forward this time. We appreciate the time you took, and you can apply again in [30 days].
- Thanks for your application. We had a lot of strong candidates and we can't accept everyone. You're welcome to apply next time we open recruitment.
- Thanks for applying. We're looking for someone with more experience in [moderation / this role] right now. Stay active on the server and try again in [30 days].
- Thanks for applying. We need someone available [on weeknights / during EU hours], and your schedule doesn't match this time. If that changes, apply again.
- Your application was too short for us to decide. Tell us more about [your experience / how you'd handle the scenario], and you can apply again after [7 days].
- Your account or time on the server doesn't meet our minimum yet. You can apply again once you've been here for [30 days].
- We've filled the spots for this round. We've kept your application, and we'll post here when we open again.
- Thanks for reaching out about a partnership. Your server isn't the right match for us right now, because [different audience / too small for an exchange]. We wish you all the best.
- We reviewed your ban appeal and the ban stays in place. This decision is final, and further appeals won't be reviewed.
- We won't be accepting your application, and we won't review new ones. Please don't contact staff about this decision.
Which one to use
- Messages 1 and 2 are the default for a good applicant you simply can't accept. Keep them warm.
- Messages 3 to 6 give a reason the person can act on. They're the ones that bring back better applicants.
- Message 7 fits a wave of recruitment that's full: it isn't about the person at all.
- Message 8 is for partners, who often run a server of their own and will remember how you treated them.
- Messages 9 and 10 close the door. Use them rarely, and only when you mean it.
What a good rejection does
A rejection has three jobs: to give a clear answer, to protect your staff from an argument, and to leave the door open when that's what you want. A two-line message sent within a few days does more for your reputation than a long one sent after a month.
Say who decided as a team, not as a person. "We" keeps the moderator who clicked Decline out of a private argument.
What to avoid
- Silence. A clear no lets the person move on.
- Personal judgments. "You seem immature" invites a fight, and it may get screenshotted.
- Details about other applicants. Never compare people.
- Promises you can't keep. Don't write "we'll contact you" unless someone really will.
- Fake reasons. Applicants on the same server talk to each other.
- Too much feedback. A rejection isn't a performance review. One reason is enough.
How to reply when someone asks why
For most applicants, a single honest sentence is enough: the reason, then what they can do next. If they keep going, stop replying and let the cooldown do the work. Write one team rule for this, so that no moderator has to improvise at midnight.
In Toscio
In the form editor, you can save up to 10 preset decline reasons per form, such as "Application too short" or "Not enough experience". When a reviewer clicks Decline, they pick one or type their own. The applicant gets it by direct message, in their Discord language, or on their page for a web application. Your cooldown tells them when they can apply again, and Block this member covers message 10. It's all in the free plan. See reviewing applications.
Questions
Should I always give a reason?
Give a short one whenever you can. A reason that is general and true ("we're looking for more moderation experience") is better than silence. Don't list personal flaws, and don't debate it.
Should I send rejections by DM or in a channel?
By DM, or on the applicant's page for a web application. Never decline someone in a public channel.
What if the applicant argues?
Answer once, calmly, and stop. A decision that changes under pressure teaches everyone to argue. Point them to when they can apply again.
