IGNITION
click anywhere to skip
ServicesWorkAboutBlogStart

AI and Automation

Email automation, and what to automate first.

21 September 2026 · Abdullah Rajpot · 11 min read

Email automation

Email automation is a set of emails that go out on their own when somebody does something, or when somebody stops doing something. A person joins your list and a welcome lands an hour later. Another leaves a basket behind and a reminder follows the next morning. You write each email once, then it keeps working while you get on with the rest of the business.

That is the appeal. It is also where most people overreach, because the temptation is to map every path a customer could take before a single sequence exists. Build the two or three that pay for themselves instead, and leave the rest until the list is big enough to deserve the work.

First, a warning. Automation multiplies whatever your emails are already worth, so a weak email just reaches more people more often. If nobody reads what you send now, start with the basics of email marketing instead. A trigger cannot rescue a message the reader never wanted.

Illustration from the article: Email automation, and what to automate first

What email automation actually does

An automated email waits for a signal, then goes. The signal might be a sign up, a purchase, a page view, a date on a calendar, or a stretch of silence. Nothing about the writing changes. What changes is who decides the moment it leaves.

Because the trigger comes from behaviour, the email arrives while the subject is still on the reader's mind. A broadcast reaches everybody on a Tuesday whether they care that day or not. Email automation reaches one person while that interest is still fresh, so the same words can land very differently.

None of this needs artificial intelligence. Most of it is a rule: if this happens, wait this long, then send that.

Start with the sequences that pay for themselves

Order matters more than ambition when you plan email automation. Build in order of how close the reader sits to a decision.

  1. Welcome, for people who just joined and are paying attention.

  2. Abandoned basket or abandoned enquiry, for people who nearly acted.

  3. Post purchase, which quietly sets up the second order.

  4. Win back, for people who have gone quiet.

  5. Everything else, once the first four run without you.

The first two reach people who have just shown intent. So they usually deserve building before the rest. Later ones matter too. Still, they are not where somebody starting out should spend the first month.

The welcome sequence comes first

Somebody has just handed you their address. Right now they know who you are and why they signed up, but that memory fades fast.

So the welcome should arrive quickly, say what to expect, and give one genuinely useful thing. A single email works. A short welcome email series works better, since it lets you introduce one idea at a time rather than packing everything onto one screen. It is also the easiest piece of email automation to get right, which makes it a sensible place to learn the tool.

Be honest about frequency while you are there. If you plan to write monthly, say monthly. Readers forgive a quiet list far more readily than a surprising one.

Then the one that recovers a sale

A basket left behind is the clearest signal of intent you will ever get for nothing.

Good abandoned cart emails ask why, remove the obstacle, and then stop. Delivery cost, sizing doubts, a card that failed: each has a different answer, and a generic nudge answers none of them. This is usually where email automation pays for itself soonest.

Service businesses have the same pattern under another name. Someone starts an enquiry form and stops halfway. Somebody books a call and never confirms it. Both deserve a short, plain follow up rather than silence.

What email automation needs before it works

Three things have to exist first, and skipping any of them produces sequences that misfire in public.

First, a reliable signal. Your website has to tell the email tool what happened, and both have to agree on who the person is. Second, tidy data on the list itself, since a sequence branching on a field nobody fills in will branch wrongly every time. Third, a rule for who may receive what.

That last one prevents the most common embarrassment. A customer who bought yesterday should never receive the sequence begging them to buy. Email segmentation is what keeps those two audiences apart, and it matters more as the number of sequences grows.

Permission sits underneath all three. Rules on marketing email differ from one country to the next. So check what applies to your own list before you switch a sequence on. Automation makes it easy to reach people at a scale you never would by hand.

Triggers, and the three kinds worth knowing

Almost every piece of email automation starts from one of three signals.

  • Action, such as a sign up, a purchase or a completed form.

  • Inaction, such as a basket nobody returned to, or an email nobody opened.

  • Time, such as a renewal date, a birthday or a service interval.

Time based triggers are the most overlooked and often the simplest. A boiler serviced last October, a subscription ending next month, a dog due its yearly vaccination: none of that needs clever technology. It needs a date field and a rule.

How email automation goes wrong

The failures are boringly consistent, and every one of them is avoidable.

Sequences run on forever because nobody wrote an exit rule. Two of them fire at once and a reader wakes up to four emails from you. A discount reaches somebody who would happily have paid the full price. Meanwhile a broken merge field greets a hundred people as "Hi FIRSTNAME".

All four share one root cause. Automation runs whether or not it makes any sense that morning. So write the exit rule at the same moment as the entry rule, and cap how many automated emails one person can receive in a week.

What not to automate

Some emails are worse when a machine sends them, and knowing which ones is part of the job.

A reply to a complaint should come from a person. A proposal follow up in a considered sale usually should too, particularly where the deal is large enough that the buyer notices a template. Condolence, apology and anything about a mistake belong to a human being. Email automation makes a bad apology worse, because the reader can tell nobody was there.

There is a quieter case for restraint as well. A small list run by one owner often does better with a short note written that morning than with a sequence designed for a company many times its size.

Email automation and the tools question

Start from the tool you already pay for rather than from a comparison table. The differences that matter are whether the tool can see what happens on your website, how easily it joins up to your shop or your customer records, and how clearly it shows you what a sequence actually did.

Avoid choosing on the length of a feature list. A tool with visual branching you never touch is worse than a plain one you understand, since email automation you cannot audit is email automation you eventually stop trusting.

One distinction is worth settling before you build anything. A timed sequence sends on a schedule once somebody joins it. A triggered one waits for behaviour instead. Getting that wrong is how somebody ends up running drip campaigns while believing they are reacting to a customer.

Measuring email automation without fooling yourself

Automated emails flatter their own numbers. They reach people who already did something, so of course they respond better than a broadcast to the whole list.

Judge each sequence on what it adds rather than on what it claims. The honest question for a recovery sequence is whether total orders moved, not how many the tool attributed to itself. For a welcome, ask whether new subscribers buy sooner than they used to before you built it.

A worked example, with round numbers chosen to make the arithmetic clear rather than to describe a typical business. Say your tool reports that the recovery sequence brought back ten orders last month. Before it existed, a few of those people came back on their own, say four of them. The sequence added six orders, not ten. Judge it on the six. Your tool will keep reporting ten, which is why the honest number has to come from you.

A first month you can actually finish

Four weeks is enough to build the email automation a small business actually needs. Take one task a week and finish it before moving on.

  1. Write the welcome, then send it to yourself and read it on a phone.

  2. Build the recovery sequence for whatever your version of an abandoned basket is.

  3. Add an exit rule to both, plus a cap on how many emails one person can receive.

  4. Read the results, then improve the weakest email instead of adding a fifth.

Everything after that is refinement. Once those two sequences run cleanly, the next ones take a fraction of the effort, because the signals and the segments already exist.

Frequently asked questions

What is email automation?

Email automation is a set of emails your tool sends on its own when a rule fires. The rule watches for a signal such as a sign up, a purchase, a date, or a period of silence, then waits a set time and sends the email you wrote earlier. Nothing about the writing changes. Only the decision about when to send moves from you to the tool.

What should I automate first?

Start with the welcome, then build a recovery sequence for people who nearly bought. Those two reach readers while your business is still on their mind, so they are the easiest to justify building. Post purchase and win back sequences come next. Leave elaborate branching alone until the first two run for a few months without needing your attention.

How many emails should a welcome sequence contain?

Three or four is a sensible starting point for most businesses, though one good email beats four weak ones. Give each email a single job: say who you are, explain what to expect, share something useful, and only then mention buying. If you cannot think of a job for the fourth email, do not write it. An empty email teaches people to ignore you.

Do I need an expensive tool for email automation?

Probably not. Open the tool you already pay for and look for the words workflow, journey or sequence, because the first two sequences need very little. The bigger cost is moving later. Triggers, sequences and reports all have to be rebuilt by hand when you switch tools, so pick something you can live with once the list has grown. Time, not licence cost, is what makes email automation expensive.

How do I stop somebody receiving two sequences at once?

Write exit rules and a frequency cap before you switch anything on. An exit rule removes a reader from one sequence when they enter another, or when they do the thing the sequence was asking for. A frequency cap limits how many automated emails one person can receive in a week. Both take minutes to set up and prevent the failure readers notice most.

Is email automation worth it for a small list?

Usually yes, because the work happens once and the sequence keeps running. A welcome sequence written this month still greets people next year. The exception is a list so small that you already reply to everybody personally. In that case a note you write yourself beats email automation, and you should spend the time growing the list instead.

How often should I review my sequences?

Twice a year is enough for most, plus any time the product, the pricing or the website changes. Read every email as a subscriber would, on a phone, and check that the links still resolve. Sequences rot quietly, since nobody sees them going out. An automated email pointing at a page you deleted can run for months before anyone notices.

Can email automation damage deliverability?

It can, mainly by sending too much to people who never engage. Mailbox providers pay attention to how readers treat your mail, so a sequence that keeps writing to somebody who ignores everything works against you. Build an exit for inactive readers into every sequence, and check it still fires before you add another one. Handled that way, email automation can help rather than hurt, because a triggered email usually reaches somebody who was expecting it.