The calendar moves an appointment to Thursday, but the customer still receives Tuesday's reminder. A successful reschedule has left its notifications on an older version of the booking.
Reminders need to follow the appointment's current state, not just the time they were originally queued.
Find which system owns each reminder
An external calendar, CRM automation, text provider, and custom worker can all generate messages. Start with an inventory of those paths before adding another notification.
For a fictional consultation, decide which system sends confirmation, advance reminders, change notices, and cancellation messages. Two independent “helpful” automations can produce duplicate or contradictory information.
| Notification | Required appointment evidence |
|---|---|
| Original confirmation | Successfully saved booking |
| Reschedule notice | Verified new time and relevant old reference |
| Advance reminder | Current, active appointment version |
| Cancellation message | Verified cancellation outcome |
Do not infer that a change notice was delivered merely because its job was enqueued.
Revalidate when a reminder is about to send
Where your notification architecture allows it, have the worker check the current appointment state and version before delivery. A reminder for a cancelled or superseded version should not describe it as active.
Use stable message-operation references so retries do not multiply notifications. Keep an explicit decision for cases where a change happens near the sending boundary; a message already accepted by an external provider may not be retractable.
Google documents calendar events and reminders. Custom notifications layered around a calendar need their own consistency policy rather than assuming every message is managed by that provider.
Recover the missing effect, not the whole reschedule
If the appointment changed successfully but the text failed, retry or review the notification step. Do not create a second appointment to make the workflow look complete.
Keep the resulting event reference and message status together. Staff should see “rescheduled, notification pending” rather than a vague global failure that hides the successful calendar update.
The rescheduling guide describes the appointment transition itself. This guide concerns the messages that follow it.
Test the send boundary
Use fictional cases where the customer reschedules before a reminder is queued, after it is queued, and while delivery is in progress. Add cancellation, a time-zone correction, and a notification-provider timeout.
Inspect message contents, recipient, delivery state, and the current appointment. A correctly cancelled background job is useful only if another automation does not send the stale message anyway.
Reminder questions
Is deleting a scheduled job always enough?
Not if the job has already started or another system also sends reminders.
Should failed texts reverse the booking?
Usually those are separate outcomes. Apply the business's documented policy.
What should staff receive?
Provide the current appointment and unresolved notification state in the handover.