Set exit rules and frequency limits so someone in several flows at once doesn't get buried in email.
Priya runs a centre that offers trial classes for children, and she gives away a heuristics checklist to get parents to sign up. In this example, one parent signs up for the checklist on a Monday and books a trial class on Tuesday. Over the next six days she gets six emails:
welcome email two the trial booking confirmation the fortnightly newsletter welcome email three the trial reminder the post-trial follow-up
By Saturday the parent wonders whether booking was a mistake. A week earlier she had never heard of the centre.
Each of those emails came from a flow that was built separately and makes sense on its own. Nobody planned six emails in six days. They piled up because each flow was built without looking at the others.
Automations are triggered by events, and one person can trigger several events close together. A new subscriber who buys quickly is in the welcome flow and the post-purchase flow at the same time. A customer who has gone quiet and then clicks a newsletter link can be in a re-engagement flow and a browse reminder at the same time. All the while, the newsletter keeps going out on its own schedule.
Your email tool will not warn you about this. Each flow follows its own rules and knows nothing about the others, so you have to look across all of them yourself, from the subscriber's side.
The simplest check is to pick a common path a customer takes, such as "signs up and buys in the same week". Then write down every email that person would get, day by day, across every flow and the newsletter. Read the list as if you were receiving it. If it makes you uncomfortable, it will make the subscriber uncomfortable too, and it needs fixing.
When Priya noticed the flood, she mapped every email a parent would get in their first fourteen days. Her path was: sign up on day 0, book on day 1, attend the trial on day 5. The total came to fourteen emails. She made three changes, covered in the next two sections.
Exits are the most important rule. An exit condition is a rule that takes a person out of a flow when something happens, usually the thing the flow was trying to achieve. If a flow exists to get a purchase or a booking, that purchase or booking should end the flow.
Without an exit, a customer who bought on day two gets the day five email offering a discount on something they already paid full price for. A parent who booked a trial gets "Still thinking about a trial class?" the next morning. Both of these happen all the time, and both make the business look like it isn't paying attention.
To set one up, find the goal of each sales flow, whether that's a purchase or a booking, and set it as the flow's exit condition. Most tools let you do this on the flow itself, often under the name goal or exit trigger. If your tool has no exit condition, add a check before each sales email that sees whether the person has already bought or booked, and skips the email if they have.
Check that the exit is set on the right thing. In Mei Ling's welcome sequence test in Lesson 4.4, an exit set on the wrong tag let an offer slip through.
Priya's first change was to make her welcome sequence exit on booking. Its later emails had been pushing the trial the parent had already booked.
Some flows send a lot of email on purpose. A welcome sequence sends several emails in its first week, and a booking confirmation and a reminder land close together. A newsletter on top of a flow like that adds noise.
Many tools let you exclude people in a particular flow from a newsletter send. Many also let you exclude anyone who got an automated email in the last day or two. Some have a frequency limit, sometimes called smart sending, which skips a contact who was emailed very recently. Use one of these if your tool allows it. If it has none of them, exclude the "in welcome flow" tag from your newsletter sends by hand.
Not every overlap needs fixing. A booking confirmation is wanted even if a newsletter went out the same morning, because the person asked for it. Leave emails like that alone. The aim is to cut marketing pile-ups while messages people are waiting for still arrive on time.
Priya's second change was to exclude anyone in the welcome or booking flows from the newsletter. Her third was to move the post-trial follow-up from the same evening as the trial to two days later. Her fortnight went from fourteen emails to seven. Each of the seven is one the parent wants, and no two marketing emails land on the same day.
Automations run quietly, which is why they're useful. It also means they go out of date without anyone noticing. A welcome email may still promote the holiday programme that ended in June. A post-purchase email may link to a care guide page that has moved. An abandoned cart email may quote last year's delivery fee. A flow that has gone out of date keeps sending to every new person who triggers it, for months.
Put a flow review in your calendar every few months. In each review, go through every flow and read each email as a subscriber would. Click every link. Check prices, dates, offers and names against what is true today. Then look at each flow's results. An email that gets far fewer clicks than the others in its sequence needs attention, and so does any step that triggers unsubscribes. Module 8 covers how to read these numbers.
In the activity below, you'll draw up the same map for your own business: every email a new customer could receive in their first fortnight, across every flow and the newsletter. Then remove or delay anything that overlaps.
List every email a new customer could get from you in their first fortnight. Remove or delay any that overlap.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).