fabIAna

Follow-up that runs on its own, from the first message to the next booking

Fabiana follows up on her own: automations react when a contact changes stage, gets a tag, turns hot or is created, and email sequences keep writing to them on the days you set. Each sequence stops when the customer replies, so the conversation goes back to the inbox and nobody gets an email that no longer makes sense.

Try her nowRequest a demo

Try it

An interactive example with a fictional business. Click around.

Automation “When booked”Active

Then

Sequence “After the dive”

  1. Email 1
  2. Email 2
  3. Email 3

Emails go out between 09:00 and 20:00, with an unsubscribe link. The sequence stops when the contact replies.

A/B results on 64 contacts

A18% clicked
B31% clicked

Try it on a contact

Run the automation to see what happens, day by day.

How it works

  1. Something happens to a contact

    A deal moves to Booked, a tag is added, the lead score turns hot, a new contact is created or your own system sends an event.

  2. The automation does the work

    It adds a tag, creates a task for the team, sends an email, starts a sequence, hands the conversation to the right person or calls a webhook.

  3. The sequence keeps writing

    Emails go out on the days you set, in daytime, with the contact’s name. When the customer replies, the sequence stops and the conversation is in the inbox.

Recorded from the interactive example above, with a fictional dive school.
Read the transcript

An automation: when a deal is booked, start a sequence, add a tag and create a task. The sequence is a few emails, each with its own wait, and an A/B test if you want one. Run it on a contact, and follow it day by day. The moment the contact replies, the sequence stops, and the conversation is in the inbox. See which subject got more clicks, and keep it for everyone.

Everything included

Automations

  • Triggers: stage change, tag added, lead score, deal value, new contact, a field that changes or an event from your system
  • Several actions per rule
  • Add tags and create tasks with a due date
  • Send an email or start a sequence
  • Route waiting conversations to the right person
  • Webhooks to your other systems

Email sequences

  • Steps with a wait in days or hours
  • Wait for an event, or branch on a contact’s fields
  • Start on a stage, by hand or for a whole segment
  • Templates with the contact’s name and custom fields
  • Sent only in the hours you choose

Measure and improve

  • A/B test the subject and text of each email
  • Click tracking per contact and per sequence
  • Keep the winning variant with one click
  • Every send on the contact’s timeline

Respectful by default

  • Stops when the customer replies
  • Stops on the events or fields you choose
  • Unsubscribe link in every marketing email
  • Only contacts with consent, or who are already customers
  • A daily email of leads nobody answered, with a task for each

Questions

What is the difference between an automation and a sequence?

An automation reacts once to something that happens, like a deal moving to Booked, and runs its actions. A sequence is a series of emails sent over days. An automation can start a sequence.

Does the sequence keep sending if the customer replies?

No. When the customer writes back, their sequences stop and the conversation is in the shared inbox for Fabiana or your team.

Can I test two subjects?

Yes. Each email can have a variant B. You see how many contacts clicked each one and keep the winner for everyone.

Can an automation call my own systems?

Yes. A rule can send a signed webhook, and your system can send events back that start automations or move contacts along a sequence.

Used for

More features