Email automation examples: what works and why

These email automation examples are six workflows that established firms run all year, each described by what starts it, what it sends and what stops it. The question this article answers is practical: which automations are worth building first, and how do you use email automation without creating a tangle of workflows nobody understands. Every example below can be built on the levelpartner.ai platform in an afternoon.

Six examples, in the order most firms should build them

Enquiry acknowledgement

Starts when a website form is submitted. Sends a short reply confirming receipt and naming who will respond. Stops after one email. It is first on the list because it protects leads you already paid to attract.

Booking confirmation and reminders

Starts when an appointment is booked. Sends a confirmation, a reminder the day before and a reminder an hour before. Stops if the appointment is cancelled. Fewer missed calls means more of your team's diary turns into revenue.

Missed appointment recovery

Starts when an appointment is marked as a no-show. Sends a polite note with a rebooking link, then one follow-up two days later. Stops when the contact rebooks.

Proposal follow-up

Starts when an opportunity moves to the proposal sent stage. Sends a check-in after three days and a second after seven, both from the deal owner. Stops when the stage changes.

Dormant contact reactivation

Starts when a contact has had no activity for six months. Sends a short "still relevant?" email with one useful link. Stops on any reply or click.

Review request

Starts when a project, case or sale is marked complete. Sends a thank you and a link to leave a review. Stops after one reminder.

Before you start

You need a verified sending domain and clean contact data: names, email addresses and a field or stage that reflects where each person is. Map your pipeline stages and calendars first, because most triggers depend on them. Decide also who owns automation in your firm. Workflows without an owner multiply and contradict each other.

How to do email automation, step by step

Use the proposal follow-up as your first practice build. The pattern transfers to every other example.

1. In Opportunities, confirm you have a stage for proposals sent.
2. In Automation, click + Create Workflow and choose Start from scratch.
3. Give the workflow a name that states its job.
4. Add the Pipeline Stage Changed trigger for the proposal stage.
5. Add a Wait of three days.
6. Add If / Else checking the opportunity is still in that stage.
7. On that branch, add a Send Email written in the owner's voice.
8. Add a four-day Wait, the same check and a second email.
9. Add an Internal Notification asking the owner to call.
10. Click Test Workflow and run it on a dummy contact.
11. Switch to Publish and click Save.

How to use email automation without making a mess

Give every workflow a name that says what it does and a single trigger. Write down, somewhere your team can see it, which workflows exist and who owns them. Add exit conditions to every one, because the most damaging automation is the one that keeps emailing someone who has already said yes.

Review your list of workflows each quarter. Turn off anything that has not fired in 90 days and nobody can explain.

What it is for in a firm with flat revenue

Most stalled firms do not lack leads; they lose them between steps. A lead who waited two days for a reply, a prospect who missed a call and was never chased, a proposal that sat unanswered. These six examples close those gaps without hiring.

They replace sticky notes, calendar reminders and good intentions. Weekly upkeep is around an hour across all six: read replies, check delivery, fix any broken trigger. Agencies, consultants, mortgage brokers and real estate firms all use the same six, though the stages and wording differ.

For the mechanics behind triggers and actions, read how email automation works. For the structure of a single workflow, see our guide to building an email workflow. Two of the examples have their own deeper guides: automated follow-up emails and automated birthday emails, a seventh example many client-service firms add later.

When not to automate

Do not automate messages where the content changes every time, such as a bespoke proposal or a reply to a complaint. Automate the reminder to write it, not the message itself. Also avoid automation when a process is not yet stable; automating a broken process makes it fail faster.

Troubleshooting

A workflow fires twice for one contact. Two triggers overlap, or the contact re-entered. Restrict re-entry and check that no other workflow sends the same email.

Emails go out after the deal is won. The exit condition is missing. Add a stage check before every send.

Delivery drops after a large automation goes live. Volume rose suddenly. Introduce new workflows gradually and watch bounces in Reporting.

Nobody knows why a contact received an email. Use the contact's activity history to see which workflow sent it, and name workflows clearly so the answer is obvious.

Frequently asked questions

Which email automation should we build first?

Enquiry acknowledgement, then booking reminders. Both protect revenue you are already generating and are simple to build. Leave complex nurture programmes until those are working.

How many workflows does a 50-person firm need?

Usually between six and fifteen. More than that often means duplicates. One owner and a written list keep the number sensible.

Can automated emails still feel personal?

Yes, if they come from a named person, use merge fields carefully and are short. The proposal follow-up example works because it reads like the deal owner checking in.

Do we need a developer to set these up?

No. Workflows are built in the platform's visual editor. A confident operations or marketing lead can build all six examples without writing code.