Approve a client cancellation request
Review the customer's pending request and apply the authorised cancellation flow with history and communication.
What this feature does
Review the customer's pending request and apply the authorised cancellation flow with history and communication. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The staff action requires Approve permission and a valid pending request.
Approval changes the request and appointment state, adds history and can send cancellation messages.
Calendar and invoice consequences remain separate integrations to review.
Step-by-step workflow
- Open the flagged appointment.
- Review the request reason and appointment details.
- Check calendar and invoice implications.
- Approve the cancellation.
- Verify Cancelled status, history and customer notification.
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
- Do not approve the wrong appointment.
- Check service cancellation terms.
- Process financial adjustments separately.
- 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.
