Last updated:
Quick answer
Connect your booking calendar to an SMS tool through Zapier or Make. Every new appointment automatically triggers a confirmation, a 24-hour reminder, and a day-of nudge. You build it once and it runs itself.
At a glance
All outcome figures are estimates from cited sources, not independent verification by us.
- What it is allowed to do
- Acts for you
Takes real actions on a schedule or trigger: sends, posts, books, or updates without per-item approval. Check what it is allowed to touch before you turn it on.
- Time saved (estimate)
- Roughly 4–6 hours a week
- Difficulty
- Advanced
- Tools needed
- ChatGPT, Zapier
- Typical cost
- Zapier or Make: free tiers cover low volume; paid plans as you scale. SMS: roughly a few cents per message through most providers. Google Calendar: free.
Reviewed Oct 19, 2026
Basis (estimate): Estimate only: assumes automating reminders for 20–30 appointments a week eliminates manual calls and texts plus no-show firefighting. No timed study found.
What does this setup do?
Wire calendar bookings to automatic SMS reminders (confirmation, 24-hour, day-of) with filters, logging, and reply handling.
Who is it for?
Appointment businesses doing 20+ bookings a week who are ready to stop confirming everything by hand.
How do you set it up?
Tools
- Google Calendar, Calendly, or Acuity for bookings
- Zapier or Make (free tier to start)
- An SMS sender (Twilio, or your booking tool’s built-in SMS)
- ChatGPT or Claude for drafting the workflow and messages
Steps
- Pick your pieces: a calendar (Google Calendar works), an SMS sender, and Zapier or Make to connect them.
- Make sure every appointment lands on the calendar with the customer’s name, phone number, and appointment type in the event.
- Build the Zap: trigger on new calendar event, wait, then send SMS. Start with one reminder 24 hours before.
- Add the confirmation (fires at booking) and the day-of nudge as additional steps once the first one works.
- Test with your own number three times before turning it on for customers. Check timing, merge fields, and the STOP wording.
- Add a filter so only real customer appointments trigger texts, not your dentist appointment. Then turn it on and check the first week’s logs.
Example output
Illustrative. Your results will differ.
- This week: 6 bookings, 2 open slots left
- Reminder drafts ready for tomorrow's appointments
- You confirm before anything goes out.
Where to paste this prompt
ChatGPT: ChatGPT → Project instructions, or ChatGPT Tasks for scheduled reminders (once a day on Free)
Copy-paste prompt
Adapt bracketed fields to your situation.
Help me design an automated appointment reminder workflow.
BOOKING SYSTEM: [Google Calendar / Calendly / Acuity / other]
APPOINTMENT TYPES: [e.g. consult 60 min, service call 2 hr]
SMS TOOL: [e.g. Twilio, or "recommend one for low volume"]
AUTOMATION PLATFORM: [Zapier / Make]
Design the workflow step by step:
1. What triggers it (new event? event with a keyword?)
2. The message sequence: confirmation at booking, reminder 24h before, nudge day-of. Draft each message with merge fields for name, date, time.
3. What filters to add so internal events never trigger texts.
4. How to handle replies (confirm / reschedule): what breaks if nobody monitors replies?
5. A testing checklist before going live.
Flag the compliance requirements (consent, STOP wording) I must handle myself.Newsletter
Get the free starter pack
Free starter pack with five beginner copy-paste prompts after you confirm, plus three sourced setups in your inbox each week. Unsubscribe anytime.
What usually goes wrong?
Where agents tend to stall on this job. More patterns in Where AI gets stuck.
- Triggering on every calendar event, including personal ones. Filters are not optional.
- Merge fields pulling the wrong data. One test with a fake "John Test" appointment catches most of this.
- Ignoring replies. If a customer texts back "need to reschedule" and nobody sees it, you built a no-show machine.
- Compliance is on you. Consent to text and STOP opt-outs are legal requirements the automation will not enforce for you.
Which chat tools work with this prompt?
Paste the prompt into any of these assistants (free or paid tiers).
- ChatGPT
- Zapier
Common questions
- Zapier or Make?
- Either works. Zapier is simpler to learn. Make is cheaper at volume and more flexible. Pick the one you will actually maintain.
- What does this cost at scale?
- Roughly a few cents per SMS plus the automation platform tier. One prevented no-show usually pays for a month of messages.
- Can AI handle rescheduling replies too?
- Some setups route replies to a chatbot or a human. Start with replies going to your phone. Automate the conversation only after the reminders run clean for a month.
What tips make it smoother?
- Start with one reminder, not three. Get the plumbing right before adding steps.
- Use a delay step, not the event creation time, so the reminder lands 24 hours before, not the moment you book.
- Log every sent text to a sheet. When a customer says "I never got it," you have an answer.
- Watch replies for the first month. Automation that nobody monitors becomes a liability.
Where do the claims come from?
Summaries use public sources linked below, not independent verification. How setups are picked.
- Read Call Loop’s write-up (www.callloop.com)
Call Loop: Zapier automation walkthrough: Google Calendar trigger, delay, SMS action.
- Read Remindlo’s write-up (www.remindlo.co.uk)
Remindlo: Google Calendar to SMS reminder Zaps with filters and delays; cost math.
Related setups
- Write appointment reminder texts for your small business
Draft the three-message reminder sequence (confirmation, 48-hour, day-of) for each appointment type you offer.
- Plan a month of social media on one calendar
Fill a month-long content calendar (pillar, platform, post idea per slot) and plan the batch creation session to produce it.
- Build your first virtual assistant delegation list
Turn a week of your own task data into a ranked delegation list with clear first tasks, boundaries, and review points for your first virtual assistant.