Approve a client cancellation request
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to review the customer's pending request and apply the authorised cancellation flow with history and communication.
What you’ll accomplish
Review the customer's pending request and apply the authorised cancellation flow with history and communication. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it 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.
Follow these steps
- Go to the flagged appointment.
- Check the request reason and appointment details.
- Check calendar and invoice implications.
- Approve the cancellation.
- Verify Cancelled status, history and customer notification.
Settings to check
Check it worked
After this workflow completes, Pixie CRM 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 Pixie CRM 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.
Common mistakes to avoid
- 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.