Slack community onboarding checklist — every step from pre-join prep through week 2

The pre-join phase is what most operators skip entirely because the member has not arrived yet and there seems to be nothing to do. In practice, this phase determines the quality of everything that follows. An unprepared day-0 response is slower, more generic, and less likely to produce activation than a day-0 DM you wrote in advance.

• Signup form includes a goal field. Add one open-text question to your payment or registration form: “What is the one thing you most want to get out of this community?” This field is the raw material for personalisation in every subsequent touch. Without it, you are writing generic DMs to a generic member; with it, you can address the member’s specific stated objective from the first sentence. If you are using Stripe + Memberstack, this is a custom metadata field. If you are using Circle, Mighty Networks, or a native intake form, it is a standard onboarding question.
• Day-0 DM template written and ready. Write your day-0 DM template before any new member joins, not in response to each join notification. The template has three components: (1) a specific acknowledgement tied to the goal field (“You mentioned wanting to [goal] — that’s one of the most common things people come here for”); (2) one narrow first-action ask tied to that goal (introduce yourself in #intros and mention [specific relevant thing] — not three asks, one); (3) a reply-triggering offer (“If you want a pointer to the two or three channels most relevant to [goal], just reply and I’ll send them over” — this creates a low-friction reply that starts the conversation). A day-0 DM template that exists in advance means you can send within two hours; one you write on the fly arrives six hours later or the next morning.
• Tracking spreadsheet row added on payment confirmation. Before the member joins Slack, add them to a five-column tracking spreadsheet: member_name, join_date, day_0_sent (date), day_3_sent (date or SKIP—already_posted), day_7_sent (date or SKIP—already_posted). This row is the source of truth for which members need which touch and when. Creating it at payment confirmation, not at Slack join, means you catch the gap between payment and workspace acceptance — some members pay and never actually join.

Day 0 is the moment a new member first experiences the community as something that noticed them specifically, not just a workspace they landed in. The two-hour window is not arbitrary: members who receive a personalised DM within two hours of joining have substantially higher activation rates than members who receive the same DM the next morning. The first few hours in a new paid community are high-anxiety; the member is wondering whether the price was worth it and whether they belong. A timely, specific DM answers both questions.

• Send within 2 hours of Slack join. Set up a notification for new member joins — Slack can email you on every new member join if you configure workspace notifications. The goal is to see the join within 30 minutes and send the DM within 2 hours. If you cannot do that during working hours, consider batching: check once in the morning and once in the evening, and aim for under 8 hours on off-hours joins. The quality-of-personalisation benefit degrades significantly above 24 hours.
• Three-component structure: acknowledgement, one ask, one offer. The acknowledgement is goal-specific (“You mentioned wanting to [goal from signup form]”). The ask is one action only — introduce yourself in #intros and mention [specific thing related to goal]. Not three actions. Not “explore the channels and post when you feel ready.” One narrow ask that the member can complete in three minutes. The offer is a reply trigger: a genuine, low-effort next step they can get by replying to the DM (“reply here and I’ll send you the two most relevant channels for your goal”).
• Do not include: link lists, channel indexes, or more than one ask. The single most common day-0 DM mistake is the information dump — a DM that lists every channel, links to the welcome doc, explains the community norms, and ends with “let us know if you have any questions.” This DM is trying to answer questions the member has not yet asked and creates cognitive overload at the exact moment the member most needs a clear single next step. Save the channel index for the reply after they take their first action. The welcome doc is for members who explicitly ask where to find norms. The day-0 DM is a narrow, specific activation prompt, not a community guide.
• Update tracking spreadsheet: day_0_sent = today’s date. Mark the tracking row immediately after sending. This is the flag that day-3 logic reads: if day_0_sent is set and day_3_sent is not set, and the member has not posted, they need a day-3 nudge.

Day 3 is conditional: check whether the member has posted before sending. Members who posted in the first three days after your day-0 DM should receive no day-3 message — they activated, sending an additional nudge is unnecessary and slightly awkward. The day-3 message is for the roughly 50–70% of members who received the day-0 DM, may have replied, and have not yet introduced themselves or posted in a channel.

• Check post status before sending. Go to Slack Analytics or manually check the member’s profile — recent messages will show if they have posted. Do not send the day-3 DM to a member who has already posted anywhere in the workspace, regardless of whether they completed your specific day-0 ask. Any posting is a signal of activation; the specific channel matters less than the fact of participation.
• Reframe, do not repeat. The day-3 DM must not be a copy of the day-0 message. A repeat DM signals to the member that the system sent it, not a person — and therefore requires no response. The reframe focuses on a different component of their stated goal: if day 0 suggested introducing themselves in #intros, day 3 might surface a specific thread from the last three days that is directly relevant to their goal (“There was a thread yesterday about [specific topic from their goal area] that I thought you’d find useful — I linked it below”). This brings them back to a specific, valuable reason to open Slack, not just another nudge to complete their introduction.
• Use a different voice register. Day 0 is welcoming and directional. Day 3 should feel more informal and slightly more conversational — like a follow-up from a colleague who noticed they hadn’t seen you around yet, not a reminder from an onboarding system. One technique: make the day-3 DM shorter. A two-sentence day-3 message (“[Member], I came across a thread that’s directly relevant to [their goal]. [Thread link]. Worth a read.”) often outperforms a three-paragraph reminder because it reads as a genuine human observation, not a workflow step.
• Update tracking spreadsheet: day_3_sent = today’s date OR SKIP—already_posted. Both outcomes are tracked. The SKIP notation tells you the member activated between day 0 and day 3 and no further intervention is needed. The date tells you day-7 logic now applies.

Day 7 is the most frequently skipped step in the checklist — and the one with the highest marginal return. By day 7, a member who has not posted has received two personal DMs and taken no visible action. The instinct is to stop: they’ve clearly lost interest, another message would be pushy, the silence speaks for itself. That instinct is wrong. Data from paid community operators who add the day-7 escalation consistently shows that 40–60% of silently non-posting members respond to the day-7 message — and of those who respond, a meaningful fraction do go on to post and remain active subscribers.

• Check post status before sending (again). Some members post between day 3 and day 7 without responding to the day-3 DM. Check before sending. If they posted at any point in the workspace in the last seven days, update the tracking spreadsheet as SKIP—already_posted and send no further onboarding messages.
• Acknowledge the silence explicitly. The day-7 DM should not pretend the previous two messages did not happen. “I noticed you haven’t had a chance to post yet” is not passive-aggressive — it is honest, and it signals that a person noticed rather than a workflow triggered. Pretending the silence did not happen (sending another cheerful activation prompt) makes the message feel automated and produces lower response rates.
• Remove social obligation. The framing that works: “That’s completely fine — these communities can be hard to find time for, especially in the first week.” This sentence does two things: it removes the social pressure of having not posted (reducing the guilt-barrier to responding), and it signals that you will not be offended by an honest answer. Members who would otherwise cancel silently because they feel too awkward to admit they haven’t engaged will often respond to this framing.
• Ask a binary diagnostic question. End the day-7 DM with a single binary question: “Still interested in [specific topic from their goal], or did something change?” The two-option structure (yes or something changed) makes responding extremely low-effort — the member can reply with a single word — and the responses surface the two most actionable outcomes: either they re-engage, or they tell you why they didn’t, which is information you can use to improve your onboarding or your product.
• Update tracking spreadsheet: day_7_sent = today’s date. After day 7, the formal onboarding sequence is complete. Members who remain silent after the day-7 message are low-probability activations. Remove them from your active onboarding tracking and flag them for a 30-day re-check (some will re-engage when the community posts something directly relevant to their goal; this is a passive outcome rather than an active intervention).

Week 2 is frequently misunderstood as a continuation of the onboarding sequence. It is not. Week 2 addresses a structurally different failure: the month-two retention cliff. A member who activated in week one — posted, subscribed to channels, replied to a thread — can still go quiet by week four if the community’s content cadence does not give them a regular reason to return. Week 2 is the bridge between first-week activation and month-two engagement habit.

• Operator scan: who activated versus who is still silent. At the end of week one, run a quick scan of the tracking spreadsheet for all members who joined in the last seven days. Activated members (any post in the workspace) need a different week-2 experience than silent members (responded to day-7 DM but have not yet posted, or no response to day 7). This scan takes three minutes and produces the two-segment action list.
• Activated members: introduce them to one other member or thread. The highest-value week-2 action for an activated member is a specific connection — a DM that says “I saw your intro and thought you should know [other member] works on exactly this. They posted about [specific thing] in #channel last week.” This is a relationship broker intervention, not an onboarding prompt, and it builds the community habit that sustains engagement through month two and month three. It also signals to the member that the operator reads their posts — which is a retention signal of its own.
• Silent members (responded to day 7 but have not yet posted): lower the floor for first participation. Some members want to participate but are blocked by the activation hurdle of introducing themselves in #intros. The week-2 intervention for this segment is to lower that hurdle directly: a brief DM asking for their reaction to a specific thread (“There’s a quick question in #channel that I thought you’d have a good answer for — would you be willing to drop a reply? Just two sentences would be great.”). A reply to an existing thread is a lower-stakes first post than a fresh introduction, and it can break the silence that the day-7 acknowledgement started to address.
• No week-2 message for members who ignored day 7. Members who did not respond to the day-7 escalation should receive no further active onboarding messages. They have been contacted three times with personalised DMs. Additional messages are unlikely to activate them and may create a negative impression that accelerates cancellation. The correct posture: maintain a passive watch. If they post in the next 30 days in response to a community thread that is directly relevant to their goal, note it and resume normal engagement. If not, plan for a 30-day re-check and a possible winback when you have new content that matches their original stated goal.