Add to Discord
Onboarding is the part of a server that gets the least attention and decides the most. Someone clicks your invite, spends about a minute deciding whether this is a place for them, and then either says something or never opens the tab again. Nothing you do afterwards reaches the ones who chose the second option.
The useful thing about that minute is that it is short and completely under your control. This guide is what to put in it.
What actually happens when someone joins
Discord drops a new member into the first channel they have permission to read. They see a conversation already in progress between people who know each other. They have no idea whether it is polite to interrupt, whether the server is active or this is the only conversation of the week, or what they are supposed to do next.
So they do the safest thing, which is nothing.
Almost nobody leaves a server. They just never come back, which looks the same in your member count and nothing like it in your channels.
A good onboarding answers four questions before they have to ask any of them. In order, because the order is what makes it feel like a path rather than a wall:
What is this place?
One or two sentences. Specific enough that somebody could repeat it to a friend. Not your values, not your history — what happens here.
What are the boundaries?
Short rules in plain language. This is not really for the reader — most people skim them. It is so that when you enforce something later, there is a thing to point at. Rules you can copy.
Where do I go?
Name one channel. Not a tour of nine. The single most effective onboarding sentence in existence is some version of "say hi in #general", because it converts a reader into a participant in one step.
What do I pick?
Optional roles — games, regions, ping preferences, colours. This is where somebody stops being an anonymous member and starts being a person with a stake in the place.
Use Discord's built-in Onboarding if you can
Discord ships a native onboarding flow, and it is better than anything a bot can draw because it happens before the member reaches any channel. They answer a few questions and land in a server already shaped around their answers, with the channels they picked and the roles that go with them.
Two things to know before you plan around it:
- Your server has to be a Community server. That is a switch in Server Settings, and it brings its own requirements — a rules channel, a moderation-updates channel, verification and content filter levels.
- Onboarding itself needs at least seven default channels, five of which
@everyonecan view and post in. A small server built on the "start with six channels" advice will not qualify yet, and that is fine — it is a reason to wait, not a reason to make eleven channels. - It can only be configured on desktop.
Onboarding and a welcome message are not alternatives
They do different jobs and the difference is worth being precise about. Onboarding handles the choices — which channels, which roles. A welcome message handles the greeting, and a greeting is what makes a room feel occupied.
A server where a real name appears the moment somebody joins reads very differently from one where they arrive in silence, even when the silence is technically well organised.
The welcome message
Short, specific, and pointed at one thing. The failure mode is writing it for yourself rather than for them — a paragraph about the community's spirit, when what the reader needs is a name and a door.
- Welcome to the server! Please read the rules and enjoy your stay!
- A new member has joined. We now have 248 members!
- Welcome @kira! We hope you have a great time here! Make sure to check out all our channels!
- Welcome @kira — sessions are Tuesdays 8pm UK, planned in #sessions.
- Hey @kira. Post what you are working on in #wip, we critique on Sundays.
- Welcome @kira. Grab a game role in #roles so you get pinged for the right things.
Public message or DM?
| In a channel | As a DM | |
|---|---|---|
| Who reads it | Existing members, mostly | The new member, mostly |
| What it is good for | Making the server look alive and welcoming | Actually delivering information |
| What it costs | Noise in #general if you are growing fast | Nothing, but many people have DMs from servers turned off |
| Best used for | A one-line greeting with a mention | The longer orientation — rules, where to go, what to pick |
The honest answer for most servers is both, doing different jobs: a one-line public greeting so the room looks inhabited, and a DM with the actual orientation. If you only pick one, pick the public one — a DM that does not arrive helps nobody, and a visible greeting at least tells the other members somebody new is here.
Auto-roles, and the one case they matter
An auto-role is a role handed out the moment somebody joins. For most servers it does nothing useful — everyone has it, so it distinguishes nobody, and @everyone already exists for "all members".
It earns its place in exactly two situations:
- You want a channel visible to members but not to raiders. Give the auto-role a short delay or pair it with Discord's verification level, and the channel is invisible to accounts that join and leave in the same minute.
- You need something to hang permissions on that is not
@everyone. Occasionally cleaner, particularly if you ever want to lock the whole server down quickly.
Outside those, skip it. A role every member has is a role that tells you nothing, and it will sit at the top of your role list forever looking like it means something.
Measuring whether it works
Onboarding is unusual in that it has a real metric and almost nobody looks at it: what fraction of new members say anything at all?
You do not need analytics for this. Scroll back a week in #general and count the names that appear for the first time against the joins you got. If it is under about one in five, the problem is the first five minutes and not the server.
- Nobody posts after joining — they do not know where, or it feels like interrupting. Name one channel explicitly and reply to everyone who does post, fast.
- People pick no roles — the picker is too far down, or there are too many options. Move it up; cut it to the ones that change what someone sees.
- People join and leave within minutes — usually the invite promised something the server does not deliver, not an onboarding failure at all.
- People post once and never again — nobody replied. That is the whole cause, in almost every case.
Frequently asked
Do I need to make my server a Community server?
Only if you want the native Onboarding flow, Server Discovery, or announcement channels. It also brings requirements — a rules channel, a moderation-updates channel, and minimum verification settings. For a server under a few hundred members, a locked #welcome channel and a good greeting cover the same ground.
Should the welcome message ping the new member?
Yes, if it is in a channel — a mention is what makes it register as addressed to them rather than as bot noise. Never ping @everyone or a role; it fires on every join.
How many roles should I offer in the role picker?
Enough to be useful, few enough to read without scrolling. If a role does not change what someone sees or gets pinged for, it is decoration — which is fine, but put the functional ones first.
Is a verification step worth it?
For a server dealing with raids or spam, yes — but Discord's own verification levels and rules-screening usually do the job without a bot. A custom "react to verify" gate adds a step for every genuine member to stop bots that mostly do not read it anyway. Add it when you have an actual problem.
What is the single most important part of onboarding?
Naming one channel and telling people to post in it. Everything else is an improvement on the margins; that one sentence is the difference between a member and a visitor.
Next
If you are writing the greeting now, there are welcome messages you can copy with the variables that actually work. If new members are arriving and vanishing despite all of this, why members leave covers the causes that are not onboarding.