Skip to content
Docs home

CORE CONCEPTS · UPDATED AUGUST 2026

Availability

Availability is an intersection: service duration, staff schedule, resources, existing bookings, and overrides must all agree before a slot is offered.

The intersection model

QUE does not offer slots by decorating a calendar. When the public booking page asks for availability, the engine intersects every constraint the service declares. Only a window where all dimensions agree is offered. If any dimension rejects the window, the slot does not appear — the customer never sees, and can never take, a slot the constraints refuse.

textWhat the availability computation intersects
Slot is offered only if ALL of these hold:

  Service duration fits the window
  AND assigned staff are scheduled (and not overridden out)
  AND required resources are free for the whole window
  AND no existing booking occupies the staff or resource
  AND the location's schedule covers the window
  AND timezone conversion places the slot in real working time

The dimensions

DimensionSourceRejection looks like
Service durationService configurationWindow too short to fit the service
Staff scheduleStaff record + overridesNo assigned staff available at that time
ResourcesResource configurationThe required room or device is occupied
Existing bookingsBooking recordsThe staff or resource is already committed
Location scheduleLocation configurationThe place is closed at that time
TimezoneTenant / location timezoneSlot lands outside real working hours

Behavior customers and staff see

From the customer's side, availability behaves like a simple calendar — but one that never over-promises. From the staff and operator side, a missing slot is diagnostic: the dimensions table above is a checklist. Check each dimension in order until one rejects the window, then fix the configuration rather than working around it. The Troubleshooting section includes the full slot-not-offered ladder.

Why this matters

Most booking failures in production are not bugs — they are constraints doing their job. A system that silently offers impossible slots creates the failures that destroy customer trust. A system that refuses them creates configuration work instead. QUE chooses the second.

STILL READING

Something here still feels worth checking together.

This documentation describes the product exactly as it is implemented. If a behavior you expected is not here — or is here and does not match your deployment — tell the team. Implementation questions start on the contact page.