Appointments & Scheduling · How-to guide

Understand status notifications and appointment activity

Trace which lifecycle actions create history and which configured messages may be sent to customers, providers or attendees. 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.

Audience: Staff who manage appointmentsFeature: Status activityModule v1.3.6
Jump to steps
Where to goAppointments > Open appointment > History / Settings > Templates
Before you startThis guide follows the supplied Britixo Appointments & Scheduling module version 1.3.6. The relevant access is Appointments: View. A menu, button, provider, time slot or client action can remain hidden when the signed-in user lacks the required permission, the module setting is disabled, the related record is in an ineligible state, or availability validation rejects the request.

What you’ll accomplish

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.

Follow these steps

  1. Go to an appointment and review its current history.
  2. Identify the lifecycle action that produced each entry.
  3. Go to appointment email and SMS settings to review enabled triggers.
  4. Perform a test status change on a non-production test record.
  5. Verify both the saved status and delivery logs.

Fields and decisions to review

Activity entryInternal audit record of a change.
Email templateFormatted message with appointment merge fields.
SMS triggerGateway-backed short-message event.
Delivery resultExternal message outcome distinct from database save.

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 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.
Scheduling and data safetyAppointment changes can notify customers, reserve provider time, update remote calendars, create meeting links or invoices and alter reports. Confirm the exact record, timezone, status and recipients before saving.