From a cancellation to a confirmed replacement booking

Check the complete opening

When a cancellation arrives, first inspect the actual appointment in your existing system. Which service was planned, who was assigned and how much time becomes available? Include preparation and finishing time. A cancellation message alone does not establish which replacement service can fit into the opening or whether every resource needed for it is available.

Prepare a suitable invitation

Choose a matching request using your waiting-list rules. The proposed message should clearly state the service, date, time and next action. Check that any price or service information comes from a current, confirmed source. Resolve unclear details internally before sending. The invitation should promise only what the team can actually provide and should be understandable without earlier conversation history.

Distinguish interest from reservation

Define which response merely expresses interest and which response triggers a confirmed booking. If the team temporarily holds a slot, make the length of that hold explicit. Internal states might be available, invitation sent, under review and confirmed. The essential point is that colleagues do not act on conflicting assumptions about whether the opening is still available.

Handle changes deliberately

Test what happens when a response arrives late. If the slot has already been allocated, the person needs a clear update. A change to the requested service may also require another duration check. An earlier proposal therefore should not be reused unchanged as a confirmation. Keep the current status in one agreed place that the responsible colleagues can access.

Check the final handover

Confirm that the booking appears in the authoritative appointment system and that the waiting-list entry has been updated appropriately. After a trial, discuss which handover remained unclear. The local draft helps plan these steps; real messages and calendar changes require a separately configured connection. A reliable process starts with clear states, rather than the largest possible number of automatic messages.