Skip to main content

Build automated email sequences with branching

Build an email sequence in Hook that follows up only with customers who haven’t acted, using wait and split steps, live customer data and language-specific emails.

You can send a series of emails to a group of customers, stop emailing anyone who takes the action you wanted, and follow up only with those who have not. This article shows how to build that sequence in Hook using wait and split steps.

Who can build this: Managers and Technical Admins have access to Automations settings in Hook. If you do not see Automations in your settings, ask a Manager or Technical Admin to build the sequence. Each email sends from a connected Gmail or Outlook mailbox, so the sender also needs their email account connected to Hook.

By the end you will have one automation that:

  • Sends a first email to every customer in a chosen campaign

  • Waits a set number of days, then checks whether the customer has changed their behaviour (for example, turned on a feature)

  • Sends a second email only to customers who have not changed, then repeats the wait and check before a third email

  • Fills each email with live customer data, such as their usage in the last 90 days

  • Sends each email in the recipient's preferred language

Before you start

Set these up first so the automation can be finalised in one go:

  1. Connect your email. Emails send from a connected Gmail or Outlook mailbox, so the sender needs their email account connected to Hook. See Connect Your Email to Hook.

  2. A way to identify the campaign audience. This can be customer-level data, such as a field in the Customers table or Customer details (a custom field set to the campaign name, a lifecycle stage or a product), or user-level data, such as a field in the Users table (a user type, role or activity).

  3. A way to detect the behaviour change. Pick the field or metric that shows the customer did what you wanted, for example a feature-enabled flag or a usage metric above zero. It must appear in the Customers table (or the Users table for user-level behaviour).

  4. The data you want to show in the emails. Anything you want to insert as a variable, such as reservations by channel in the last 90 days, must already exist as a field or metric in Hook.

  5. A language field. Each customer or user needs a preferred language stored in Hook so you can route them to the right version.

  6. Email templates. Create one template per email per language in Email templates settings. See Create Email Templates.

How the sequence works

Every customer in the campaign receives Email 1. After a wait, Hook checks whether they have changed their behaviour. Those who have leave the sequence, and those who have not receive Email 2. The same wait and check then happens once more before Email 3, the last email. Every path in Hook needs an action, so the exit path uses one that does not email the customer, such as recording that they have completed the campaign.

Steps 1 and 2: Choose your audience and send the first email

The first email goes to everyone in the campaign, so the trigger is a filter on that campaign.

Choose the audience

  1. Go to Organisation settings > Automations and click Create automation.

  2. Enter a descriptive name and click Next step: Choose type.

  3. Select Based on customer activity. The type cannot be changed once the automation is created.

  4. Click the + on If... and select Customer filters are met.

  5. Hook adds a default filter of Customer status: Active. Use Add filter to narrow the audience to your campaign, for example a custom field set to the campaign name, a lifecycle stage or a product.

  6. Click These filters will match [number] customers to see a filtered view of the Customers table and check the audience is right. Use your browser's back button to return to the automation.

  7. Click Create.

Customer filters are met: choose who is in the campaign

Send the first email

  1. Click the + on Then... and select Send an email.

    Then...: choose Send an email
  2. Under From, select the sender's role (for example Account Manager) and choose a Backup mailbox for accounts that have no one in that role. A backup mailbox is required, and it comes from the email aliases set up in your profile settings.

  3. Under Send to, choose Include contacts, Include users, or both. Use Users filter if you only want specific people to receive the email.

  4. Choose Compose email and write the Subject and Email, or choose Use saved template and pick a template.

    Send an email: sender, recipients and message
  5. Leave Include sender's email signature ticked if you want the sender's signature added. Tick Require approval before sending if you want the emails created as Actions that your team reviews before they go out.

  6. Under When to resend, choose Never. Each customer then receives this email once, however many times the automation checks them.

  7. Click Create.

    Approval and When to resend settings

Plan for deliverability. Hook emails send from the sender's own Gmail or Outlook mailbox, so they count towards that provider's daily sending limits and are subject to its spam filtering. As a guideline, stay within about 500 emails a day on Gmail and 1,000 on Outlook, and avoid sending the same message to a very large group at the same moment. Hook shows a reminder when you set up the email, and suggests refining your filters to limit how many emails go out at once. See Emails in Hook - FAQs for sending limits, shared inboxes and opt-outs.

Automations run every 2 hours and immediately after they are created.

Step 3: Wait, then branch on behaviour

This step stops follow-up emails going to customers who have already done what you asked.

  1. Once the first email is saved, click the + below it. This adds a step with a Wait... setting and a Progress... setting.

  2. Use the − and + buttons to set how many days to wait. The default is 7 days. Choose a gap long enough for someone to act on the first email.

    A Wait step, with Progress set to All or Split
  3. Under Progress..., select Split. Hook creates two paths: an If... path and an Otherwise... path, which applies to all other customers.

    A Split creates an If... path and an Otherwise... path
  4. Click the + on If... and choose a trigger that describes the behaviour change you want to see. For example, choose Customer filters are met and filter on the field or metric that shows the feature is now on, such as a usage metric greater than zero. You can also use triggers based on a trend in customer data, signals, subscriptions, engagement level changes or external activity.

    The conditions available on the If... path
  5. The If... path is for customers who have changed their behaviour. Give it an action that does not email them, such as Populate a custom field to record that they have completed the campaign. Every path needs at least one action before the automation can be finalised.

  6. The Otherwise... path is for everyone else. This is where the next email goes.

The check runs when the wait ends, so a customer who changes their behaviour at any point during those days is caught before the next email is sent.

Step 4: Add the follow-up emails

Repeat the same pattern for the second and third emails.

  1. On the Otherwise... path, click the + on Then... and select Send an email. Set the sender, recipients and template as you did for the first email, and set When to resend to Never.

  2. Click the + below the second email to add another Wait... step and set the days between emails 2 and 3. Select Split under Progress....

  3. Set the If... path to the same behaviour check, with a record-keeping action as before.

  4. On the Otherwise... path, add Send an email for the third and final email.

  5. Select the Active toggle at the top of the automation when you are ready. You can only activate an automation once it is complete, and the Incomplete badge shows while any step still needs an action.

The third email is the end of the sequence, so there is no further wait or split after it.

Step 5: Add live customer data to each email

Variables fill each email with details that are specific to the recipient and their account, so one template can read as personal to every customer.

  1. While composing an email in the automation, or when creating an email template, click Insert variable.

  2. Search for or scroll to the field you want. The list starts with variables for the action itself (recipient first name, last name, full name and email address, and sender first name), followed by fields from the Customers table, including metrics and custom fields.

  3. Select the field. It appears in the email as a code such as {{accounts.field_name}}, and Hook replaces it with each recipient's own value when the email is sent.

  4. Send yourself a test using the Email preview section at the bottom of the action. This needs a sender email address set up in your profile settings.

Insert variable lists recipient, sender, customer and metric fields

A variable can only show data that already exists in Hook. Plan the fields before you write the email:

What you want to show

What it needs in Hook

The recipient's first name

Recipient first name (standard variable)

The customer's name

A Customers table field

A usage figure, such as activity in the last 90 days

A metric or custom field holding that figure

A value or saving, such as an estimated cost

A metric or custom field holding the result, calculated before it reaches Hook

How the customer compares with similar customers

A metric or custom field holding both figures, or the benchmark

Sender name and signature

Sender variables, or the sender's email signature

If a field you need is not in Hook yet, contact [email protected] to have it added as a custom field.

Step 6: Send each email in the recipient's language

The simplest way to send in different languages is one automation per language. Each has the same structure but its own audience filter and its own templates.

  1. Build and test the full sequence for your main language first, using the steps above.

  2. From the automation menu (the three dots at the top of the automation), select Duplicate automation.

  3. Rename the copy to include the language, for example "Feature campaign - French".

  4. Edit the trigger or the Users filter so it only matches that language: use a customer filter if the language is stored on the account, or a users filter if it is stored on the person.

  5. In each Send an email step, select the translated template for that language, so the first, second and third email each use the matching version.

  6. Repeat for each language, then set each automation to Active.

So that no one is missed or emailed twice, make sure the main-language automation excludes the other languages, or acts as the default for anyone whose language is empty. Otherwise a customer could match more than one automation.

Use clear template names such as "Feature campaign - Email 2 - French" so the right version is easy to find in the template list.

Example: a feature adoption sequence

This example encourages customers to turn on a feature they already have but are not using. Square brackets show where a variable or link goes. Adapt the wording to your own product and tone.

Email

Sent

Purpose

Email 1

When the customer matches the campaign filter

Show what the customer is missing, using their own data

Email 2

X days later, only if the behaviour has not changed

Share a customer story as proof

Email 3

X days after Email 2, only if the behaviour has still not changed

Make it as easy as possible, with steps and an offer of help

Email 1: lead with their data

Subject: A quick opportunity for [Customer name]

Hi [First name],

I've noticed an opportunity for [Customer name] to get more from [Product] and I'd love to help.

As far as we can see:

- [Metric 1, for example activity in the last 90 days]

- [Metric 2, for example the value that represents]

You already have [Feature], it just isn't switched on yet. It takes about [X] minutes to set up, and this short video shows you how: [Video link]

Would you prefer to set it up together? Book a call with me: [Booking link]

Best,

[Sender first name]

Email 2: share a story

Subject: A story that reminded me of [Customer name]

Hi [First name],

I wanted to share a story that reminded me of [Customer name]. [Similar customer] was in a similar position.

They switched on [Feature] and [what they did next].

[Result, for example the improvement they saw].

The full story takes 2 minutes to read: [Case study link]

Would you like to do the same at [Customer name]?

Book a call with me and we'll set it up together: [Booking link]

Best,

[Sender first name]

Email 3: make it easy

Subject: Still interested in switching on [Feature]?

Hi [First name],

I wanted to check whether you're still interested in [Feature].

It's quick to set up and it's included in your plan.

You can do it yourself in a few steps:

1. [Step 1]

2. [Step 2]

3. [Step 3]

There's also a short guide ([X] minutes): [Guide link]

Or we can do it together in [X] minutes.

Book a time with me: [Booking link]

Best,

[Sender first name]

Tips for a sequence that performs

  • Leave long enough between emails for someone to act, typically 5 to 7 days, and test the whole flow on a small audience first.

  • Send from a named individual's mailbox rather than a shared inbox, which has a lower sending capacity. See the deliverability note in Step 2.

  • Ask for one action per email, and offer a second route, such as a call, for customers who would rather be helped.

  • If recipients need to be able to opt out, use Hook to identify the audience and send through a tool that handles unsubscribes. See Emails in Hook - FAQs.

Track how the sequence performs

Two views help once the sequence is live:

  • Automation logs show each time the automation ran and which path each customer took. Open the automation and select View logs on a Send an email output. See Automation Logs.

  • Email reporting shows what happened to each email: Sent, Bounced, Opened, Clicked and Replied. Treat opens as a directional signal, and use clicks and replies as stronger signs of engagement. A high number of bounces usually points to outdated addresses in your contact data. See Understanding email reporting for what each status means and its limitations.

Frequently asked questions

Will a customer receive the same email twice?

Not if When to resend is set to Never on each email, which is the default.

How do I check the emails have sent?

Open the automation and select View logs on a Send an email output. Make sure the automation is saved and set to Active, and that at least one customer matches the trigger filters. See Automation Logs.

A customer changed their behaviour but still received the next email. Why?

Check the automation logs for that customer to see when the check ran and which path they took. Automations run every 2 hours, and the behaviour field must have updated in Hook before the check happens.

Can I pause the sequence?

Yes. Switch the Active toggle to inactive. It is better to set an automation to inactive than to delete it, in case you need it again.

My automation is not sending.

Related articles

Did this answer your question?