Understand status notifications and appointment activity
Trace which lifecycle actions create history and which configured messages may be sent to customers, providers or attendees.
What this feature does
Trace which lifecycle actions create history and which configured messages may be sent to customers, providers or attendees. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Status actions write appointment history or activity entries with the responsible user and timing.
Email and SMS delivery depends on enabled templates and trigger options for approval, cancellation, reminders, updates and other events.
Notification state is separate from status: a status can save even when an external email, SMS or calendar API fails.
Step-by-step workflow
- Open an appointment and review its current history.
- Identify the lifecycle action that produced each entry.
- Open appointment email and SMS settings to review enabled triggers.
- Perform a test status change on a non-production test record.
- Confirm both the saved status and delivery logs.
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 assume a successful status update proves message delivery.
- Keep templates active and recipient details valid.
- Use test records before enabling broad customer notifications.
- 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.
