Automating sequences: emails that work while you sleep

The difference between sending and automating

Up to now, we talked about campaigns: an email written today, sent to the list now. Automation changes the logic: you write once emails that go out on their own, triggered by an action or a date, to every new contact, indefinitely. This is what turns email from a weekly chore into an asset that produces while you sleep. A new subscriber receives your best welcome sequence whether they arrive at 3 a.m. or on a Sunday — without you touching anything.

A campaign is work you redo with every send. An automation is work done once that replays for each new contact.

The queen sequence: the welcome

If you should automate only one thing, it's the welcome sequence. It's the moment attention is at its peak: a new subscriber just raised their hand, they're curious, they read you. A good sequence of 3 to 5 emails over the first days:

• Email 1 (immediate): deliver the promised lead magnet, welcome them, establish who you are.
• Email 2: tell your story or your angle — build a bond, not a sale.
• Email 3: provide a quick win, useful content that proves the value.
• Email 4-5: present your offer, now that trust exists.

This sequence converts for months without you coming back to it: it's automation at the best effort/return ratio.

Behavior-triggered scenarios

Beyond the welcome, modern ESPs trigger emails based on what the contact does (or doesn't do):

These scenarios send the right message at the right moment, with no intervention — relevance at scale.

The tools and their level of automation

Not all ESPs automate the same way. Accessible tools (MailerLite, Brevo) cover welcome sequences and simple scenarios, plenty to start. Creator tools (Kit) excel at tag- and condition-based chains ("if clicked, then…"). E-commerce tools (Klaviyo, Omnisend) offer the finest behavioral scenarios, wired to the store. And to connect email to outside tools — add a contact from another piece of software, alert on Slack, push data into a spreadsheet — Zapier and Make bridge the gap when native integration is missing.

The trap: automating a bad message at scale

Automation amplifies everything — including mistakes. An error in a campaign email touches one send; the same error in a sequence touches every new contact for months, without you seeing it. Hence three precautions: test the sequence end to end by subscribing yourself before activating it, date content cautiously (avoid "this week" in an evergreen email), and review active automations periodically (a dead link or an expired offer otherwise runs silently). You never automate a message you haven't checked under real conditions.

Keeping the human in the loop

Automating doesn't mean disappearing. The best sequences invite a reply ("reply to me, I read everything"), which builds a bond and improves deliverability (replies are a strong positive signal for inboxes). Likewise, certain moments deserve a human: a hand-written email for a big announcement, a personal reply to a new customer. The rule stays the same as the whole stack: automate repetitive, low-judgment tasks, keep the human where it creates bond and value. A sequence that sounds robotic saves time but loses the relationship.

Key takeaways

Automation turns email into an asset: you write sequences once that replay for each contact, at any hour. Prioritize the welcome sequence — best effort/return ratio — then add behavior-triggered scenarios (interest, abandoned cart, post-purchase, re-engagement). MailerLite and Brevo are enough to start, Kit for creators, Klaviyo/Omnisend for e-commerce, Zapier/Make to connect the rest. Beware the amplification of errors: test every sequence end to end and review it regularly. Keep the human in the loop by inviting replies. None of this matters if the email doesn't arrive: let's protect deliverability.