Configure blocked days and holidays
Remove one-off dates from booking availability without rewriting the normal weekly schedule.
What this feature does
Remove one-off dates from booking availability without rewriting the normal weekly schedule. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Blocked-date data is checked during slot generation after the requested date is received.
A blocked date can prevent slots despite otherwise open company or provider hours.
Existing appointments on a newly blocked date are not automatically resolved and require operational review.
Step-by-step workflow
- Open the module schedule or blocked-days settings.
- Add the holiday, closure or unavailable date.
- Apply the block to the intended scope where the interface permits.
- Save.
- Test the date and review any appointments already scheduled there.
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 change weekly hours for a single holiday.
- Blocking a date does not automatically notify existing participants.
- Check timezones when the closure crosses regional dates.
- 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.
