The front door needs one floor truth, not another calling screen.
One Hub tracks waitlist, reservation holds, and seating before table ordering, subject to store and source conditions.
Sound familiar?
- A waiting party gets a reserved table
- Calling does not update table state
- Seated guests restart in another ordering tool
Before vs with VDine
| Before | With VDine |
|---|---|
| Separate waitlist and booking records | One Hub for queue, holds, and floor state |
| Hosts remember reserved tables | The engine respects existing holds |
| Restart after seating | Continue into table ordering after confirmation |
How it works
- Collect waitlist and connected bookings Confirm store and source conditions first.
- Call and seat from one floor state Avoid assigning a held table to walk-ins.
- Continue into ordering After seating, enter the QR/NFC flow.
State the conditions first
Waitlist currently applies to specific conditions such as postpay stores. Third-party bookings do not import without a completed connection. Validate the actual store and source before rollout.