The work
What this actually involves
The system covers the whole journey: capture and score the enquiry, warm them before the appointment, handle the appointment itself, chase the undecided, turn customers into advocates, and work the existing base.
Every message is a template with the location's own details slotted in, which is why a repeatable build still sounds like the specific business running it.
Included
What you get
A new lead is ranked by how ready they are and worked until they book.
Capture and score
A new lead is ranked by how ready they are and worked until they book.
Attend and convert
Sequences that close the gap between booking and turning up, ready to buy.
Recover the undecided
The biggest pot of recoverable money in most businesses, worked on its own track.
Advocate and reactivate
Reviews and referrals pushed back to the top; the base worked rather than written off.
Hire me when
Signals this is the right piece of work
Leads arrive and nothing happens until someone remembers
No-shows are absorbing appointment capacity
“I’ll think about it” is where most of your pipeline dies
Reviews and referrals are collected by hand, when they are collected at all
The existing customer base goes quiet after one purchase
The same journey needs deploying across many locations without retyping it
The problem
Most automation is built for the easy customer
Almost every automation setup handles the person who says yes. Enquiry, booking, confirmation, reminder, thank you. That path is well covered because it is the obvious one to build.
The money is elsewhere. It is in the person who booked and did not turn up, the person who turned up and said they would think about it, the person who bought once eighteen months ago, and the person who enquired, went quiet, and was never contacted again. Those groups are usually larger than the yes group, and in most accounts nothing happens to any of them.
The architecture
Six stages, and the two that pay for the rest
Acquire. Capture and score the enquiry, then work it until they book. Response speed matters more than message quality at this stage.
Attend. Warm them in the gap between booking and appointment so they arrive ready rather than needing to be sold again. This is what protects show-up rates.
Convert. The appointment itself, and what happens immediately after it.
Recover. The "I will think about it" track. Usually the largest pot of recoverable money in the business, and usually the one nobody works, because it feels like chasing. Done properly it addresses the actual objection rather than repeating the offer.
Advocate. Reviews, referrals and testimonials collected at the point of highest satisfaction and pushed back to the top of the funnel.
Reactivate. People who never booked, never turned up, or said no, picked up later. Existing customers matched to other services they would genuinely benefit from.
Stages five and six feed back into stage one. That is what stops the base going quiet after a single purchase.
The rule that prevents chaos
One system owns the contact at a time
Most accounts I am called into have automations that contradict each other. A contact sits in three sequences simultaneously, receives a reactivation message the day after booking, or gets a review request while an unresolved complaint is open.
The cause is almost always the same: no single system owns the contact, so several of them act on it at once. The fix is to enforce ownership in the data rather than by convention, with explicit handoffs between stages and a rule that a contact belongs to exactly one system at any moment.
It is unglamorous architecture and it removes an entire category of embarrassing message.
Boundaries
What this deliberately does not include
More messages is not the goal. Sequences taper, and contacts who are clearly not interested exit rather than being pursued indefinitely.
Volume for its own sake
More messages is not the goal. Sequences taper, and contacts who are clearly not interested exit rather than being pursued indefinitely.
Ignoring messaging rules
Consent, opt-out and quiet hours differ by country. A2P registration in the US, GDPR and PECR in the UK. Built in, not bolted on afterwards.
Writing your offer for you
Automation distributes a message. If the underlying offer does not land, sending it more reliably will not fix that.
Common questions
Questions people ask before booking
Where does automation actually make the most difference?
The follow-up nobody does manually. Specifically the person who said they would think about it, and the dormant customer base. Both are usually larger than the active pipeline and both are usually ignored.
How do you stop customers getting contradictory messages?
By enforcing that one system owns the contact at a time, in the data rather than by convention, with explicit handoffs. This is the fix for most of the chaos in a mature account.
How many messages is too many?
Sequences should taper and exit. A contact who has clearly disengaged should stop hearing from that sequence rather than being pursued until they complain or unsubscribe.
Does this cover compliance for SMS and email?
Yes, and it varies by market. A2P 10DLC registration in the US, GDPR and PECR in the UK, and different rules again in Australia. It is designed in rather than retrofitted.
Can this work alongside automations we already have?
Usually, though the audit often finds existing workflows that duplicate or contradict each other. Consolidating those is frequently more valuable than adding anything new.
What if we do not have a big database yet?
Then start with acquire, attend and convert, and add recover and reactivate once there is a base worth working. Building all six on an empty database is premature.
Start here
Start with the audit
A written architecture record and a staged plan, useful whether or not I build the rest.