Email marketing automation: five examples you can plan before choosing a tool

The most useful automation is often the email you keep forgetting to send. A new subscriber asks for a guide; a customer needs help getting started; someone has stopped engaging. Start there. A thoughtful sequence should help the recipient make progress, rather than simply increase the number of messages in their inbox.

Email marketing automation sends or changes messages when a defined event or condition occurs. A drip campaign usually follows a planned schedule; a behavior-based journey can branch or stop when the recipient takes an action. The examples below are editorial planning designs. We have not run them or measured conversion results.

Before you write: define five things

For every journey, write the trigger, intended audience, message purpose, timing and exit rule. Also name the owner. Without an exit rule, a new customer may keep receiving a sales pitch for something they already bought. Without an owner, the sequence may promote an offer that ended months ago.

Use marketing contacts whose permission and status support the messages. Keep service messages and promotional sequences distinct. Check the current requirements of your platform and the rules that apply to your business before a live launch.

1. Welcome sequence after a signup

Trigger: a person joins the relevant list or requests a resource.

Message one: deliver what they requested and explain what happens next. Message two: show a useful example or answer a common beginner question. Message three: invite one appropriate next step, such as reading a guide or choosing an interest.

An illustrative schedule is immediate delivery, then a follow-up two days later and another three days after that. Those timings are starting assumptions, not proven best times. Stop marketing sends when the person unsubscribes; route a buyer into the appropriate customer journey.

Check successful resource delivery and the intended next action. Open rates alone do not establish that someone received value.

A welcome email you can adapt

Subject: Your checklist is ready

Hi [First name],

Here is the checklist you requested: [resource link]. Start with the first section and note the one step that is hardest to complete today.

I’ll send one practical example in two days. If you have a question about using the checklist, reply to this email.

[Sender name]

Flow: signup → deliver resource → wait two days → check whether the person is still eligible → send the example. Before each marketing send, apply the platform’s unsubscribe and suppression rules. Exit the introductory sequence when the person buys or completes the chosen next action.

Measure: successful resource access and relevant replies. The copy and timing are original planning examples, not a tested campaign.

2. Lead-nurture drip campaign

Trigger: an interested subscriber requests information about a specific problem.

Write a short sequence that develops the decision: explain the problem, show how to evaluate possible solutions, then answer a real objection. Each email should do one job. If a person books a conversation or becomes a customer, stop the introductory pitch or move them to a relevant follow-up.

Avoid treating an interest click as proof that someone is ready to buy. Use it as a signal to make the next message more relevant. Test the path for someone who never clicks as carefully as the path for someone who does.

A nurture email for a service decision

Subject: Three things to compare before choosing a provider

Hi [First name],

Before you decide, compare what is included, who handles changes and what the ongoing cost covers. Ask each provider to explain the same small example so the answers are easy to compare.

If you would like help checking your requirements, reply with the task you need completed.

[Sender name]

Flow: relevant opt-in → send comparison criteria → wait three days → check for a booked conversation or purchase → send a question-and-answer follow-up only if still relevant. The three-day delay is a planning assumption.

Measure: qualified replies or booked conversations. A click alone should not automatically trigger a sales call.

3. Post-purchase onboarding

Trigger: a confirmed purchase or account milestone from a supported connection.

Send the information needed to start: where to access the product, the first useful action and where to get help. A later message can address a common obstacle. Suppress promotional acquisition messages that no longer make sense for this customer.

Verify the purchase event, product identifier and recipient mapping. A misconfigured connection can send onboarding for the wrong product or send it twice. Use safe sample transactions and confirm the platform’s plan requirement before relying on it.

An onboarding email focused on one first step

Subject: Start here: your first useful step

Hi [First name],

Your [product or service] is ready. Open [access link] and complete [first useful task]. It should leave you with [clear result].

If that step does not work, reply with what you see and we will help.

[Sender name]

Flow: confirmed purchase → match the product and recipient → send access instructions → wait two days → check completion → offer help if the task is unfinished. Keep service messages and marketing permission requirements distinct in your implementation.

Measure: completion of the first useful task and unresolved support requests. Do not infer completion merely because an email was opened.

4. Re-engagement and preference check

Trigger: a carefully defined period without meaningful engagement.

Ask whether the content is still useful and offer a clear preference or unsubscribe route. Do not create an endless “last chance” sequence. Decide what happens when there is no response, and document how suppression is handled.

Use signals appropriate to your platform and audience; email-open measurement can be affected by privacy features. A click, reply or relevant account action may answer a different question from an open. We are not claiming a particular inactivity threshold is best for every business.

A preference-check email without an endless last chance

Subject: Would you still like these updates?

Hi [First name],

I want these emails to stay useful. Would you prefer [topic A], [topic B], or fewer updates? You can choose here: [preference link].

If you no longer want them, use [unsubscribe link].

[Sender name]

Flow: defined inactivity segment → confirm marketing eligibility → send one preference request → wait seven days → follow your documented suppression rule if there is no response. The delay is an example, not a universal best practice.

Measure: preference updates, relevant replies and unsubscribe handling. Stop re-entry loops from repeatedly sending the same request.

5. Customer handoff connected to a CRM

Trigger: a verified inquiry or status change that genuinely requires a person’s attention.

Create a task or notification for the owner, and send the customer an appropriate acknowledgment if that belongs in the workflow. Keep the internal handoff and marketing journey distinct. A person asking for support should not be treated as a fresh sales lead simply because an event arrived in the automation tool.

Check duplicate prevention, field ownership and recovery after a failed run. Confirm the exact trigger and action on both sides of the connection. This is a design example, not proof that every CRM integration supports it.

A customer acknowledgment paired with an internal task

Subject: We received your enquiry

Hi [First name],

Thanks for explaining what you need. Your enquiry is with [team or owner]. We expect to respond by [realistic time]. If there is a deadline we should know about, reply with it.

[Sender name]

Flow: enquiry event → check event ID → create or update the record → assign an owner → create a task → send one acknowledgment. If assignment fails, notify the person responsible for the workflow instead of silently treating the enquiry as handled.

Measure: enquiries assigned, time to a human response and duplicates prevented. Only state a response deadline your team can meet. These designs have not been tested in the listed tools.

How to choose email automation tools

Count more than the emails. Waits, conditions, updates and exits can affect the plan. Write the journey first, then compare the plans supporting its actual behavior.

Use ActiveCampaign vs Kit, Kit vs MailerLite or Brevo vs Mailchimp for the shortlist that matches your decision.

Match the plan to the journey, not the tool name

The official plan pages checked on 6 October 2026 show different kinds of boundaries: MailerLite Free lists three automations, ActiveCampaign Starter five actions per automation, and Mailchimp Free excludes Marketing Automation Flows. Brevo’s Free automation allowance applies to contacts, while Kit Creator lists unlimited sequences and visual automations. A workflow count is not an action count or a contact allowance.

Use those facts to rule out a plan that cannot perform the required journey. Then compare the supported trigger, entry/exit rules, sending allowance and total renewal cost. The examples above are planning templates, not a ranked list of the best automation software.

Estimate sends before choosing a free plan

For 200 subscribers receiving four newsletters monthly, campaign sends total 800. If 40 newcomers receive three welcome emails, add 120: 920 sends, before other messages. This hypothetical calculation helps check monthly limits. Also inspect the busiest day, subscriber allowance and permitted automation features.

A launch checklist worth keeping

1. Test each path with safe addresses, including duplicates and missing fields.
2. Confirm links, personalization fallbacks and the mobile reading experience.
3. Verify entry, purchase and unsubscribe exit rules.
4. Record the required plan and expected usage.
5. Name the owner and review date, then launch one journey before adding another.

For platform selection, use the email software checklist. It covers the buying decision; this guide helps you define what the software must do.

Marketing automation software: compare the required journey

Marketing automation software should be chosen for the journeys you can define and maintain. The examples above supply triggers, timing and exits; the platform choice is the next step.

Candidate	Reason to evaluate it	Plan boundary to check
MailerLite	A compact signup-to-welcome pilot	Free lists three automations; subscriber and send limits also apply
Brevo	A sending-led campaign and automation workflow	Daily sends, stored contacts and automation-contact allowance
Kit	Creator newsletter and audience-product journeys	Broadcasts versus paid sequences and visual automations
ActiveCampaign	Conditional journeys with several decisions	Every action, branch and any separately required CRM capability
Mailchimp	An existing campaign workflow or newsletter-first shortlist	Marketing Automation Flows on the required paid plan

For a full shortlist, read best email marketing platforms for small business. Keep this article for journey design and the shortlist for product selection.

A complete automation pilot

Write one journey with an entry event, consent requirement, messages, waits and exit conditions. Build it in two candidate plans with safe records. Test duplicate signups, a contact who unsubscribes, an existing buyer and a missing field. Record which action is excluded from the plan and what happens after an integration failure. Keep a manual fallback until those cases are understood.

Separate launch success from business success. A correctly delivered test sequence is evidence that the design runs; it does not establish a higher conversion rate. Review messages and keep consent records before importing a live list.