Understand appointment statuses
Use Pending, In Progress, Completed, Cancelled and No Show consistently so notifications, reports, feedback and calendar actions reflect the real outcome.
What this feature does
Use Pending, In Progress, Completed, Cancelled and No Show consistently so notifications, reports, feedback and calendar actions reflect the real outcome. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Status is stored on the appointment and controls which actions the module exposes.
Pending supports an approval decision, In Progress represents active delivery, Completed closes successful work, Cancelled records a stopped booking and No Show records non-attendance.
Status changes can add history, send configured messages, update remote calendars or trigger later feedback and reporting behaviour.
Step-by-step workflow
- Open the appointment detail page.
- Confirm the current status and source.
- Choose the next valid lifecycle action.
- Add a reason or note where the interface requests one.
- Save and verify history, notifications and calendar state.
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 mark a cancellation as No Show merely to avoid an approval flow.
- Completed status should reflect delivered work, not only a past date.
- Review communication triggers before changing a customer-facing appointment.
- 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.
