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 with | Then read |
|---|---|---|
| A business operator | Quickstart | Booking operations → Reminders |
| Staff on a team | Roles | Booking operations |
| A developer integrating QUE | API | Authentication → Webhooks |
| An implementer or self-hosting admin | Self-hosting architecture | Environment → Observability |
| A security evaluator | Tenant isolation | Security 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 area | What you can do | Key page |
|---|---|---|
| Booking surface | Public booking pages per tenant, token-based cancel/reschedule, embeddable widget | Booking operations |
| Availability | Computed from services, staff, resources, overrides | Availability |
| Reminders | SMS, WhatsApp, email waves with retry and rate protection | Reminders |
| Automation | Triggered messages relative to booking start | Workflows |
| Calendar | Google Calendar sync and read-only external feeds | Calendar sync |
| Payments | Hosted checkout with Stripe, PayPal, 2Checkout, Authorize.Net | Payments |
| Webhooks | Outbound event delivery plus inbound Stripe and alert sinks | Webhooks |
| Domains | Custom tenant domains with DNS verification | Domains |
| Self-hosting | Full private deployment with edge, observability, and recovery | Self-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.