Keep a booking clear when plans change.
A booking is more than a calendar slot. The person delivering the work needs the right time, place, scope and latest instructions. A change should travel through that whole path, not stop at the inbox where it arrived.
Choose the current booking record.
Decide which system owns the booking details. Other views can show those details, but the team needs to know where to check when two versions disagree. Record the booking reference, owner and confirmation state.
Keep an enquiry, a provisional hold and a confirmed booking distinct. A request for a date does not establish availability or a customer commitment.
Check the handoff before the day.
The person delivering the work should be able to find the agreed time, location, relevant access information and any preparation required. Give them a way to acknowledge a material change.
- Customer changes the time
- Check availability, agree the change and update the current record.
- Location or instructions change
- Update the delivery details and confirm the relevant person has seen them.
- The booking is cancelled
- Record the cancellation, stop dependent reminders and handle commercial terms according to the agreement.
- The update fails to transfer
- Flag the affected booking and use the agreed manual route.
Follow one changed booking.
Illustrative example: a customer moves an appointment from Tuesday to Thursday. The office changes the current record, but the delivery team still has Tuesday in a separate calendar. The handoff is incomplete until that mismatch is resolved.
A useful check compares the affected booking and confirms the recipient received the latest details. It does not assume that a successful “update” notification proves every connected view changed.
Prepare for seasonal changes.
When hours, availability or staffing change, review the information shown on the website, booking tool and customer messages together. Identify who changes each surface and how the team checks the result.
Use actual dates and working arrangements. Do not leave last season’s availability in a saved reply or turn a provisional plan into a public promise.
Test cancellation and recovery.
Before relying on a connection, test a change, a cancellation, a duplicate notification and a failed transfer using clearly labelled test records. Check that replaying a failed update does not create a second booking.
The process should have a named person who can pause reminders, correct the record and tell the affected people what happened.
