Configure company working hours
Set the normal opening and closing windows used when staff inherit the organisation schedule.
What this feature does
Set the normal opening and closing windows used when staff inherit the organisation schedule. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Each weekday can be enabled with a start and end time or disabled.
Saved values are read by provider availability when the provider uses company schedule.
A requested slot must fit fully inside the applicable working window after service duration and buffers are considered.
Step-by-step workflow
- Open Company Schedule.
- Enable each normal operating weekday.
- Set opening and closing times.
- Disable days when the organisation is normally closed.
- Save and test opening, middle and closing-edge slots.
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 set an end time that leaves no space for the service duration.
- Use blocked days for one-off closures rather than changing the weekly pattern repeatedly.
- Test the boundary with service buffers included.
- 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.
