A reminder sent after a last-minute change can tell the customer to attend the old time. The messaging workflow should follow the current appointment version rather than a copied timestamp from the original booking.
Define which changes require a revised notice: time, location, stylist, service scope, or cancellation. Keep reminders distinct from change confirmations. A successful reschedule should not automatically trigger several messages with overlapping purposes.
Link message intent to appointment version
Store the appointment identifier, version or last-verified state, message purpose, scheduled send time, and outcome. Before sending, compare the intended content with the current verified commitment. Retire messages that are no longer valid under the salon's policy.
A simple delay does not solve stale content. It can merely postpone the wrong message. The workflow needs an explicit check or supported event-driven update when the appointment changes.
Work through a fictional same-day move
A customer moves from two to four in the afternoon. A reminder for the original time is already queued, while staff also change the assigned stylist. The workflow verifies the final booking and sends the approved change notice with the correct time and stylist.
The old reminder should not later repeat the two o'clock appointment. If the message was already sent, the new notice should clearly identify the current arrangement rather than pretending the earlier communication never happened.
| Change scenario | Required messaging behavior |
|---|---|
| Time moves before reminder send | Old content retired or refreshed |
| Reminder already delivered | Accurate revised notice |
| Stylist changes | Customer-approved assignment reflected |
| Appointment cancelled | No future attendance reminder |
| Send outcome uncertain | Reconcile before duplicate send |
Verify delivery separately from booking
An updated appointment can be correct while the notification fails. Keep both outcomes visible to staff. The salon may need a callback for a consequential same-day change rather than relying on an unverified message.
Version-aware messaging requires more state than a static scheduled text. It also prevents confusing customers with outdated instructions. A small salon can begin with one message owner and a manual review of last-minute changes, then automate the boundary when the platform supports reliable updates.
Test reschedule, cancellation, branch change, and concurrent staff edits. Review duplicate message triggers for the broader distinction between repeated events and repeated customer messages.
Questions about salon reminders
Should every field change send a new text?
Only changes covered by the salon's communication policy should trigger customer notices. Internal note edits should not generate unnecessary messages.
Does a delivered reminder prove the customer accepted the change?
No. Delivery, acknowledgment, and agreement are separate states.
What if the final booking state cannot be read?
Pause the automated notice or route to staff under the approved fallback. Do not send a confident reminder based on uncertain old data.