Reservations & Waitlist

Server-backed book for owner entries, Joe phone reservations, Google Reserve-ready requests, and the live walk-in waitlist.

Launch timing

Day 1 operational

Take reservations now. Optimize pacing as real guests arrive.

Reservations can be turned on at cutover. AIR should still show what needs tuning after launch so the book gets smarter instead of becoming another disconnected calendar.

Start on day 1

Use the book for staff-entered reservations and phone requests.
Run the walk-in waitlist from the floor map during service.
Let servers add reservations or waitlist entries from the PWA.

Becomes useful when

Week one tunes party-size rules, pacing, and waitlist handoffs.
Day-30 reporting shows covers by daypart, no-shows, and wait times.
Google/website booking paths can be promoted once the flow is tested.

What AIR tracks

Reservations created by staff, website, or Joe
Waitlist joins, quoted waits, and seated guests
Floor-map assignments and party-size patterns
No-shows, cancellations, and daypart demand

Total: 0Available: 0Seated: 0Ordering: 0Check dropped: 0

Chan Nara Floor Plan

Loaded from the active floor plan used by the PWA.

Loading floor plan...

🎯

Maestro

Ask me anything about your restaurant.

💼

CFO Assistant

I’m here to help you use your menu as a revenue-generating tool. Before we look at growth opportunities, let’s make sure your data is clean and accurate — that’s the foundation everything else is built on. What would you like to start with, or should I flag what I’m seeing?