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.
Named schedules
Create multiple schedules under Availability for different working patterns, such as normal hours, support rotation, or interview days. One schedule is the default. Each meeting type may use the default or select another schedule.
Every schedule has:
- A name and IANA timezone.
- Independent weekly working windows.
- Available or unavailable date overrides.
The last schedule cannot be deleted. Deleting another schedule safely moves its meeting types to the default schedule.
Date overrides and out of office
Date overrides replace weekly hours for one local calendar date. Mark the date unavailable, or provide custom start and end times.
Out-of-office periods block every schedule owned by the user. Use them for holidays and other time away without editing each weekly schedule.
Slot troubleshooter
Choose a meeting type and start time in the Slot troubleshooter. Aroundtime reports whether the slot is available and identifies minimum notice, booking-window, schedule, override, out-of-office, booking, calendar, limit, or seat-capacity blockers.
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. |
| Slot interval | Distance between offered start times. |
| Booking limit | Maximum bookings inside a rolling number of days. |
| Reschedule notice | Deadline before the current start when rescheduling closes. |
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 the selected named schedule or an available date override.
- The user is not out of office.
- Minimum notice has elapsed.
- The date is inside the meeting type’s booking window.
- The rolling booking limit has not been reached.
- The slot still has group capacity when seats are enabled.
- No selected calendar is busy.
- No active 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.