You pick the moment. Ada writes the message and takes the next step: texts them, books them, or reminds herself to try again.
This is how a regular quietly becomes a lost client. Nobody cancels. They just don't come back, and by the time anyone notices, they've found somebody else.
Ada catches the gap the same day. The service is still new, the client still loves how it looks, and that is the cheapest moment you will ever get to book their next visit. Checkout got busy and nobody asked, so she asks.
Every automation is the same shape: an event, and an action. Once that's the pattern, “can it do X?” almost always has an answer.
A visit ends with no next appointment
LifecycleText them while the service is still new, and get them back on the calendar before they drift.
A client is coming due
RetentionReach out around their own rhythm, not a blanket six weeks for everybody.
Nobody replies to the first message
RetentionFollow up once more with a different angle, instead of letting the thread die on a single unanswered text.
Someone says “reach back in a week”
RetentionAda schedules herself against their record, saves why in their words, and actually texts them then.
A booking is made
RemindersConfirmation goes out immediately, then reminders on the schedule you set.
A client checks in at the front desk
OperationsTheir stylist gets a text that their next client just walked in.
A slot opens up
OperationsThe people who wanted in sooner hear about it first, before it becomes a hole in the day.
A client hasn't been in far too long
RetentionA win-back sequence that escalates gently instead of one desperate “we miss you!” blast.
Not seeing yours? The list above is what most salons turn on, not the limit. If you can describe when it should fire and what should happen, bring it to the demo.
Set per automation, because a booking confirmation and a win-back text should not be written by the same hand.
Locked copy we maintain. Best for the transactional ones: confirmations and reminders that shouldn't be creative.
You write it, with merge fields for name, service, provider, and time. Ada fills them in and sends exactly what you wrote.
No template at all. She writes each message from that client's history and context, so two people never get the same text.
The most valuable follow-up in a salon is the one a human promised and forgot. Ada writes it down against the client the moment they say it.
“Next month” becomes a real date on that client's record. “After the holidays” becomes a real date too.
In their words: waiting until after the wedding, traveling until mid-July. That note is the only context she has later, so it's what makes the message land.
No sticky note on the monitor, no “I'll remember.” When the date arrives, the text goes out with the reason baked into it.
A client cancels and adds, almost in passing, that he'll reach back out in August. Ada replies that she'll check in then if she doesn't hear from him first. Open his profile a second later and there is a dated follow-up sitting on the record with the reason saved in his own words.
She leads with the reason he gave her weeks earlier and offers the exact slot he gave up. That is why it reads like somebody remembered instead of a campaign going out, and it is why he books in a single reply.
Most salons send one message and call it a day. Ada follows up once more from a different angle, because the first text usually arrived while someone was driving.
Repeating yourself is what makes outreach feel automated. The second message approaches it another way.
The sequence ends the moment they're on the calendar. Nobody gets nudged about an appointment they already made.
A clear no ends it. Ada never schedules a follow-up to override someone who told her not to.
Automations aren't a cron job blasting a list. Each one is an event, a rule, and an agent that can respond to what comes back.
An appointment is created, a visit closes out, a client goes quiet, a slot frees up. These come from the same records your calendar uses, so there is nothing to sync.
Their own visit rhythm, whether they already rebooked, whether they opted out. A client who booked at checkout never gets the didn't-prebook text.
Locked copy, your template with merge fields filled in, or written fresh by Ada from that client's history, depending on the mode you picked for that automation.
Same line as your reminders and your team, so it lands in the thread the client already has with you instead of a new unknown number.
This is the part a scheduled blast can't do. If they answer, she picks up the conversation: answers the question, offers times, books it.
Each automation shows whether it's on, when it last ran, and how many messages it has sent, so nothing is quietly firing in the background.
How Ada keeps clients coming back without nagging them.