Approve a pending appointment
Accept an eligible pending booking and allow configured confirmation, calendar and meeting actions to run. 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
Accept an eligible pending booking and allow configured confirmation, calendar and meeting actions to run. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The approval action requires the module Approve permission and verifies the appointment exists in an eligible state.
Approval updates status and history, then can send confirmation, add an external booking to Google Calendar and create or attach Google Meet according to settings.
Any automatic invoice flow remains subject to its separate contact, service price and source conditions.
Follow these steps
- Go to the pending appointment.
- Verify contact details, service, provider, timing and availability.
- Select Approve.
- Verify the resulting status and participant communication.
- Check calendar, meeting and invoice references where those features are enabled.
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 approve a slot that now conflicts with provider availability.
- Check public booking details for spam or incorrect contact information.
- A remote calendar failure should not be confused with failure to store the Britixo approval.
- 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.