Configure staff working hours
Define provider-specific weekly availability or choose to inherit the company schedule.
What this feature does
Define provider-specific weekly availability or choose to inherit the company schedule. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Working-hour records are stored per staff member and weekday.
A provider can use the company schedule or maintain independent enabled days and start/end times.
The availability engine evaluates these hours only after confirming the provider is active and assigned to the selected service.
Step-by-step workflow
- Open Staff Working Hours.
- Select the provider.
- Choose company schedule inheritance or provider-specific hours.
- Configure enabled weekdays and time windows.
- Save and test the provider against an assigned service.
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
- Configuring hours does not assign services.
- A provider with no valid working window cannot generate slots.
- Check timezone when staff work in different regions.
- 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.
