The 10 a.m. slot does not show up. You still paid for the room, the staff, and the customer you turned away last week because that slot was taken. Multiply by every no-show this month and it stops being a shrug.
What it does
Every hour, the workflow checks tomorrow’s calendar. Twenty-four hours before an appointment, the customer gets a text: see you tomorrow at ten, reply C to confirm or R to reschedule. Two hours before, one last nudge. Replies flow back in and update the calendar, so you can see at a glance who is actually coming, and an R gets your booking link plus an alert to you.
How it works
Two small workflows. The first reads the calendar on a schedule, picks events entering the 24-hour and 2-hour windows, pulls the phone number from the event, and sends the reminder. A tracking sheet remembers what was already sent, so re-runs never double-text anyone. The second workflow catches inbound replies: C marks the event confirmed, R starts the reschedule conversation. Both are plain to read and easy to adjust to your own windows and wording.
Setup
- Import the two workflow files (reminders + replies) into your n8n instance.
- Connect Google Calendar and store each customer's phone number in the event description, the way the workflow's note shows.
- Connect Twilio and set its inbound messaging to the reply workflow's webhook.
- Create the small tracking sheet so nobody gets double-reminded.
- Book a test appointment for tomorrow with your own number and run it.
The template runs on n8n, any recent version, cloud or self-hosted. Every place that needs one of your accounts is marked with a note inside the workflow.
Get the workflow
Rather have this running in your business without touching a single node? That is the actual job. Write to hello@nurho.net or start with the ROI calculator to see if it is even worth automating.