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?

Before vs with VDine

BeforeWith VDine
Separate waitlist and booking recordsOne Hub for queue, holds, and floor state
Hosts remember reserved tablesThe engine respects existing holds
Restart after seatingContinue into table ordering after confirmation

How it works

  1. Collect waitlist and connected bookings Confirm store and source conditions first.
  2. Call and seat from one floor state Avoid assigning a held table to walk-ins.
  3. 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.