Write a full welcome sequence and set it up as an automation that starts when someone signs up.
Mei Ling bakes custom cakes, a business she started from a kitchen in Punggol (she is an invented example). Her welcome sequence is four emails, written in one document, loaded into her email tool and tested by signing up as a subscriber herself. That is the job here for your own sequence.
You already made a plan for your welcome sequence in lesson 4.2, and you got a sense of how each email should read in lesson 4.3. A common gap at this stage is that the plan exists but the finished emails aren't loaded into a tool that sends them automatically. Many sequences stall here. Half-written drafts sit in a notes app, and new subscribers receive only the lead magnet, the free resource they signed up to get.
There are four steps: draft, shorten for phone, build the automation, and test as a subscriber. Allow about forty-five minutes for the build, plus however long the sequence takes to run during testing. At the end you should have three to five emails live in your tool. They should be triggered by your signup form or its tag (the label the form adds to each new contact), use delays that match your plan, and have an exit for buyers, a rule that takes anyone who buys out of the sequence.
Draft every email in one document before you open the email tool. For each email, write the subject line, the preview text (the short line an inbox shows after the subject) if you know it, the body and a single link. With everything in one place, you can read the sequence in the order a subscriber meets it. This catches problems you would miss one email at a time: the same story told twice, a tip in one email that contradicts a later email, or a tone that starts friendly and turns formal partway through.
Read the whole document aloud once. Anything that makes you wince will make a subscriber wince too.
Mei Ling's document has four emails. The Day 0 email gives her ordering guide, a two-line hello and a request to reply with the date of the reader's next family celebration. Day 2 covers the three details she needs for any custom cake order. Day 4 tells how she started baking from her Punggol kitchen and shows a photo of a recent cake beside the customer's reference picture. Day 6 gives her starting price, how far ahead to order, and one link to the order form.
Most subscribers read on a phone, often in a spare minute on the MRT or in a queue. Each email should take under a minute to read, which for most welcome emails means a few short paragraphs. Cut hard. If an email covers two ideas, split it into two emails or drop one idea. If the opening paragraph is about you, move the useful content above it.
Priya, another learner, wrote first drafts of four or five hundred words each. Her final versions were around half that length, and the shorter versions read better.
The feature that runs your sequence is the automation. Depending on the tool, it may be called a flow, workflow, journey or sequence. The parts are the same in every tool.
Set the trigger first. The trigger is the event that starts the sequence. You can trigger on someone joining through the signup form you built in lesson 2.4, or on the tag or list that form adds them to. The tag is the better choice: if you add a second form later and give it the same tag, people who sign up through it will also go into the welcome sequence.
Next, add the emails in order, with a delay before each email after the first. Match the delays to the days in your plan. Mei Ling's emails go out on Day 0, Day 2, Day 4 and Day 6. Paste the text in from your drafting document rather than rewriting it in the tool. Set the sender name to a real person and the reply address to an inbox you actually check.
If your tool allows it, add an exit condition, a rule that removes anyone who buys or books from the sequence. If the tool can't do exits directly, add a tag when someone buys, then set each later email to skip contacts with that tag. Module 7 covers exits properly.
Finally, check what happens when the sequence ends. Once the last welcome email has gone, the subscriber should move on to your regular newsletter list.
Sign up through the live form with a personal address, the same way you tested in lesson 2.4. To avoid waiting days for every email, some tools let you shorten the delays for a test contact or send each email in the sequence to yourself as a preview. If yours can't, make a temporary copy of the automation with delays of a few minutes, test with that, and switch the copy off when you're done.
As the emails arrive, work through these checks:
Read each email on a phone, in order. In the inbox view, check the sender name, subject line and preview text. Click every link. Reply to the email that asks for a reply, and confirm your answer reaches an inbox you read. Look for anything that reads oddly in sequence, such as an email that says "yesterday I sent you" when the actual gap is two days.
Fix what you find, then run the test again.
Mei Ling's test turned up one problem. She placed a test order on day 3, but the day 6 email still reached her test address. Her exit condition had been set on the wrong tag. She fixed the tag and ran a second test, and this time the day 6 email didn't send.
When your final test run is clean, keep the test emails from that run. The activity below asks you to save them as your record of the finished sequence.
Put a welcome sequence of three to five emails into your email tool, start it with a test signup, and keep the test emails as your record.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).