Holiday closures and special days: protecting the calendar from wrong bookings
Closures and absences should be managed before customers can find available slots on non-working days.
Quick answer
Closures that are not planned in the platform create a painful mistake: the customer books, receives confirmation and then must be contacted again. Planning these blocks early also protects the business reputation, because it avoids awkward explanations after an automatic confirmation has already been sent.
- Full closure
- Single staff absence
- Reduced hours
Block dates before publishing
Holidays, staff leave and training days should be excluded from the public calendar in advance.
- Full closure
- Single staff absence
- Reduced hours
Check reopening dates
A block with no end date may hide useful availability. A missed closure may open the wrong slots.
- Start date
- End date
- Staff involved
Communicate consistently
When opening hours change, the public page, messages and team should all say the same thing.
- Website notice
- Updated confirmations
- Team alignment
Blocks to review
- ✓ Staff holidays
- ✓ Business closures
- ✓ Special opening hours
- ✓ Reopening dates configured
Continue reading
Useful next pages
FAQ
When should closures be added?
As early as possible. Late closures force the team to move bookings that were already confirmed.
