Delete an appointment safely
Remove an appointment only when deletion is appropriate and the organisation does not need its status, history, invoice, calendar or feedback evidence.
What this feature does
Remove an appointment only when deletion is appropriate and the organisation does not need its status, history, invoice, calendar or feedback evidence. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The delete action requires Appointments Delete permission and targets the native appointment record.
Related attendee, service, custom-field, history or integration data may be cleaned by module logic, while external calendar or financial records can require separate handling.
Deletion differs from cancellation because it removes operational evidence instead of preserving a cancelled outcome.
Step-by-step workflow
- Open the full appointment and confirm its identity.
- Check status, customer relationship, invoice, recurrence, feedback and remote calendar references.
- Prefer Cancel when the booking existed operationally and history matters.
- Use Delete only with authorised reason and confirmation.
- Verify the record and any orphaned remote event are no longer accessible.
Important fields and decisions
What happens after completion
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
- Never delete merely to improve report figures.
- Do not delete a recurrence parent without reviewing future cycles.
- Confirm legal, audit and customer-service retention requirements.
- 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.
