Add and use appointment custom fields
Capture organisation-specific appointment information through the module's supported custom-field integration.
What this feature does
Capture organisation-specific appointment information through the module's supported custom-field integration. 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 registers appointments as a custom-field context and loads enabled fields into supported staff and public forms.
Submitted values are saved through the CRM custom-field value system and returned with the appointment record.
Visibility and required behaviour depend on each custom-field configuration and the form context.
Step-by-step workflow
- Open the CRM custom-field configuration.
- Create a field for the Appointments context.
- Set its type, label, order, required status and visibility.
- Open a staff or public appointment form and test the field.
- Save an appointment and verify the value on the detail view.
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 expose staff-only or sensitive fields on the public form.
- Changing a field type after data exists can make old values harder to interpret.
- Test required fields in every enabled booking context.
- 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.
