Event-triggered, not calendar-blasted
Messages fire off a booking, a completed job, a due date or a missed payment. If the event has not happened, the message does not go.
Automated Customer Reminders & Followups
Confirmations, reminders and re-engagement messages triggered by real events: a booking, a job done, a service due, a payment missed. By SMS, Messenger or WhatsApp.
See it work
Each message is keyed to an event in the job, so it goes out when the thing it refers to has happened.
Illustrative. Sample business.
What’s included
Confirmations, reminders, thank-yous and service-due nudges, keyed to what the record says has happened.
Messages fire off a booking, a completed job, a due date or a missed payment. If the event has not happened, the message does not go.
Each customer is reached in the channel they already use, from one set of rules rather than three separate tools.
The system knows what was done and when, so the next-service nudge comes from the record instead of someone's memory.
Outstanding balances get a polite, timed follow-up that stops the moment the payment is recorded.
Opt-outs are honoured, sending windows are respected, and nobody receives the same message twice.
You can see what was sent, what landed, and what came back, per sequence and per customer.
Setup
The sequences are built on the events your business actually records, and on the tone your customers already hear from you.
Which events matter, what gets sent after each one, and which channel your customers actually read.
Message copy, timing windows, quiet hours, opt-out handling and the rules that stop a sequence early.
Replies that need a real answer, complaints and anything sensitive are routed to a person on your team.
Who it’s for
Not one campaign. The same handful of messages, owed on every job, to every customer.
Installs and repairs that come due again, where the next visit depends on someone following up.
Appointment confirmations, reminders and rebooking nudges that front desk staff cannot always get to.
Check-in details, renewals and payment reminders across more units than one inbox can carry.
FAQ
It is not a broadcast list. Each message is tied to something that happened on that customer's own record, opt-outs are honoured immediately, sending windows are limited, and there are caps on how often one person can be contacted.
We set up on the provider that works for your country and your volume, and we can keep the one you already pay for. The sequences are built so the provider can be changed without rewriting them.
Replies come back into one inbox. Simple answers can be handled by the rules you set; anything that needs a real answer is handed to a named person on your team with the thread attached.
Yes, once it is cleaned and the contactable records are separated from the rest. Reminders then run off live records going forward rather than a static export.
Tell us what your team is supposed to send and we will map the sequences with you.
Trusted by founders who’ve outgrown the standard