Enable the public booking language selector
Allow visitors to switch supported interface language on the public appointment form.
What this feature does
Allow visitors to switch supported interface language on the public appointment form. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
A module option controls whether the public view exposes the language selector.
Available choices depend on installed and supported language files.
Changing language affects interface labels and translated strings, not appointment date, time or timezone values.
Step-by-step workflow
- Confirm the required CRM/module languages are installed.
- Enable the public language selector.
- Save.
- Open the booking form and switch language.
- Test the complete form and validation messages in each supported language.
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 promise a language that lacks complete module translations.
- Check email templates separately.
- Timezone must still be chosen or interpreted correctly.
- 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.
