Close the company on specific weekdays
Disable normal booking availability on recurring closed weekdays such as weekends. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Disable normal booking availability on recurring closed weekdays such as weekends. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
A disabled weekday is excluded from the company schedule.
Providers inheriting company hours receive no normal slots on that day.
Staff-specific overrides may differ, so each provider's configuration must be reviewed when closure must be universal.
Follow these steps
- Go to Company Schedule.
- Find the weekday to close.
- Disable that day.
- Save the schedule.
- Test public and staff slot searches for that weekday.
Fields and decisions to review
How to confirm it worked
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
- Review provider overrides before claiming a universal closure.
- Use a blocked date for a one-off holiday.
- Existing appointments are not automatically cancelled by disabling a weekday.
- 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.
