Automated emails tend to go wrong in a few familiar ways: a sales email for the course she bought yesterday, two welcome sequences at once, a reminder about a payment she has already sorted out, or an email after she unsubscribed. You avoid all four if each automation starts on a specific event, checks what’s true at that moment and stops once it has done its job.
Describe every automation on one page
Write down:
- Goal: what should happen for her, or for you?
- Start: which event sets it off? A purchase, a booking, a form.
- Who it’s for: consent, what she bought, language and status.
- The emails: what each email is for and how long it waits.
- When it stops: a purchase, a cancellation, a reply, a payment sorted out or anything else that means the job is done.
- Exceptions: who should never enter it.
- Who looks after it: who checks when something breaks or the copy goes stale?
- How you know it works: one thing you follow, and one thing that warns you if something’s wrong.
Be specific about the start and who it’s for. “Filled in the retreat form, in Swedish, on 3 May” is something you can follow up; “joined the list” isn’t.
Four journeys you can use
1. A free guide or meditation
Start: she asks for your free guide and has said yes to your emails. Send the guide straight away, tell her what comes next and follow up with a few short emails on the same topic. Stop if she unsubscribes or buys something, so she gets the emails that belong to the purchase instead.
2. Purchase and welcome
Start: the payment goes through and she gets access. The receipt and login go out as ordinary customer emails. Then show her the first thing to do, where to get help and what comes next. Switch track once she’s got started. Never make access to something she paid for depend on her saying yes to marketing.
3. She hasn’t got started
Start: a participant hasn’t done the first practice within a set time. Point to the exact next step and offer help. Stop when she gets going, replies, gets a refund or her access ends. Don’t call anyone inactive just because an image in an email didn’t load.
4. The card payment didn’t go through
Start: the payment service reports a failed renewal. Explain calmly what happened and link to the payment service’s secure page where she updates her card. Never ask for card details by email. Stop the moment the payment is sorted, she cancels or you resolve it another way.
Customer emails, marketing and consent
Receipts, logins and security emails do a different job from a launch email, under different rules. Give them their own templates. Someone who unsubscribed from your newsletter should still get her receipt, and a receipt mustn’t become a back door for marketing.
Swedish marketing law generally requires prior consent for marketing emails to a private person, with a limited exception for existing customers and a requirement that people can unsubscribe. See sections 19–20 of the Marketing Practices Act. The rules depend on country and context, so get advice for your own business.
Getting delivered: SPF, DKIM and Google’s rules
Send from a verified domain, and keep an eye on bounces, complaints and unsubscribes. Google now requires SPF or DKIM from everyone sending to Gmail. Anyone sending more than 5,000 emails a day to personal Gmail accounts has further requirements: SPF, DKIM, DMARC and one-click unsubscribe. Google says the share of mail marked as spam should stay below 0.3%. Read Google’s current requirements rather than an old checklist.
What to measure
Open rates tell you little, because privacy features in email apps and image loading skew them. Watch bounces and complaints, then measure what the emails are for: that she got started, bought, sorted out her payment, got her question answered or stayed in the membership.
Test with a few different addresses before you switch the automation on: a new subscriber, an existing customer, someone who unsubscribed, a participant who has already started and someone whose payment is already sorted. Keep a note of what you change and when, so you can trace the cause when something starts going wrong.
In Idun Blue an automation starts when someone buys, books or finishes a lesson, and the emails live in the same account as the course. It can wait, choose a path based on what she did, give access to a course, add a tag or let you know. See automations.
