Configure appointment SMS triggers
Choose which appointment events send SMS through the main Britixo SMS gateway, including approval, cancellation, reminders and updates.
What this feature does
Choose which appointment events send SMS through the main Britixo SMS gateway, including approval, cancellation, reminders and updates. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The module exposes SMS trigger options for supported appointment events.
When a trigger runs, the module passes appointment merge data and recipient telephone details to the CRM SMS gateway.
Gateway configuration, active trigger and valid recipient number are all required.
Step-by-step workflow
- Configure the CRM SMS gateway.
- Open Appointments SMS settings.
- Enable only approved triggers.
- Verify customer/provider telephone formats.
- Run approval, cancellation and reminder tests.
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
- Control message length and cost.
- Do not enable SMS without consent and valid numbers.
- Check gateway logs separately from appointment history.
- 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.
