Guide · September 1, 2026 · 3 min read

The welcome: one minute to convince

A new member decides in under a minute whether they stay or close the tab. What they see at that moment — a channel, a message, a list of rules — weighs more than everything the server offers afterwards.

The message has to say what to do

“Welcome to the server, have fun!” is useless. The new member sees a list of thirty channels they know nothing about, and has no reason to write in one rather than another.

A good welcome message contains an action, not a formula. Three forms work:

• Point them to a specific channel: “Drop by #introductions, someone will answer.”
• Ask a question: “Tell us how you found your way here.”
• State the next step: “Pick your roles in #roles to see the rest of the server.”

The third is the best when the server hides some of its channels: it explains why there is so little to see, which is otherwise the leading cause of people giving up.

To mention or not to mention

Mentioning the new member in the general channel makes them visible and draws replies. That works up to a certain server size: beyond a few arrivals an hour, the general channel becomes a run of welcome messages nobody reads, and ongoing conversations get chopped up.

The practical threshold sits around ten arrivals a day. Below that, welcoming in the general channel works. Above it, a dedicated arrivals channel becomes necessary — even if the message is seen less there.

The welcome image

A card carrying the member's avatar has a real effect: it gives the impression somebody prepared something, where a text message looks like a notification. On community servers, it is often the first thing newcomers mention.

Two technical points deserve attention. First: the avatar is fetched from Discord's servers, which hiccup from time to time. A decent system retries and, if it keeps failing, draws a fallback badge rather than giving up on the image — a welcome that falls back to text one time in ten gives the impression that nothing works.

Second: the background has to stay readable with a long username. A template tested only with “Bob” overflows the moment somebody with a twenty-five-character name arrives, and that happens on the very first day.

What makes people leave

1. A wall of rules on arrival. Nobody reads fifteen rules before deciding to stay. Three lines at the door, the full rules in a dedicated channel.
2. No visible channel. A server entirely locked until verification looks like a closed door. Leave at least one readable channel.
3. An automatic private message. It lands in an inbox full of spam and looks exactly like what malicious accounts do. Many members ignore it by reflex, and rightly so.
4. Three bots saying welcome. More common than you would think, and it does not inspire confidence.

And departures?

Announcing departures in a public channel is a bad idea in almost every case: it stages a loss, invites commentary, and brings nothing. The useful trace — who left, when — belongs in the moderation logs, not in the general channel.

Frequently asked questions

Do I need a separate arrivals channel?

Beyond about ten arrivals a day, yes. Below that, the general channel stays more effective because somebody answers.

Can the message be tested before switching it on?

Yes, and you should: it is the only way to see what the image looks like with a real avatar and a real username, rather than with a generic preview.

Should the message mention the rules?

One line, with a link to the channel. The full rules on arrival never get read.

What about bots that join?

Exclude them from the welcome. A welcome message for a bot is the kind of detail that makes people say the server is badly set up.

Read next : Auto-role, Captcha and verification, Server rules.