Plan for changing plans
A booking rarely exists in isolation. Someone may need to arrange travel, move another appointment, or coordinate with a colleague. When a time changes, the product should help them understand the new situation. Begin with a clear record of the original appointment, the proposed replacement, and whether the change has been confirmed.
Distinguish a request from a confirmation
A customer asking for a different slot is not the same as a slot being reserved. Make those states visible. If approval is needed, explain who will respond and what the customer should do while waiting. Do not send a confirmation message until the booking system has actually accepted the new arrangement.
Keep the details together
Show the date, local time, location or joining instructions, and any preparation notes in one place. When a booking changes, update the information consistently across the customer view and the staff view. A short change history can help the support team understand what happened without asking the customer to repeat the story.
Make recovery a normal option
Provide a clear way to cancel, request help, or choose another time. Explain relevant conditions before the person commits to the change. Test a fully booked day, an unavailable staff member, and a customer returning after a long pause. The goal is not to prevent every disruption. It is to help people recover without confusion.