Create a waitlist reservation
Add a guest to the waitlist when an automatic Harbor Soho service cannot offer an acceptable booking slot, while keeping the customer record, reservation status and occurrence context in Antylogic.
In this article
Use this guide when the optimised reservation modal reaches the time step and the operator chooses the waitlist path instead of accepting a split or unavailable slot.
In the implemented flow, Antylogic creates the customer inline first, then creates a reservation with status `waitlist` for the selected service occurrence. The backend keeps waitlist timing tied to the occurrence start and stores a 120-minute duration.
Before you start
- The operator is signed in to Harbor Demo Group and working in the Harbor Soho location context.
- A service occurrence is open from `reservations/:occurrenceId`; for the optimised modal path it must be automatic, open for acceptance and not treated as a past day by the app.
- The operator has `reservation:manage` to create the reservation and `customer:manage` to create the customer inline.
- The availability path is enabled through `reservation-automatic:use` plus one of `optimization:view`, `reservation-availability:view` or `reservation:manage`.
- The time step shows `Add to waitlist` because there is no acceptable slot, or the available slots are only split-eligible.
Instructions
- 1.
Open the service occurrence
From the reservations calendar or deep link, open the Harbor Soho service occurrence. The detail page loads the occurrence, existing reservations and table assignments for the selected location.
- 2.
Start a new reservation
Select `New reservation`. When the occurrence supports automatic booking, Antylogic opens the optimised reservation modal with the service already selected.
- 3.
Confirm party and table preferences
Set the party size and choose the table preference mode. If the mode is not indifferent, select at least one valid table before moving to the time step.
- 4.
Choose Add to waitlist
On the time step, use `Add to waitlist` when no acceptable slot is available. The modal clears any selected slot and moves to the contact step for the waitlist fallback.
- 5.
Enter customer contact details
Enter the customer name and phone. The optimised modal creates a new customer record inline before it creates the reservation.
- 6.
Create and confirm the waitlist reservation
Submit the modal. Antylogic creates the reservation with status `waitlist`, channel `phone`, the selected party size and occurrence, then refreshes the occurrence context after the backend marks optimisation data stale.
Validations and limits
- Customer name and customer phone are required before the inline customer can be created.
- The reservation requires an `occurrence_id` and a party size greater than zero.
- The customer and occurrence must both belong to the current Harbor Soho location.
- Waitlist reservations do not receive physical table assignments, although table preferences or restrictions can be kept on the reservation.
- The backend is the source of truth for waitlist timing: it uses the occurrence start time and a 120-minute duration.
- If the optimiser fails, the modal offers manual mode; it does not automatically create a waitlist reservation.
Expected result
The guest is stored as a customer and the occurrence has a new reservation in `waitlist` status. The occurrence optimisation cache is marked stale, waitlist analysis is cleared, and the operator can review the seeded waitlist state in Harbor Soho.