One
Live service board
Bookings, tables, and attention items in one operating view.
Reservations in RMS
Know who's coming. Seat every table with confidence.
Give the host one place to read demand, place parties, handle walk-ins, and carry guest context into service.
Dinner service
Friday, 11 August
Live6:30–10:30 PM
42
covers
12
bookings
3
need attention
Next up
Search7:00
Aanya Mehta
Arriving4 guests
Anniversary · window preferred
7:15
Kabir Shah
Confirmed2 guests
Nut allergy · confirmed
7:30
Mira & team
Watch6 guests
High chair · main room
Main room
8 openT01
2 seats
T02
4 seats
T03
2 seats
T04
6 seats
T05
4 seats
T06
8 seats
T04 clears at 7:08 · best fit for Mehta, party of 4
3 views
List, calendar, and floor
Change the lens without losing the state of service.
7 states
Explicit guest lifecycle
From pending confirmation through seated, complete, or no-show.
Host-led
Every assignment
Recommendations inform the team; the team stays in control.
The host workspace
See the room, the book, and the next hour together.
Move between a detailed queue, a time-based calendar, and the table board without fragmenting the service picture. Search, filters, density, and attention states keep the important work visible.
01
Service list
Search by guest, filter by status or source, and isolate the bookings that still need a table.
Same service · another lens
02
Calendar
Read the day by time and density before a rush becomes a surprise.
Same service · another lens
03
Table board
Match party size, section, and availability against the physical room.
Same service · another lens
Guest context
A booking should carry more than a name and time.
Keep contact details, occasions, seating preferences, dietary and accessibility notes, reminder choice, source, and customer history close to the reservation.
Link a returning customer without losing the booking.
Read the reservation timeline and prior changes.
Keep sensitive operational context visible to the right team.
AM
ConfirmedAanya Mehta
4 guests · 7:00 PM
Occasion
Anniversary
Seating
Window preferred
Accessibility
Step-free route
Source
Direct booking
Dietary note
One guest has a nut allergy. Confirm with the kitchen on arrival.
TimelineGuest historyDining session
Explicit lifecycle
Every arrival has a next action.
The team can see exactly where a reservation sits and move it deliberately—from confirmation and table assignment to check-in, service, and close.
01
Confirm
Turn an enquiry into a committed booking.
02
Assign
Choose a table or review a suggested fit.
03
Check in
Mark the guest arrived and seat the party.
04
Serve
Carry table and dining-session context into POS.
05
Close
Complete, cancel, expire, or record a no-show.
Due reservations and linked visits put useful arrival context beside POS—without pretending the host stand and the bill are the same job.
Availability and planning
Make a better call, then keep the human in charge.
Check the requested slot, compare nearby availability, and review table-aware assignment recommendations. Pins, policies, and host judgment still decide what happens on the floor.
Nearby slots
Offer a workable alternative instead of a dead end.
Section-aware fit
Respect table capacity, room, and explicit pins.
Walk-ins
Keep the queue beside the book—not buried inside it.
Timed reservations and walk-in parties have different promises. Give staff a dedicated queue for estimated waits, return-by times, arrival, seating, cancellation, and no-shows while preserving one view of demand.
Walk-in queue
6 parties · 24 covers
1
R. Iyer · 3 guests
Arrived
12 min
2
S. Patel · 2 guests
Return by 8:05
18 min
3
N. Bose · 5 guests
Waiting nearby
26 min
Status updates stay attached to the party.
Control and accountability
The quiet systems behind a composed service.
Reservations stay useful when rules are explicit, signals are explainable, and operational changes leave a trail.
Rules
Shape service by branch.
Turn times, overbooking controls, auto-release rules, table sections, and service windows stay explicit.
Signals
See why something needs attention.
Deterministic risk context highlights arrival drift, no-show patterns, reminder priority, and service pressure.
Ledger
Keep deposit context with the booking.
Track amount, status, method, processor reference, due date, and notes in a processor-agnostic ledger.
Ready for the next service
Turn arrivals into a service your team can see coming.
See how reservations, walk-ins, tables, and POS context fit into the same restaurant operating layer.