Aroundtime offers a slot only when it fits inside your working hours and does not overlap a selected calendar or an existing Aroundtime booking.
Working timezone
The onboarding flow detects an IANA timezone from the browser. You can accept it or search by city and region to select another timezone. The same searchable selector is available under Availability.
Working hours are interpreted in this timezone. Guests see the resulting slots translated into their own browser timezone.
Weekly hours
Choose one or more working days and a shared start and end time. Aroundtime creates one availability rule for every selected day.
A valid schedule requires:
- At least one enabled day.
- An end time after the start time.
- A valid IANA timezone.
Meeting-level timing rules
Each meeting type adds its own constraints:
| Rule | Effect |
|---|---|
| Duration | Length of the meeting. |
| Before buffer | Reserved time immediately before the meeting. |
| After buffer | Reserved time immediately after the meeting. |
| Minimum notice | How soon a guest may book. |
| Booking window | How far into the future the booking calendar extends. |
Buffers participate in conflict detection. A guest cannot book a slot whose reserved window overlaps another booking or calendar event.
How a slot becomes available
A slot must pass every check:
- The full reserved window is inside working hours.
- Minimum notice has elapsed.
- The date is inside the meeting type’s booking window.
- No selected Google calendar is busy.
- No confirmed Aroundtime booking overlaps.
- The slot still exists when the guest confirms.
The final booking uses an atomic database insert, so two guests cannot confirm the same host time concurrently.