Queues, bookings, deposits & no-shows
Handle walk-ins and multichannel reservations through check-in and seating.
On this page · Jump to a section
Before you begin
Booking enabled with hours, branch capacity and deposit policy configured.
Where to go
Board-game tables → Reservations / POS → Queue
Visible menus may vary with language, permissions, app version and shop configuration.Follow these steps
- For walk-ins, add party size and necessary contact details, then call when a suitable table is ready. Queue entry does not start play time.
- For bookings, check date, time, duration, party size and branch table. A requested reservation is not a confirmed table.
- When a deposit is required, use the configured payment route and have an authorized person verify the evidence. Check deposit readiness before check-in/seating.
- Arrival check-in is allowed from two hours before to six hours after the booking once confirmed and deposit-ready. Choose Seat, enter players and rates; this creates the session in the same action. Do not separately open the table again.
- Recheck availability before rescheduling. Handle no-shows and deposits separately under shop policy; cancellation does not prove an external refund occurred.
- Time/table edits require a CONFIRMED reservation before check-in and recheck availability. REQUESTED entries need staff review. Request expiry, unpaid-deposit expiry and no-show are distinct outcomes.
- The scheduled job marks still-CONFIRMED bookings NO_SHOW after six hours past the appointment. It does not automatically close checked-in WAITING/CALLED parties; staff own those queues and the scheduler must be enabled.
How to verify success
Bookings recorded through BMS share one workflow, with no conflicting table windows or duplicate deposits. Staff must enter phone/external bookings; they do not synchronize automatically.
Limits & things to check
Capacity can prevent strict FIFO seating. Explain the reason and do not promise unsupported wait times.
Ready to try it in your shop
Lessons are free to read. Actual operations require sign-in and the appropriate permission. Use test data for training.