WhatsApp platform3 min read
WhatsApp appointment reminder guide
A customer moves a Friday appointment to Monday. On Thursday evening the old reminder still arrives: “See you tomorrow.” This guide covers what happens after booking; for the first conversation, see the appointment qualification journey.
Four messages, one booking
| Message | Tells the customer |
|---|---|
| Confirmation | The slot is saved |
| Reminder | The existing appointment is coming up |
| Change | Which details replaced the old ones |
| Cancellation | The appointment is off |
All four read the same booking record: which appointment, whether it is active, date and time zone, branch or address, and how to request a change. Name the actual branch, not "your usual branch". Leave out personal details the customer does not need.
Give every reply somewhere to go
A fictional salon reminder (as an API template, it would still need Meta's review):
Your haircut at Sawsan Studio, Marina branch, is booked for Friday 18 September at 4pm, Dubai time. Please reply to confirm, ask to change the time, or cancel.
| Customer replies | Your team |
|---|---|
| Confirms | Records it against the appointment |
| Asks for another time | Checks the diary and saves the change before confirming |
| Cancels | Updates the booking and stops its remaining reminders |
| Will be late | Checks policy and capacity; promises nothing automatically |
| Asks for a person | Passes the chat to someone who can resolve it |
A read receipt is not a confirmation, and a missing one does not mean the reminder was missed.
Recheck before each send
A reminder scheduled at booking can go stale. Before it sends, check whether the appointment was cancelled, moved, reassigned or completed, and use the latest details.
- If a change fails, tell the customer it is still being resolved. Never announce a time the booking system has not saved.
- Decide which process owns each message, so a manual reminder and an automatic one never both go out.
- Ask any booking integration to show this with a test appointment: read status, detect a change, stop the old reminder.
Time reminders to the appointment
No single schedule fits a short salon visit, a home repair and a course booked weeks ahead. Consider when the customer must prepare, how much notice your team needs for a change, and what the customer agreed to receive.
Start modest, review the replies, and make sure last-minute bookings do not get a backlog of early reminders.
When delivery fails
Keep "undelivered" separate from "delivered, no reply". The first needs action; the second may mean the customer has nothing to add.
Some booking systems can fall back to text; check the cost and whether the customer agreed to that channel. Otherwise assign the failed reminder to a person, who rechecks the booking before retrying.
WhatsApp rules to plan around
- A reminder outside the customer service window needs an approved template.
- Adding a discount for the next visit can change its template category.
- Meta charges for reminder templates, even inside the window. See the pricing guide.
- A "Change time" button must lead to a real change process.
Preview wording with the message builder. It creates a copyable preview; it does not schedule anything or submit a template to Meta.
Measure appointments, not messages
Track attended, cancelled, rescheduled and unexplained missed visits separately, from the booking system. A missed-visit rate is unexplained misses divided by appointments still expected to happen; keep that definition fixed and report the counts too.
A before-and-after change does not prove reminders caused it: service mix, staffing and season all move attendance. Review failed cases one by one. Was the reminder wrong, late, undelivered or unanswered?
Where Otobiz fits
Otobiz Appointments collects the service, day and time in the chat, and passes each request to your team to confirm. Replies to reminders land in the shared inbox, where your team sees what has already gone out.
