Use Appointments history
Review the module-wide chronology of appointment creation, updates, approvals, status changes, requests and communications.
What this feature does
Review the module-wide chronology of appointment creation, updates, approvals, status changes, requests and communications. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The History controller loads appointment activity records under module access checks.
Entries connect actions to appointment context, responsible staff and timestamps where available.
History supports investigation but does not replace CRM server, mail or external API logs.
Step-by-step workflow
- Open Appointments > History.
- Filter or locate the relevant appointment activity.
- Compare entries with the appointment detail page.
- Open the source appointment.
- Use external logs when delivery or calendar evidence is required.
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 edit history merely to hide an error.
- Use mail/API logs for external delivery evidence.
- Confirm timezone when comparing timestamps.
- 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.
