Skip to content
Docs home

CORE CONCEPTS · UPDATED AUGUST 2026

Bookings & Lifecycle

The booking is QUE's central object: five states, token-based customer management, and an event history that makes every change inspectable.

The five states

Every booking moves through a small, closed state set. The database enforces the valid values, and the operational surfaces are built around exactly these five.

StateMeaningTypical transition
pendingCreated, awaiting confirmation conditions (e.g. payment or manual confirmation)→ confirmed when conditions are met
confirmedReady to happen: slot held, staff and resource committed→ completed, cancelled, or no_show
completedThe appointment happenedTerminal
cancelledThe appointment will not happen, policy-appliedTerminal; slot released
no_showThe appointment window passed without the customer arrivingTerminal; policy may apply

What a booking connects

A booking is the intersection point of the whole model: it references the customer, the service, the staff member who owns it, the resource it consumes, the location, and the reminder waves planned for it. When any of those changes — a reschedule moves the time, a cancellation releases the slot — the connected objects update consistently because the change flows through the same booking API that created it.

Customer self-service

Customers manage their own bookings through the token in their confirmation link: they can cancel or reschedule without logging in. Token endpoints validate the token and the booking's tenant on every request, so a customer link can never reach another tenant's data and a stale link simply stops working.

Changes are operational events

A moved booking retains its reason or policy path, shows old and new state where appropriate, and makes ownership visible. A cancellation follows the approved policy. The system does not claim to prevent no-shows automatically — that is an operational decision the business makes.

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.