Customise the booking form heading and description
Present clear Britixo-branded instructions above the public scheduling form without changing booking logic.
What this feature does
Present clear Britixo-branded instructions above the public scheduling form without changing booking logic. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Heading and description values are stored as module options and rendered by the public booking view.
The content sits above the service/provider/date workflow and does not change eligibility or availability.
All visible wording should remain branded as Britixo and avoid internal implementation names.
Step-by-step workflow
- Open Booking Form settings.
- Enter a concise Britixo heading.
- Add booking expectations, preparation or response-time information in the description.
- Save.
- Review desktop and mobile public views.
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 include confidential scheduling rules.
- Keep instructions consistent with terms and confirmation templates.
- Avoid overly long headings that crowd mobile layouts.
- 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.
