Waitlist — collecting and handling requests
Waitlist collects requests from people for whom no place or time is currently available. It is not a confirmed booking. The business contacts the customer and changes the request status in the dashboard.
Verified 2026-07-15
Waitlist collects requests from people for whom no place or time is currently available. It is not a confirmed booking. The business contacts the customer and changes the request status in the dashboard.
What can be configured
In Settings → Waitlist, the business can configure:
- whether the public form is enabled;
- a message and its translations;
- a list of services; an empty list lets the customer enter a custom name;
- required phone and/or email;
- whether preferred dates can be provided;
- predefined times or a “from–to” range;
- from 1 to 10 preferred dates;
- a weekly schedule with multiple time ranges.
The public form rejects dates in the past, closed days, incomplete time ranges and hours outside the configured schedule. The same validation applies when staff add a request manually.
Dashboard operation
Within their permissions, staff can add requests, review details and preferences, update the note and status, contact the customer, and restore or close a request. The operation history shows who made each change and when.
A “notified” status or contact with the customer does not automatically create a booking unless a separate Booking flow saves the appointment. Customer communication must clearly distinguish a proposed time from a confirmation.
Common checks
| Symptom | Check first |
|---|---|
| Form rejects a date | today's date, active day and time ranges |
| Time field is missing | time_slots, range mode and enabled dates |
| Request is not visible | correct business, filters, status and operating date |
| Customer believes they have a booking | public copy, sent message and any Booking record |
The public link is /{slug}/waitlist. Before publication, open it in a private browser window and submit one test request.