Follow-up that stops the moment it should.
Multi-step sequences triggered by a new lead, an inbound message or a missed call - with an exit condition checked before every step, so nobody gets chased for something they already did.
How it works
Start from a recipe or a blank canvas
Speed-to-lead, reactivation, new-contact handoff, missed-call follow-up. Each one becomes an ordinary draft workflow you can edit - not a locked template - so you can see exactly what it will do before you turn it on.
Choose what starts it and what stops it
Trigger on a new lead, a new contact, an inbound message, or a missed call. Then set the exit condition: booked, replied, opted out. The condition is checked before every single step, not just at the start.
Watch what it actually did
Every run is recorded step by step - what fired, what waited, what was skipped and why. A sequence that stopped because someone replied looks different from one that stopped because a send was refused, and you can tell which.
What it can do
- Triggers on lead created, contact created, message received, and missed call
- Seven node types including waits, conditions, branch-and-rejoin, and sends
- Exit conditions checked before every step, so a sequence cannot nag someone who already booked
- Re-enrolment with a cooldown, so a customer who calls twice in an afternoon does not get two sequences
- A recipe gallery that shows unavailable recipes with the reason, rather than hiding them
- A full audit of every run: which step, when, and what happened
Exit conditions are checked before every step. Booked, replied, or opted out - the sequence ends there rather than finishing the script it was given.
Automations do not get their own path to your customers. They go through the same consent, quiet-hours and frequency checks as everything else, and a refusal names the rule that produced it.
Frequently asked questions
What stops a sequence nagging someone who already replied?
The exit condition, and the fact that it is evaluated before every step rather than only when the run starts. A customer who books after step one never receives step two. This matters more than it sounds: the most common failure of automated follow-up is the message that arrives after the thing it was chasing already happened.
Can an automation text someone who opted out?
No. Every outbound message in the product - automation, reminder, AI reply, or a person typing - goes through a single send check that reads consent, opt-out state, quiet hours, message purpose, and a per-contact frequency cap. There is no path around it, which is the point of there being exactly one.
What happens if someone rings twice in a week?
Re-enrolment has a cooldown. Somebody who calls twice in an afternoon gets one sequence; somebody who calls again next month gets a new one. Both of those are deliberate, and they are the same setting.
Are there recipes I cannot use yet?
Yes, and the gallery lists them with the reason rather than hiding them. No-show recovery needs something to mark an appointment as a no-show, which does not exist yet. Review requests need review tracking and a consent basis for asking, neither of which has shipped. Being told when something is coming is more useful than a shorter list.
Where to go next
Built for
Works with
Start free. Be live this week.
Built for dental, med spa, home services, and the businesses that live on the phone.