Managing Booking Statuses
Each status tells the team what should happen next.
Overview
A booking intent moves through a defined lifecycle. Pending (pending restaurant) means the venue has not accepted or declined yet. Confirmed and Guest Confirmed reflect agreement at different stages before seating. Seated means the party is on the floor; Completed closes a successful visit; Not Shown records a no-show; Rejected and Cancelled are terminal states for declined or cancelled requests. Status badges appear in the Reservations table, mobile cards, Availability grid, and Floor View. The detail panel and timeline help audit changes over time.
Step-by-Step Instructions
Identify the current status
Read the badge on the reservation row or card, or open the detail panel for the canonical value.
Pending and decide
Use Approve or Reject to leave Pending; no other service action applies until that decision is made.
Pre-service confirmations
Use Mark Guest Confirmed when your process requires an explicit guest acknowledgment step after restaurant confirmation.
Service states
Mark Seated when guests arrive; choose lateness if you track it. Mark Not Shown if they never arrive. Mark Completed when the table is done.
Terminal states
Rejected and Cancelled stop normal service actions; treat them as closed records except for reporting and follow-up.
Tips & Best Practices
Update in real time
Availability grids and floor colors depend on accurate statuses.
Pair status changes with notes
Especially for Not Shown or late seating, context helps future decisions.
Filter by status on Reservations
Focus the list on Pending during pre-service and Seated during rush.
Use the guide modal
It lists every status with the same wording guests of the UI see.