Segments by recency, service, frequency, and value
Win-Back Bot
installed in 72 hours.
On a schedule you set, four agents work through your customer list in parallel: segmenting by recency and service, checking consent, matching the next credible offer, and drafting personal messages. You approve a batch in one screen.
Monthly cadence fires. Historian returns 212 customers last serviced 14 to 20 months ago who never bought recurring service; consent officer clears 189 of them.
Hi Priya, it has been about a year and a half since we did the move-in deep clean on Maple Ave. If it is time for a refresh before the holidays, we have Tuesdays open in your area through November. Reply YES and I will send two times. — Maria, Brightside Cleaning
The agent graph.
This is what you are buying. Not one prompt in a loop: a trigger that fires without you, agents that run at the same time, a chain that only starts once they all report, and one gate where the work meets a person.
Goes off Fires on the calendar, not on you
The cadence is the product. Reactivation dies when it depends on someone remembering.
- Monthly cadence
- Seasonal windows you define
- Individual customers crossing the lapsed threshold
In parallel Three agents work the list at once
Consent runs alongside segmentation, not after it, so an ineligible record never reaches a writer.
Historian Consent officer Enforces channel and region rules; drops anyone without a valid record or with an opt-out
Offer analyst Matches each segment to the next credible service, never a blanket discount
In series Then, in order
Only eligible, segmented, offer-matched records get written to.
Batch writer Drafts a 25-account batch with a specific reason to return per customer
Reply router Reads responses and hands warm ones to a person the same day
Approval gate Where it meets you
This is the one template where nothing auto-sends. Messaging your own customers is too consequential to delegate.
- You approve every batch before it sends
- Opt-outs honored automatically and permanently
- Batch size capped so a bad message can never reach the whole list
Hands off Then it learns
Each run makes the next segmentation better rather than repeating the same sweep.
- Records who responded, booked, or opted out
- Suppresses non-responders from the next two cycles
- Hands bookings to Review Engine if installed
What fires it.
- Your monthly cadence, on its own schedule
- A seasonal window you define, such as pre-summer or year-end
- A customer crossing your lapsed threshold
Your tools, not ours.
- Your customer list as CSV or from your CRM
- Email or SMS
- Calendar or booking tool
Where it stops and asks.
Nothing goes out without your approval of the batch. Consent rules for your channel and region are configured on day one and enforced by a dedicated agent every run, not by a line in a prompt.
Best for
- Cleaning companies
- Pool, lawn, and pest
- Dental and vet practices
- Salons and studios
- Accountants and advisors
The arithmetic, labeled as a scenario.
Every number here is illustrative. On kickoff we replace it with your inquiry volume, quote value, list size, or ticket count, and the system reports observed results after that.
- Formula
- 2,000 lapsed customers × 4% response × $180 average return visit
What you receive.
- Segmentation on your real history
- Consent rules for your channel and region
- Three message variants in your voice
- Approval desk with one-tap batches
- Monthly cadence you can pause
$2,500
- 90-minute kickoff: accounts, voice, rules, and approval boundaries
- Triggers wired to your forms, inbox, calendar, and tools
- Every agent in the topology configured on your real history
- A dry run on past cases before anything reaches a customer
- An approval desk you can run from your phone
- Live within 72 hours of kickoff
$400 after 30 days
- Hosting, scheduling, and the trigger watchers, 24/7
- Claude usage up to 1,000 agent runs a month
- Rule, prompt, and routing changes whenever you ask
- A 30-minute tuning call every month
- Weekly report: what ran, what it decided, what it escalated
- Cancel anytime; the bots run to the end of the paid month
It hands off to these.
Bots chain. Win-Back Bot finishes its run by handing the result to the next system, so one trigger can carry a customer from first contact to a paid, reviewed job with no one retyping anything.
Plain answers.
Is this legal for SMS?
Only with consent, and the consent officer is a separate agent with veto power over the writers. Anyone without a valid consent record or with an opt-out on file is dropped before a message exists.
How personal is personal?
It uses what you actually know: last service, address street, season. It never invents familiarity.
What list size makes sense?
A few hundred records is enough for the first batch. Larger lists just mean more months of cadence.
Buy the system.
Keep the desk.
One install for one business. The managed desk starts after 30 days, so the first month has one job: prove this system deserves to stay.
- Live within 72 hours of kickoff
- All 5 agents tuned on your history
- Triggers wired to your tools
- Approval desk on your phone
- Monthly tuning call
- Direct founder support