Business hours, holidays, and booking edge cases
Avoid false availability by treating timezone, holidays, breaks, buffers, and temporary closures as first-class rules.
Booking
Business hours, holidays, and booking edge cases
Why this matters
Most availability mistakes happen around exceptions: lunch breaks, daylight-saving changes, staff leave, holidays, or a temporary closure.
Recommended workflow
- Store the business timezone separately from the caller's timezone.
- Layer regular hours, breaks, holidays, and date-specific overrides.
- Apply service duration and buffer time before presenting options.
- Explain unavailable dates without inventing a reason.
Quality checks
- Tests cover dates near timezone and daylight-saving boundaries.
- Blocked time cannot be booked through an alternate call path.
- Temporary overrides have an owner and expiry date.
Practical takeaway
Availability is a rule system, not a list of opening times. Test exceptions before normal dates.
Sources and VoxsAgents research note
This article is original VoxsAgents workflow analysis informed by product behavior, failure-path review, and the official primary references below. It is not a customer outcome study.
- Create events — Google Calendar API — Google for Developers
- Handle API errors — Google Calendar API — Google for Developers
- NIST AI Risk Management Framework — National Institute of Standards and Technology
Treat this guide as an operating starting point. Test the workflow with the business's real rules, tools, permissions, and failure paths before using it with callers.