HelpWriting and sending

Automations

Emails that go out on their own when someone joins, gets a tag or clicks: the canvas, waits, conditions and the people in each.

An automation sends a series of emails on its own: when someone joins your newsletter, gets a tag or clicks a link in an issue, they get its first email, then the next ones, with the waits you choose between them, and conditions can send each person down a path of their own. Each newsletter has its own, on the Automations page, and each one is a path you draw: who enters at the top, then its steps, one under the other.

Starting one

New automation starts a blank one, with one email to everyone who joins, ready for your words. Or use a template, already filled in with your newsletter's name and its best issues:

  • Welcome series. Three emails over a week: a welcome, your best issues, and a question they can answer.
  • Lead magnet. Sends what you promised as soon as a contact gets its tag, then a reminder to those who didn't open it.
  • Email course. Five lessons, one a day, for everyone who joins.
  • Start here. The day after they join, new readers get your most-read issues.

The welcome series starts from your welcome email when you have one. Everything in a template can change, and nothing goes out until you turn it on.

Building the path

The automation's page is a canvas, with the path in the middle, and the sidebar folds down to its icons to leave it more room:

  • Add a step by dragging Email, Wait or Condition from the panel on the left onto the path: a space opens where it lands. Clicking one adds it after the step you selected, or at the end, and the + between two steps adds one right there.
  • Move an email or a wait by dragging it along the path, into either branch of a condition too.
  • Edit a step by clicking it: its settings open on the right, and an email opens in the same editor as your issues, with Preview and Send test. Delete or Backspace deletes the step you selected, and Escape closes it.
  • Undo and redo with the arrows at the bottom left, or ⌘ Z and ⌘ Shift Z (Ctrl Z and Ctrl Y on Windows): they take back your last changes, one after the other, and bring them back. A step you bring back keeps its numbers. While you type in a field or an email, they undo your typing there.
  • Move around by scrolling or dragging the background. The buttons in the corner zoom in and out, and fit the whole path on screen.

Everything saves as you go. A step with something to fix, like an email without a subject, says what under it, and the panel on the left counts them.

Who enters it

Click the top of the path to choose when someone enters:

  • Joins the newsletter: as soon as they sign up on your website, your form or through the API. With double opt-in on, when they confirm.
  • Gets a tag: when one contact gets the tag you pick, from the tags your contacts have or a new one, as you add them or tag them on their page, or through the API. Imports and tagging many contacts at once never start it, so an automation never emails a whole list in one go.
  • Clicks a link in an issue: any link, or only links that start with the one you give, like a guide or a product page. Clicks from link checkers that open every link don't count.
  • Is added to it: you add someone from their page on Contacts, in About, or an app adds them through the API, one contact at a time.

Who gets it can be everyone the trigger picks, or only the people of one of your segments. Only people whose trigger happens while the automation is on enter it, and each of them once: people already on your list don't get it when you turn it on.

Conditions

A condition splits the path in two: each person who reaches it goes down Yes when its check is true for them, and down No otherwise. It checks one of these, as each person is when they reach it:

  • Opened the email before, or clicked in the email before: the email right before it on their path. Put a wait between them, like 2 days, to give people time to read it.
  • Has a tag, picked from your tags.
  • Is in a segment, one of yours.

Each branch goes on with its own emails, waits and conditions, 2 conditions deep at most, and the two never meet again. An empty branch ends the path of the people who go down it. Dropping a condition in the middle of a path moves the steps after it into its Yes branch. Each condition shows how many people went down each branch. Deleting one deletes the steps in its branches too, after asking.

Emails and waits

A wait counts from the step before it, an email or the condition its branch starts from, in hours or days, up to 365 days. An automation has 20 emails at most. On every path, its emails go at least 1 hour apart, and each person gets 2 automation emails a day at most, whatever they're in: the next one waits for the day after.

From email 3 on, the next emails go to readers: people who confirmed their address, were added with their consent, or opened or clicked one of your emails since they entered. The others wait up to 14 days for a sign of life, then leave the automation, so it keeps writing to the people who read it.

Turning it on and off

Turn on starts it. If something needs fixing first, it says what and opens the step. Automations need a plan to turn on: you can build one without. When a “joins the newsletter” automation's first email goes right away, it replaces your welcome email, so turning it on turns the welcome email off, and it says so.

Turn off stops it: nobody new enters, and the people in it wait where they are until it's on again. You can change it while it's on: people keep their place, those waiting for a step you delete go on to the next one in their branch, and the people in a branch you delete reach the end of their path.

Like issues, its emails go through the content check when you turn it on, and when you change them while it's on. While one is in review, the people who reach it wait for it.

People and numbers

Each email shows how many got it, opened it and clicked it, and how many are on their way to it. People, at the top, lists who's in progress, who reached the end of their path and who left, with why. Remove takes someone out, and each contact's page shows the automations they're in and the emails they got from each.

People who unsubscribe, bounce, complain or become dormant leave every automation they're in, and unsubscribing from an automation email unsubscribes them from your newsletter.

Keeping it healthy

MailCheap watches each automation's bounces and complaints as it sends, with the same rates as your issues. If they climb, it turns the automation off and you get an email saying why, so one automation never holds up your issues. Its emails also go out at a steady pace: when many people reach the same email at once, they get it over a few minutes rather than all together.

Its emails to people you never emailed go out in steps, like an issue's first send. Your account's first 1,000 new contacts in 7 days, issues and automations together, get them as they come. Past that, each next step, of 1,000 to 5,000 people, waits until the emails before it have their results and few of them bounced, were marked as spam or were refused. People who got an issue or an automation email from you aren't new, and people who signed up on your forms in the last 3 days get theirs at once, like a welcome email.

If the new contacts so far bounce or complain too much, the automation turns itself off and you get an email saying why. Take out the contacts you can't vouch for, then turn it back on: the next step goes, checked the same way. While a person at MailCheap takes a look at your account's sending, your automations wait with your issues, except for people who just signed up on your forms, who get theirs like a welcome email.

Plans

Automation emails count toward your plan's emails, like issues. Once the month's emails are used up, they wait until you upgrade or your emails reset, and you get an email: nobody misses one. Each newsletter can have this many automations on at once:

PlanAutomations on
Starter5
Growth10
Pro25
Scale50
Max125
Ultra250

From the API or an AI assistant

Everything here works from the API and AI assistants too: create_automation from a template or your own steps, conditions with their branches included, update_automation, turn_on_automation and turn_off_automation, list_automation_people, add_to_automation and remove_from_automation. An assistant shows you who enters it and what it sends, and asks you to confirm, before it turns one on.

An email made this way can be a whole HTML document, like a campaign's: it goes out as it is, with the footer at the bottom, and the automation shows its HTML to edit.

Still stuck? Chat with us from your dashboard.