Waitlist, Reservation, and Seating Hub

Stop guessing table availability across three lists

Common pain points

Separate records double-assign tables
Calling, seating, and floor state drift

Key capabilities

Waitlist queue
Reservation holds
Call and seating state

Collect waitlist and bookings Walk-ins and connected sources enter one Hub.
Respect floor and holds The waitlist engine avoids reserved tables.
Confirm seating after call Updated state continues into table ordering.

FAQs

Can every store enable waitlist immediately?

The flow has store-type and postpay conditions; third-party bookings require connection.

A good place to start when

The front door handles walk-ins, bookings, and floor state together
The store matches current waitlist conditions

Confirm before rollout

Whether the store uses an applicable postpay flow
Which third-party booking sources are connected
Table hold, no-show, cancellation, and requeue rules

What the system does not do

Unconnected third-party bookings do not appear automatically
Showing a table number is not guest-phone floor navigation

Observe first after launch

Track double assignments, missed calls, wrong seating, and wait-estimate error before adjusting table pools and host rules.