Plan a five-email welcome sequence

Quick answer: A five-email welcome sequence should help a new subscriber use the specific thing they requested. Deliver it immediately, help them complete one step, resolve a likely obstacle, offer a relevant next path, and ask what they need next. Give each message one purpose and one main action. The example schedule below uses days 0, 2, 4, 7 and 10 after entry; adjust it to your reader and sending rules rather than treating those intervals as a tested optimum.

Important constraint: A sequence is only as good as its entry and exit logic. Suppress unsubscribed people, prevent accidental duplicate entry, and stop or change a promotional path when the subscriber has already completed its goal or become a customer. Test those states before activation. Brevo’s welcome-workflow documentation triggers on contacts added to selected lists after the workflow is activated; existing membership alone does not mean everyone will receive message one.

Suppose someone signs up for a software-workflow newsletter because you promised a reusable project checklist. A useful welcome flow should make that checklist easy to find, show how to apply it, and learn which problem the reader has next. It should not send five versions of “here is our product” or assume a person needs the same pitch after they have already taken the intended action.

Write the promised outcome before the schedule

State the sign-up promise in one sentence: “You will get a project checklist and a short series showing how to use it to launch one small workflow.” Now choose the action the reader should be able to perform by the end: perhaps naming an owner, a deadline and a stop condition for a project. Those details shape the emails. Without the outcome, it is easy to fill the five slots with generic introductions, testimonials and links that compete for attention.

Create one primary call to action per message. A call to action can be “download the checklist,” “fill in the owner row,” or “reply with the blocker you found”; it does not have to be a sale. If a message contains several unrelated buttons, the writer may not know what progress it is meant to create. Keep optional reference links secondary and make the main action visible near the top, especially on mobile.

The schedule uses elapsed days since entry, not fixed calendar dates. A local send window can shift the actual delivery to a reasonable hour; the workflow must define how its delays and windows interact. If message two waits two elapsed days and then a window opens the following morning, it may arrive later than a simple “48 hours” expectation. Test that behavior with the selected platform rather than promising exact timestamps in the sign-up copy.

Make the copy specific enough to use

The schedule tells you what each message must accomplish. Write its main action in the same terms as the checklist, so the reader can move between the email and the resource without translating your instructions. For the ownership message, a draft might read:

Subject: Who owns the first step?

Open the checklist and find the Owner column. Put one person’s name next to the first deliverable. If two people share the work, name the person who will confirm that it is finished.

For example: “Lena — publish the signup form by Thursday.” That gives the team someone to ask and a date to work toward.

Button: Fill in the Owner column

This is illustrative copy for the project-checklist example. Replace its person, task and deadline with an example that fits the resource you actually provide. The button should land on the checklist or its instructions, rather than a general homepage where the reader has to find it again.

A follow-up can then address a specific obstacle without repeating the download pitch:

Subject: Is your first task still too big?

“Launch the newsletter” leaves several jobs hidden inside one row. Try “Create a signup form with one field and a working confirmation.” Give that smaller task an owner and a deadline, then leave the rest for the next row.

Button: Write a smaller first task

Notice the difference between the examples: the first resolves responsibility; the second resolves scope. Both use the same checklist, but each helps the reader change a different part of the plan. Read your five drafts in order and mark the new action in each. If two emails ask for the same work, combine them or use the spare message to answer a real question readers have raised.

Preference links need equally concrete labels. “Project ownership,” “Release checks” and “Measuring results” are useful choices for this sequence. Explain that the selection helps choose future topics. A click records that preference; it does not establish that someone finished the checklist or has a particular problem. For the final reply request, use a question someone can answer in one sentence: “Which row was hardest to fill in?” Make sure replies go to an inbox someone monitors.

Keep the first delivery email especially short. Put the promised asset link before any background about the brand, say when the next emails are expected, and include a contact route if the file cannot be opened. Check that link outside the logged-in editor session. A correct-looking button can still lead to a private file.

Before loading the drafts into an automation, replace placeholders and inspect each destination. Keep optional reading links below the main action. The recurring visual template can stay the same across the five messages; the useful work each message asks the reader to do should change.

Specify entry, skip and exit rules before activation

Define exactly what enters the series. For this example, a new subscriber who requests the checklist and meets the list’s permission criteria enters once. Someone already on the list should not receive a surprise replay merely because the workflow is switched on. Someone who unsubscribes exits. A duplicate import should not create a second overlapping run. A customer conversion halfway through should leave any promotional branch that no longer fits, while still receiving operational messages they requested through the appropriate channel.

Brevo’s documented welcome example starts when a contact is added to a selected list after activation. It describes removing a Time delay step for an immediate email, adding delay and email steps, optional re-entry after exit, and customer exit conditions. Those are useful implementation concepts, not proof that every plan or editor exposes identical options. Check the current account’s workflow, trigger and entitlement before turning on a live series.

For each message, write a skip or exit rule next to the copy. If an email refers to an asset that is no longer available, hold it until the link is fixed. If the subscriber chose a different path, avoid sending a contradictory next-path email. If a purchase changes the relevance of a message, stop or branch before the next send. Some conditions require event data from the website or commerce system; verify that the event reaches the automation and maps to the right contact before relying on it.

Test contacts and states, not just email design

Create test contacts that represent the cases the workflow will face. Review the expected result for each before running the test so a surprising send has a clear meaning. Use controlled addresses and do not use real subscribers as accidental test subjects.

Check the rendered message in a narrow mobile view, click the main action, inspect personalization fallbacks and follow the unsubscribed and conversion paths. Record what the platform actually did, not just what the diagram implies. Repeat after changing a trigger, delay, suppression rule or message order. An automation can be visually tidy while still sending the wrong email to the wrong state.

Measure reader progress without claiming a perfect cadence

Choose observations that match the sequence’s purpose: checklist access, a completed first step when the reader voluntarily reports it, topic preferences, replies and questions. Opens and clicks may be available, but they are incomplete signals. A click does not show that the project owner was assigned, and a low open figure does not explain whether the subject, deliverability or measurement caused it. Avoid claiming that days 0/2/4/7/10 outperform another cadence without a comparison in the actual audience.

Volume also matters. If 200 new subscribers each receive all five messages during a period, the plan contains up to 1,000 intended deliveries before other newsletters or tests; exits and timing can reduce that number or move some sends into another month. Count the steps people actually reach and compare the platform’s usage after a cycle. The email hub covers related sending decisions once the message journey and its audience are clear.