HomeBookings & Reservations
Documentation · CoreTake the floor plan online.
Manages table bookings, waitlists and the live floor plan from one screen.

Bookings & Reservations setup guide
Estimated setup time: 15–25 min
Before you start
- Your venue's table layout and seating capacity
- Standard turn-time per table type (a working estimate is fine to start)
- A logo and short venue description if you're enabling the public booking page
Setup steps
- 1
Build your floor plan
Under Bookings → Floor Plan, drag in tables matching your real layout and set each one's seat count.
- 2
Set service periods and turn times
Define lunch/dinner windows and an expected turn-time per table size — this is what NUA's forecasting uses later.
- 3
Enable the public booking page
Turn on Bookings → Public Page to get a shareable link and embeddable widget for your website.
- 4
Configure the waitlist
Set max waitlist size and the SMS/notification template guests receive when their table's ready.
- 5
Set booking policies
Add deposit requirements, cancellation windows and no-show rules if you use them.
- 6
Test a booking end-to-end
Make a test reservation from the public page, seat it from the floor plan, and confirm the table's status updates correctly.
Tips
- Start turn-times conservative; NUA's forecasting tightens them automatically once it has a few weeks of real data.
- Link loyalty before going live so returning guests are recognised at the point of booking, not just at the till.
- Large parties and VIPs can be tagged directly on a booking so front-of-house sees the context before the guest arrives.
Troubleshooting
- The public booking page isn't showing live availability.Confirm service periods and table capacities are set under Bookings → Floor Plan — availability is calculated from those.
- Waitlist SMS notifications aren't sending.Check your venue's messaging credit balance and phone number format under Settings → Notifications.
Related modules
Still stuck on bookings & reservations setup?
Email us directly, a real person on the team replies.