Send a custom appointment email
Follow this guide to send an authorised ad-hoc message from the appointment context while keeping standard automated templates unchanged. 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
Send an authorised ad-hoc message from the appointment context while keeping standard automated templates unchanged. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The custom-email action loads the appointment and permitted recipient context.
Staff provide a subject and body for this one communication.
The message uses the CRM mail service and can be recorded in appointment activity.
Follow these steps
- Go to the appointment.
- Select the custom email action.
- Verify recipients.
- Write a clear Britixo subject and message.
- Send and review delivery/activity.
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 use custom email to bypass approved templates for routine events.
- Avoid sensitive internal notes.
- Verify recipients before sending.
- 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.