Skip to main content
RoutMe
All posts
Playbooks5 min read

Appointment reminders and follow-ups without Zapier

Send WhatsApp appointment reminders and follow-ups with RoutMe Flows: an external event trigger, an approved template, wait steps and a reply path. No Zapier needed.

VR

Vinita Rathi

Product and conversation design

To send appointment reminders and follow-ups on WhatsApp without Zapier, build a RoutMe Flow with an external event trigger that your booking tool posts to, a send template step for the reminder, and wait or delay until steps for the follow-up. Replies from the customer land in the same flow system and the inbox, so a person can pick up anything the flow cannot handle.

A typical Zapier version of this uses a calendar or booking trigger, a delay, a formatter and a WhatsApp provider step. It works until a booking is edited, a template is rejected, or a step fails silently. This guide rebuilds the same behaviour with fewer moving parts, and it is honest about the one thing a flow does not do, which is run on a clock.

What you need first

  • A WhatsApp number connected to RoutMe through Embedded Signup.
  • Customers who have opted in to receive messages from you. Collect it and record it, because WhatsApp opt-in rules apply to reminders too.
  • An approved template for the reminder, and one for the follow-up.
  • A way for your booking tool to call a URL when something happens.

Step 1: Write and approve the templates

Reminders are messages you start, often after a long silence, so they must be templates. In the templates area you set a lowercase name, a category, a language, a body with numbered variables and, optionally, a header, footer and buttons. RoutMe submits it to Meta when you save. Review usually takes minutes and can take up to a day.

  • File reminders and confirmations as utility. A promotional tone filed as utility is the most common reason for rejection.
  • Lead with words, not a variable, and never place two variables next to each other.
  • Keep each language as its own template.

An example body: Hi {{1}}, a reminder that your appointment is on {{2}} at {{3}}. Reply here if you need to change it. If you already have approved templates in WhatsApp Manager, import them instead. Background in WhatsApp message templates and approval.

Step 2: Create the flow and its trigger

Create a flow with the external event trigger and set its event name, for example appointment booked. Your booking tool then posts an event with that name, the customer's WhatsApp number and a data object holding the name, the date and the time. Everything in that data object is readable in later steps as an event field, so the template parameters can be filled from it. The call needs a connected WhatsApp number, and a trigger without an event name never matches.

If your tool cannot post to a URL, a small piece of your own code or a tool in the middle, such as a Zap or an n8n workflow, can do it. Keeping one in the middle for scheduling is a perfectly good design. It is covered in do you still need Zapier.

Step 3: Confirm, wait, remind

  1. 1Add a send template step for the booking confirmation, filling its parameters from the event data.
  2. 2Add a wait step. It pauses for a number of seconds, up to 30 days, and the run is saved and resumes on its own.
  3. 3Add a send template step for the reminder.
  4. 4Optionally add a delay until step to hold the reminder until 09:00 in your customers' timezone instead of the exact moment the wait ends.

Run status shows waiting while a run is parked. If the wait you need is longer than 30 days, post the event later from your own system instead of waiting inside the flow.

Step 4: Handle the reply

When the customer writes back, their message opens the 24-hour service window. A second flow with the message received trigger can answer in free text. A simple pattern is an If step that checks whether the message contains a word such as cancel or reschedule, routing those to the assign step so a teammate takes over. The agent step can handle softer replies, such as questions about where to park, if you give it the right knowledge and keep it away from changing bookings.

Step 5: The follow-up

A follow-up after the visit is the same shape: an event after the appointment, a wait if you want a gap, then a template that thanks the customer and asks one question. Keep it short and useful. Marketing content in a follow-up changes its category, its price and the quality signal Meta watches, and customers who opt out must not be messaged again. A flow can use the opted out trigger to record that.

Step 6: Test and read the traces

  1. 1Post a test event to a number you control.
  2. 2Check that the confirmation arrives with the right values in the right places.
  3. 3Shorten the wait for testing and confirm the reminder arrives.
  4. 4Reply cancel and check that it reaches a person.
  5. 5Open the run and read the trace. A template that is not approved fails visibly and says so.

What this does not replace

Zapier or n8n still make sense for syncing the booking into other tools, writing to your calendar, or any schedule-driven job. A flow is started by a message, an opt-in or opt-out, a status change or an event, and not by a timer. If you can accept that, the customer-facing half no longer needs a general automation tool at all.

For cost, remember that each template you send is billed by Meta by category, so more reminders means a bigger bill. See WhatsApp per-message pricing explained and RoutMe's pricing. The Flows overview lists the steps, Move to RoutMe covers every migration path and you can try this live in a demo. For clinics specifically, read AI chatbot for clinics and appointments.

Keeping reminders from becoming noise

A reminder is useful once. Two or three become a reason to block your number, and blocks and reports lower the quality rating Meta keeps for each number, which can limit what you are allowed to send. A few habits help.

  • Send one reminder and one optional confirmation, not a sequence.
  • Include the one thing the customer might need to act on, such as the address or how to change the time.
  • Use the Filter step so that a cancelled booking never triggers a reminder.
  • Tag customers who ask not to be messaged, and honour the opt-out immediately.

Because every run is recorded, you can check afterwards which customers received what and when, which is a good habit if a customer ever disputes it.

  • Migration
  • Zapier
  • Templates
  • Flows
VR

Vinita Rathi

Product and conversation design

Writes about where automation belongs in a support conversation, and where it does not.

Frequently asked questions

Can a flow send a reminder at a set time before an appointment?

A flow cannot run on a calendar by itself. Your booking tool posts an event, and the flow can wait and then send. If your tool can post the event close to the reminder time, no wait is needed. Otherwise use your own scheduler to post it.

Do I need an approved template?

Yes, for any message you send first. A reminder goes to a customer who may not have written to you for days, so it must be a template, usually in the utility category.

What if the customer replies to reschedule?

Their reply opens the service window, so the flow or the agent can answer in free text. Rescheduling itself is a change to your booking system, so either hand off to a person or build that action deliberately.

See it on your own data

Connect a system, drop an agent node into a flow, and watch it answer from what is actually true in your systems right now.