Cancel an appointment as staff
Cancel an appointment directly with authorised staff access and preserve the cancellation outcome, communication and history. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Cancel an appointment directly with authorised staff access and preserve the cancellation outcome, communication and history. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
A staff cancellation action validates the appointment and permission before storing Cancelled status.
Configured cancellation email or SMS messages can be sent to participants, and remote calendar events may need update or deletion.
The appointment remains in history and reports rather than being erased.
Follow these steps
- Go to the appointment and verify it is the correct record.
- Select Cancel.
- Enter or record the cancellation reason where supported.
- Verify participant communication and calendar handling.
- Verify Cancelled status and the history entry.
Fields and decisions to review
How to confirm it worked
After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Controls, checks and common mistakes
- Do not delete an appointment when a cancellation history is required.
- Check whether a linked invoice needs separate financial action.
- A client cancellation request must be approved or processed rather than silently overwritten.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.