Skip to content
Docs home

CORE CONCEPTS · UPDATED AUGUST 2026

Waitlist

Capture demand when slots are full: customers join a per-service waitlist and are notified when capacity opens.

What the waitlist is

The waitlist captures demand for services whose slots are full. A customer joins for a specific service (optionally with preferred staff and preferred time windows), and the tenant keeps a notify token that identifies them for notification when capacity opens. Waitlist records are scoped to the tenant, like every other operational object.

How it works

When the public booking surface finds no available slot for a service, it can offer the customer a place on the waitlist instead of a dead end. The customer provides name, email, optional phone, and preferred windows. The tenant's operators see the accumulated waitlist per service and can reach those customers — through the notification channels the tenant has configured — when new capacity becomes bookable.

Demand signal

The waitlist is also a planning signal: persistent waitlist depth on one service is evidence that the service needs more staff, more resources, or more hours — not just more marketing.

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.