Modify
Change information that influences feasibility: date, time, address, service, option or employee when the workflow allows it.
Help Centre · Booking
How do I modify or cancel a booking?
The documentation confirms that a booking added, modified or removed elsewhere should trigger a fresh availability calculation. It does not, however, define one universal cancellation button or workflow for every role.
Changing a booking also changes the day context
Changing a date, address, service, option or employee can make the previous availability invalid. Removing a booking can free time and change nearby periods. In both cases, review the day again after the action.
01Name the action
Modification and cancellation do not require the same check
Start by distinguishing a context change from a booking that must be removed.
Cancel or remove
End the booking using the action actually available in the workflow and for the current role.
Important: the reference documents do not confirm the same button, action right or cancellation workflow for every user.
02Recalculate what changed
A modification can invalidate the previous choice
Recheck the elements tied to the changed field instead of automatically keeping the previous availability.
Date or time
Recalculate candidate periods against the actual planned day.
Address
Recheck territory and travel when they are used.
Service or options
Recalculate total duration and the periods that can accommodate it.
Employee
Recheck schedule, absence, existing bookings and relevant travel.
After a relevant modification, review nearby periods: the documentation calls for recalculation when bookings are added, modified or removed from another interface.
03After removal
Review the day without inventing side effects
Removing a booking can change availability around it. The documents do not support automatically promising a refund, notification or full-day reorganization.
What is documented
Availability should remain coherent when a booking is removed or modified elsewhere.
What must remain explicit
Rights, communications and financial consequences depend on the workflow and features actually available.
04If the action does not behave as expected
Document the case before contacting support
A precise example helps distinguish a missing permission, normal recalculation and truly unexpected behaviour.
Useful context
- Page or workflow used.
- Requested action and changed field.
- Expected result, observed result and exact message.
- Non-sensitive booking identifier, if useful.
Related resources
Continue the review
Each resource completes a precise aspect of modification, cancellation, or the booking context.
Collection
Booking and availability
Explore guides about calculation, time models, absence of periods, and managing an existing appointment.
Explore booking guides →Calculation
How does MapMyStaff determine availability?
Understand how the request context is used to evaluate candidate periods.
Understand availability calculation →Models
What is the difference between AM/PM/EV and one-hour slots?
Understand the difference between a booking period and a proposed start time.
Compare booking models →Diagnosis
Why is no period available?
Follow a structured check when no period matches the requested context.
Diagnose the absence of periods →