Email · 11 Nov 2026 · 7 min read
Email automation basics: flows, drips and where to start
Email automation sends the right message when something happens, without anyone pressing send. This guide explains how it works, which automated emails to build first and how to stop subscribers receiving too many.
The short answer
Email automation means your email tool sends a message by itself when a trigger happens, such as a sign-up, a purchase or a long silence. A small business can start with a welcome sequence, then add one follow-up for its main action, such as a basket reminder or an enquiry reply. Limit how many automated emails one person can receive at once.
What email automation is and how a drip campaign fits in
Email automation is a set of rules in your email tool that sends a message when a defined event happens. The event might be a sign-up, an order, a form submission, a date or a period without a click. You write the email once, set the rule and the tool sends it to each person at the right moment.
A broadcast email, such as a newsletter, goes to a chosen group on a day you pick. An automated email goes to one person at a time, triggered by what that person did. The two work together. A broadcast keeps everyone informed, and automation handles the moments that arise one customer at a time.
A drip campaign is the simplest kind of automation: a fixed series of emails released at set gaps after a starting event. It is called a drip because the messages arrive in small amounts over days or weeks. Many automated email flows go further and branch. If the person clicked, they go down one path. If they did not, they go down another. Branching adds power and adds ways to go wrong, so a first flow should often stay as a plain drip.
The parts of every automated flow
Every automation, whatever tool builds it, is made from the same five parts. Knowing them makes any tool's screens easier to read.
| Part | What it does | Example |
|---|---|---|
| Trigger | The event that puts a person into the flow | Joins the list, places an order, submits an enquiry form |
| Wait | A pause before the next step | Two days after the trigger |
| Condition | A check that sends people down different paths | Has the person already bought? |
| Action | The step itself, usually sending an email | Send the follow-up message |
| Exit | The rule that takes someone out of the flow | They bought, replied or unsubscribed |
Most mistakes come from the last part. A flow with no clear exit keeps emailing people after the reason has gone. Decide the exit before you write the first email.
Which automated emails a small business should start with
Start with the moments where a prompt, helpful message already makes sense to the customer. Four or five automations cover most small businesses, and you do not need all of them at once.
| Automation | Trigger | Its job | Stop it when |
|---|---|---|---|
| Welcome sequence | Joins your list | Delivers the promise and explains what comes next | The series ends or the person buys |
| Basket reminder (online shops) | Leaves items in a basket | Reminds and answers common doubts | They complete the order |
| Order follow-up | An order ships or is delivered | Confirms, gives care or use advice, then asks for feedback | The message sequence finishes |
| Enquiry follow-up (service businesses) | A form is submitted | Confirms receipt and explains the next step | A person replies personally |
| Win-back | No clicks for a long period | Asks whether the person still wants to hear from you | They click, or you stop emailing them |
The right first automation depends on where your business loses people. A shop that sees many half-finished baskets should build the basket reminder early. A consultancy that gets enquiries and then goes quiet should start with the enquiry follow-up. A business with a growing list and no clear first message should start with the welcome sequence.
Treat each one as a small project with a clear goal. If you cannot say what a good result looks like in a sentence, the automation is not ready to build.
Plan the flow on paper before you open the tool
Sketch each automation as boxes and arrows: the trigger, each wait, each email and each exit. Put one line under each email stating what the reader should do next. If two emails have the same line, merge them.
Then ask what the person needs at each point. That question is easier to answer once you have a picture of your typical customer. The guide to creating a buyer persona shows how to write one from real conversations. A buyer who is comparing three suppliers needs different follow-up from one who is ready to order.
Automated emails can reuse what you have already written. Product advice, answers to common questions and policy summaries often exist on your website. A website content plan helps you see what you have and what is missing, so the same material serves both the site and the emails.
List the data each email needs. If you want to greet people by first name, check that the field is filled for most contacts, and write a fallback such as "Hello" for the rest.
Writing automated emails that read like one person wrote them
Write each email as a short note from one person to one person. Name the reason you are writing in the first line: "You asked for our sizing guide" or "You left a few items in your basket". Use one link or button, and make the subject line describe what is inside. The guide to writing email subject lines covers the choices in detail.
Avoid mentioning data you do not hold, and avoid phrases that suggest you are watching the reader. "We noticed you looked at this" can feel intrusive, while "Here is the guide you asked for" does not. Leave dates and time-limited claims out of evergreen automations, since they go stale and nobody notices until a customer complains.
Let people reply. A sender address that accepts replies turns automation into conversation, and the replies tell you which messages work.
How to avoid sending too many automated emails
Over-sending rarely comes from one flow. It comes from several flows that each seem reasonable, running together for the same person. Someone who joins your list, browses, buys and is later told they have not been seen for a while can easily receive four automations in a week.
Map every flow a person can enter
Write a list of all automations and the triggers that start them. Look for people who could qualify for two at once, such as a new subscriber who also leaves a basket.
Give flows a priority
Decide which automation wins when two apply. A common rule is that a transactional or order-related message goes first, and marketing flows pause until it is done. Many tools can pause one flow while another runs. Check what yours can do.
Set a quiet period and a weekly limit
After a purchase, a complaint or a reply, give the person a short break from marketing emails. Choose a maximum number of automated emails per person in any week and design the flows to fit under it.
Exit on the goal
Remove people from a flow the moment they do what the flow was for. A basket reminder that arrives after the order is complete is the clearest example of an automation that annoys people.
Check your own experience
Join your list with a spare address, buy something small, and watch what arrives over two weeks. You will find overlaps that no diagram showed. Also watch unsubscribes for each automated email, because a spike points to the exact message causing trouble.
Test before you switch it on
Test every path, not just the main one. Send the emails to spare addresses and check that the wait times, conditions and exits behave as drawn. Confirm that the trigger fires once per event and not repeatedly, as a duplicated trigger can send the same email many times. Open each message on a phone, click every link, and check what appears when a personal detail such as a name is missing.
Check the time zone settings, particularly if customers are in several countries. A "morning" email can arrive in the middle of the night for a reader on the other side of the world. Check what your tool does when someone unsubscribes, and confirm that the sender name and address are what you intend.
Track what each automation brings
Give every link in an automated email a consistent tag so that analytics can show visits and actions from each flow. The guide to UTM parameters explains how to name them. Record per email: clicks, unsubscribes and the action you wanted, such as a completed order or a booked call.
Automation also joins channels. Someone who finds you through a short video and taps a link in your profile can land on a page with a sign-up form, then receive your welcome flow. The TikTok for business guide covers the profile and video side of that journey.
Keep automated emails up to date, and know when not to automate
Automations run quietly, which is their strength and their risk. Put a review in the diary every few months. Click every link, reread each message and check that offers, policies and opening times are still true. Review them sooner when you change a product, a policy or your branding.
Do not automate everything. A complaint, a sensitive situation or a high-value enquiry deserves a personal reply. If your volume is small enough that you can write each message by hand, you may not need automation yet. If nobody in the business will maintain the flows, build fewer of them. For help planning email alongside your other channels, see the digital marketing service page.
Related guides
- Digital marketing
- Utm parameters how to track campaigns
- Website content plan what to write first
- Buyer persona how to create one
- TikTok for Business: Should You Start and How
- Utm parameters explained for campaign tracking
Questions and answers
What is email automation?
Email automation is a set of rules in your email tool that sends a message when a defined event happens, such as a sign-up, a purchase or a form submission. You write the email once and the tool sends it to each person at the right moment. It runs alongside regular emails like newsletters.
What is the difference between a drip campaign and an automated flow?
A drip campaign is a fixed series of emails sent at set gaps after a starting event. An automated flow is any rule-based sequence, and it may branch depending on what the person does, for example whether they click or buy. A drip is the simplest kind of flow.
Which automated emails should a small business start with?
Start with the moment where your business loses people. Many begin with a welcome sequence. Shops often add a basket reminder next, and service businesses add a follow-up to enquiries. Add more only when you can maintain the ones you have.
How do I avoid sending too many automated emails?
List every flow and the triggers that start it, then look for people who could be in two at once. Give flows a priority, set a quiet period after purchases and replies, and cap emails per person per week. Subscribe yourself with a spare address to see what a real customer receives.
Do I need special software for email automation?
You need an email tool that supports triggers and waits. Many general email platforms include basic automation. Features, limits and plan details change, so check the current documentation of any tool before choosing.
How often should I review my automated emails?
Review them every few months and whenever you change an offer, a policy, opening hours or your branding. Click every link and reread every message. An automation that nobody looks at tends to go out of date without anyone noticing.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.