Choose a primary service provider
Set the preferred provider for a service while retaining other eligible staff as alternatives.
What this feature does
Set the preferred provider for a service while retaining other eligible staff as alternatives. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The primary provider is stored alongside the service-provider relationships.
Interfaces can use it as the preferred provider, but availability must still be confirmed for the chosen slot.
Other assigned providers remain eligible unless removed or inactive.
Step-by-step workflow
- Open the service.
- Confirm the preferred person is already in the assigned provider list.
- Select that person as Primary provider.
- Save the service.
- Test booking behaviour when the primary provider is available and unavailable.
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 select a primary provider who is not assigned to the service.
- A primary designation should not bypass an unavailable schedule.
- Review the primary provider when responsibilities change.
- 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.
