Skip to content
Docs home

OPERATIONS · UPDATED AUGUST 2026

Booking Operations

Creating, cancelling, rescheduling, and reconciling bookings — including the failure states operators actually have to handle.

Creating a booking

Bookings are created through the public booking surface or the operator dashboard. Creation runs the full availability computation, reserves the staff and resource for the window, plans the reminder waves for the new booking, and returns the confirmation view with the customer's management link. The booking starts in the pending state and moves to confirmed when its conditions (for example payment, where required) are satisfied.

Cancelling and rescheduling

Customers cancel or reschedule through their token link; operators do the same from the dashboard. A cancellation releases the slot so the availability engine can re-offer it, fires the booking_cancelled event through the notification system, and — if outbound webhooks are configured for cancellation events — delivers it to the tenant's endpoints. A reschedule moves the booking to a new slot, releases the old one, and preserves the change in the booking's history.

When a booking cannot be made

Operators need to distinguish five different kinds of rejection, because each has a different recovery. The table below maps them.

RejectionWhat it meansRecovery
Not offeredAvailability computation refuses the windowCheck the availability dimensions — see Availability
Not availableSlots existed but were taken between view and bookingPick another slot; the engine prevents double booking
Not permittedThe request lacks the role or token rightsCheck role or use the customer's own management link
Provider unavailableA payment or messaging dependency rejected the requestCheck the provider connection and retry when healthy
Configuration incompleteA required dependency (resource, channel, provider) is not set upComplete the configuration before offering the service

Reconciliation

When an external provider is involved (payment, calendar), the booking record stores what the provider returned alongside what QUE accepted. If the two disagree — a payment that never settled, an event that never landed in a calendar — the operator reconciles from the booking's stored provider state, not from memory.

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.