How to Automate the Rescheduling of Appointments
A patient who needs to reschedule shouldn't have to call, wait on hold, and explain everything all over again. Rescheduling can be done right during the call.

For many patients, rescheduling an appointment is more difficult than it should be: it involves calling during business hours, waiting for someone to answer, explaining the original appointment all over again, and only then hearing about the available alternative times. For those calling during a work break, that’s time they often don’t have—and the result is that the original appointment goes rescheduled, effectively becoming a no-show.
This guide shows you how to set up an automated rescheduling workflow using WhatsApp, using the calendar management and the automation builder from WhatSMS.
Step 1 — Sync the clinic’s calendar
Connect the clinic’s Google Calendar or Microsoft Outlook to WhatSMS. This integration is bidirectional and real-time, so any manual changes made to the schedule (for example, a staff member blocking off a time slot) are immediately visible to the rescheduling system.
Step 2 — Create the rescheduling workflow
In the drag-and-drop visual editor, drag a keyword trigger node (for example, “reschedule” or “change appointment”) that fires whenever a patient responds to the confirmation email requesting a new date. Link it to a message node to confirm that you’ve received the request and to check the original appointment associated with the contact.
Step 3 — Check actual availability and suggest alternatives
Add a condition node that checks the synchronized calendar and returns the earliest available time slots closest to the requested date. The patient chooses directly within the conversation, without the front desk needing to manually intervene to check availability.
Step 4 — Handle the case where no time slot is available
Set up an action node that, when no nearby time slot is available, notifies a human agent with the request and the context of the conversation—instead of leaving the patient without a response. It is this fallback mechanism that prevents a rescheduling request without an immediate solution from silently turning into a no-show.
What this prevents, in practice
A difficult rescheduling often has the same result as no rescheduling at all: the patient gives up trying to reschedule and simply doesn’t show up on the original date, without notice. Streamlining the process—making it as simple as replying to a message—reduces this likelihood because it removes the friction that leads to patients giving up.
Multiplied by dozens of reschedules over the course of a year, the time saved by the front desk by not having to manually manage each reschedule over the phone adds up to a considerable number of hours, even if each individual case seems minor.
You can Create this rescheduling workflow for free and test it against your clinic's actual schedule before making any appointments.
Frequently asked questions
Does the patient need to suggest a new date right in the first message?
No. The workflow can simply ask if the user wants to reschedule and only then present the available time options, guiding the conversation step by step.
What if the patient requests a date on which there are no more appointments available?
The condition node checks only the times that are actually available in the synchronized calendar, so it never suggests a date for which there is no availability.
Do we need to rewrite the workflow for each staff member at the clinic?
Not necessarily—the same workflow can access the specific calendar of the professional associated with the original appointment, without duplicating the logic for each person.
What happens if the patient does not respond to any of the proposed options?
The conversation appears as pending on the team dashboard, and the team can decide whether to send an additional reminder or contact the patient through another channel.
Does this require any integration beyond the calendar?
No. Calendar synchronization (Google Calendar or Microsoft Outlook) and the WhatsApp channel are sufficient for the rescheduling workflow to function.