The welcome email drip sequence, one email at a time

When someone joins your organisation, the instinct is to tell them everything at once. Here's your welcome, and here's the members' area login, and the WhatsApp group, and the calendar for the next six months, and the code of conduct, and the committee list, and by the way here's how to book a class and where to park - all crammed into one heroic email that the new member skims for about four seconds and then closes, having absorbed almost none of it. It's a natural mistake, because you're excited they joined and you want them to have the full picture. But nobody reads the full picture in one sitting, and a welcome email that tries to do six jobs usually does none of them well.

A drip sequence is the alternative, and the name makes it sound more technical than it is. Instead of one big email, you send a small handful of shorter ones, spaced out over the new member's first few weeks - each doing a single job, each arriving at roughly the moment it's useful. The "drip" is just that: a slow, steady trickle rather than one bucket tipped over someone's head on day one. It's an old idea from email marketing, but it works for memberships for a plainer reason than any marketing theory - it matches the pace at which a real person actually settles into a new group.

Let me carry one example through so this stays concrete. Say you help run Dapur Nusantara, a community cooking class in Bandung - somewhere around 90 - 120 members, a monthly class night where everyone learns to cook a regional dish together and then sits down at one long table to eat what they made, and a WhatsApp group where people post photos of the rendang they attempted at home and argue cheerfully about whose sambal is best. Every month you get maybe 6 - 10 new members, some dragged along by a friend, some who found you on Instagram and signed up on their own. What happens to those people over their first month is most of what decides whether they're still tying on an apron with you in a year. So this piece is about the email sequence I'd want Dapur Nusantara to run - what to send, when, and what each one is actually for.

Why a sequence beats one big email

The core problem with the one-big-email approach is that a new member on day one can only act on one thing, maybe two. Everything past that is noise they'll deal with "later", and later mostly never comes. A sequence fixes this by only ever asking for one thing at a time, and by asking for it when it's relevant rather than all up front. The login matters on day one; the nudge to come to the next class matters in the week before the class; the "how are you settling in" check-in matters at three weeks, not on the day they joined when there's nothing yet to settle into.

There's a quieter benefit too, and in my experience it's the one that actually holds people. A sequence keeps showing up. A new member who hears from you once and then nothing for eleven months has effectively been told, by your silence, that not much happens here - and they'll believe it. A member who gets a warm welcome, then a friendly nudge a few days later, then something that makes the community feel real, then an invite to the next class, has been shown a membership that keeps gently turning up in their life. That drip of small, well-timed contact is doing the real work. It's not clever, it's just present, and present beats clever most of the time.

This piece is about the scaffolding - how many emails, in what order, on what timing. It's not about the exact wording, because I've done that separately: if you want copy you can lift and adapt for the individual emails, the welcome email templates for new members piece has several, and the copy sketches below are deliberately short pointers rather than full templates. And the sequence itself is only the automated half of a bigger picture - the human moments that sit alongside it (someone actually saying hello at the first class) are covered in the new member onboarding process. Hold all three together and you've got the whole thing; this one is just the email schedule.

Honest caveat, up front

Before the sequence, the single most important thing about drip sequences: a short one that actually goes out beats an elaborate one you abandon. It is very easy to read an article like this, get enthusiastic, sketch out a beautiful nine-email journey with branching logic and behavioural triggers, build about a third of it, and then never finish - so new members get emails one, two and three and then fall off a cliff into silence, which is arguably worse than a plain three-email sequence that runs to completion every time. I'd rather you shipped three good emails than drafted seven perfect ones. So treat the five below as the full version, feel free to run only the first three if that's all you can sustain, and don't build a step you can't commit to keeping alive.

Email 1 - the welcome, straight away

Timing: within a few minutes of joining. Its job: confirm they're in, sound like a human, give them the one next step, and quietly promise more is coming.

This is the one email you must get out, and it must be automated, because a warm welcome that arrives three days later has lost most of its warmth and nobody reliably sends these by hand at 9pm on a Sunday. Keep it to one screen. Confirm the money did what it was meant to (people do quietly worry), sound genuinely pleased they joined, and point them at the single most valuable thing they can do this week - which for Dapur Nusantara is almost always "come to the next class" or "jump into the group where everyone actually talks". Everything else waits. This email should also hint, in one line, that a couple more helpful notes are on their way, so email two isn't a surprise.

Email 2 - one easy first action

Timing: day 2 - 3. Its job: get them to do one small, low-effort thing that pulls them a step further in.

The first email gave them a next step; this one gently makes sure they took it, or gives them an even easier one. The trick is to ask for something genuinely small - not "fill in your full profile and dietary preferences and upload a photo", just one action that takes thirty seconds and makes them feel a fraction more like a member. For a cooking community the loveliest version is an invitation to introduce themselves: pop into the group and tell everyone the one dish you'd most love to learn to make. It's easy, it's warm, it gets other members replying to them, and it quietly gives you a sense of what people actually want to cook. Don't stack three asks in here. One.

Email 3 - meet the community

Timing: day 7 - 10. Its job: make the membership feel like real people, not a mailing list.

By now they're a week in and, if you've done nothing else, at risk of the membership fading into background noise. This email exists to make the thing feel human and alive - a glimpse of what a class night actually looks like, a photo or two of the long table mid-feast, maybe a line about a member or two and what they're into. You're not selling anything here; you're just showing a newcomer the culture they've joined, so that "Dapur Nusantara" stops being an abstract name on a receipt and starts being a room full of people they'd like to meet. This is the email people most often skip, and it's a shame, because it's the one that turns a transaction into a belonging.

Email 4 - the nudge to their first class

Timing: the week before the next class (see the note below on timing this one). Its job: turn all the goodwill into an actual turn-up.

Everything so far has been building to this. The first time a new member physically walks in, apron on, is the hinge of the whole thing - it's where they find out whether the reality matches the welcome, and it decides more than any email can. So this one names the next class plainly, tells them the dish, and removes the two real barriers to a first turn-up: not knowing anyone, and not knowing what they need to bring or do. Name a person who'll look after them. For Dapur Nusantara that might be Mira, who runs the front of the room and won't mind at all being the one you're told to find.

One honest wrinkle worth flagging: a drip sequence runs on a clock (day 1, day 3, day 10) but events run on a calendar, and the two don't naturally line up. If your class is monthly, someone who joins the day after a class is three-and-a-bit weeks from the next one, while someone who joins the week before is nearly there - so a fixed "day 14" nudge will land at wildly different distances from the actual event. The cleaner fix, if your tools allow it, is to trigger this email off the class date rather than the join date (send it, say, four to five days before every class night to anyone who hasn't been yet). If your tools don't do that easily, don't agonise - a plain time-based nudge that occasionally lands a bit early still does far more good than no nudge at all. Just be aware of the mismatch so you're not surprised by it.

Email 5 - the check-in

Timing: day 21 - 30. Its job: catch the ones quietly slipping through, and confirm the good decision for the ones who aren't.

This is the step almost everyone skips, and it's cheap and it earns its keep. Somewhere around the three-to-four-week mark, check in - once - to see how they're getting on. For a member who's already been to a class and loves it, this is just a warm touch that says you noticed. For the one who joined, got busy, missed the first class and started to drift, it's a gentle hand pulling them back before they've fully let go. Keep it light and make it sound like a person, not a satisfaction survey, because the whole value is that it feels personal. Ideally it comes from a real name and invites a reply.

So how many emails, and how far apart?

Five is a comfortable full version for most community memberships, spread across the first three to four weeks - roughly day 0, day 2 - 3, day 7 - 10, the pre-class nudge, and day 21 - 30. If five feels like more than you can sustain, the three you should never cut are the welcome, the class nudge, and the check-in - those three alone (arrival, first turn-up, catch the drifters) carry most of the result. On spacing: never send two in the same day, give it at least a couple of days between each, and don't run so long that the "welcome" sequence is still going a month after they'd stopped feeling new. Once these five have run, the member simply rolls into your normal rhythm of class announcements and group chatter, which is exactly where you want them.

Resist the urge to over-engineer it, too. You do not need behavioural branching, lead scoring, or a fourteen-step lifecycle campaign to onboard a cooking club - not to start with, and quite possibly not ever. A plain time-based sequence of a few warm, well-spaced emails, sent to every new member the same way, will get you the bulk of what all that machinery promises, at a fraction of the effort and with far less to go wrong. Build the fancy version later, if you ever genuinely need it, once the simple one has been running long enough to show you what your members actually respond to….

Setting up a sequence like this so it runs itself, every time, without anyone remembering to send email three at 9pm on a Sunday, is one of the things Anggota is built to take off your plate - the emails go out on their own the moment someone joins, with the member's details already filled in, so every newcomer gets the same warm run-in. If that sounds handy you're welcome to try it for free and see how it fits your group. And if you'd sooner take this sequence and run it through whatever you already use - your existing email tool, or even a reminder in your calendar and sending the first few by hand for now - that's genuinely fine too. None of it depends on the tool; it depends on deciding a new member's first month is worth a handful of well-timed emails, and then actually sending them. For the bigger picture of why that first month matters so much, the complete guide to member retention is the natural next read.