Reminders and status updates that send themselves
Confirmations, reminders, payment links and status changes go out automatically at every step, so customers stop ringing to ask what is happening.
The problem
How it works by hand
Most where-is-my-booking calls exist because nobody told the customer anything. The confirmation went out, maybe, and then silence until the day itself. Every gap in communication becomes an inbound call, every forgotten reminder becomes a no-show, and the person answering the phone spends the day relaying information a system should have sent.
A worked example
What a working version looks like
Every status a booking or order can be in gets a defined message: confirmed, payment due, payment received, consent needed, rescheduled, on the way, cancelled, follow-up. When the status changes in your system, the right message goes out on the right channel, email, SMS or both, with the details merged in: time, address, what to bring, the payment link, who to contact. Reminders are scheduled relative to the appointment, not sent by hand, and a change to the booking automatically supersedes anything already queued so customers never get a reminder for a cancelled slot. Replies and failures route to a human, and every send is logged against the customer record.
The exact tools change per business. The shape does not.
What it needs
Honest inputs, nothing exotic
- 01Your booking, job or order system as the source of truth for status
- 02The message you want sent at each step, written once in your voice
- 03An SMS provider and sending email address
- 04Your rules on timing: how far ahead reminders go, and quiet hours
The payoff
What you get back
The questions get answered before they are asked, so inbound query volume drops and no-shows fall with it. Customers feel looked after at every step, and the person who used to relay it all by phone does something more useful.
Do it yourself
How you would build this yourself
No course, no upsell. This is the order we would build it in, with the tools named, and a prompt to start from.
- 1
List every status a booking or job can be in and write the message for each one, once, in your voice: confirmed, reminder, payment due, on the way, cancelled. That document is the system.
- 2
Check what your booking tool already does: Calendly, Acuity and most trade-specific tools have reminders built in that nobody switched on. Start there before building anything.
- 3
For the gaps, wire status changes to messages with Zapier, Make or n8n, with the details merged in: time, address, payment link, who to contact.
- 4
Add SMS via Twilio for the messages that must get read, and set quiet hours so nothing lands at 3am.
- 5
Test the edge cases hard: a rescheduled booking must kill the old reminders. A reminder for a cancelled slot does more damage than no reminder at all.
Build me automated customer updates. The source of truth is [booking system]. For each status change (confirmed, payment due, paid, reminder, rescheduled, cancelled), send the matching template from the attached document by email, with SMS via Twilio for the reminder and on-the-way messages. Merge in time, address and payment link. If a booking changes, cancel everything queued for the old slot before scheduling the new messages. Log every send against the booking and route replies to [inbox]. Respect quiet hours of [times].
Copy it into Claude Code, fill the brackets, and it will plan the build with you before writing a line of code.
We would rather show you how than bill you. The whole ladder of free help, answers, guides and the weekly build-along, is on the do-it-yourself page.
Go deeper