Skip to content
Docs home

GET STARTED · UPDATED AUGUST 2026

Introduction

QUE is a booking-led operations system. A booking is not just a timestamp: it connects a customer, a service, staff responsibility, an availability rule, resource constraints, and an event history.

What QUE is

QUE organizes service businesses around the booking. Every part of the product — services, availability, staff, resources, reminders, payments, webhooks, and the public booking surface — exists to make one thing dependable: a customer arriving at the right time, with the right person and room, without anyone having to chase it down manually.

This documentation is task-oriented. Each page explains one behavior end to end: what it does, how to configure it, what to expect, and what to check when it does not behave. Every capability documented here was verified against the running product implementation. Features that are planned but not shipped are not listed as available.

Who this documentation is for

Different readers need different parts of this documentation. The platform serves two audiences at once — the business operating its bookings, and the technical team configuring, integrating, or hosting QUE. The table below maps each audience to the sections that matter most.

If you are…Start withThen read
A business operatorQuickstartBooking operations → Reminders
Staff on a teamRolesBooking operations
A developer integrating QUEAPIAuthentication → Webhooks
An implementer or self-hosting adminSelf-hosting architectureEnvironment → Observability
A security evaluatorTenant isolationSecurity controls

The booking-led operating model

Everything in QUE is organized around a single object: the booking. A booking is created through the public booking surface, which runs a real availability computation — service duration, staff schedules, resources, existing bookings, and overrides all intersect before a slot is offered. Once created, a booking moves through a small, well-defined state set: pending, confirmed, completed, cancelled, or no-show.

Around that core, QUE automates the operational work that normally falls on humans: reminder waves fire on schedule (booking_created, day_before, two_hours), payment sessions reconcile through provider webhooks, and outbound webhooks push events to the systems your business already runs on (Zapier, Make, n8n, HubSpot, Salesforce, Slack, or any generic endpoint).

Task-driven documentation

Pages here are not ordered for casual reading. Each page is a task: creating a service, wiring a webhook, verifying a domain, troubleshooting a missing slot. Use the search box or the sidebar to go directly to the task you have.

What is documented here

Capability areaWhat you can doKey page
Booking surfacePublic booking pages per tenant, token-based cancel/reschedule, embeddable widgetBooking operations
AvailabilityComputed from services, staff, resources, overridesAvailability
RemindersSMS, WhatsApp, email waves with retry and rate protectionReminders
AutomationTriggered messages relative to booking startWorkflows
CalendarGoogle Calendar sync and read-only external feedsCalendar sync
PaymentsHosted checkout with Stripe, PayPal, 2Checkout, Authorize.NetPayments
WebhooksOutbound event delivery plus inbound Stripe and alert sinksWebhooks
DomainsCustom tenant domains with DNS verificationDomains
Self-hostingFull private deployment with edge, observability, and recoverySelf-hosting

Verified against the product

This documentation describes the QUE that actually exists. Field names, state values, header names, and endpoint behaviors below were copied from the implementation, not from a roadmap. If something here does not match your deployment, that mismatch is a defect worth reporting.

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.