Reservation lifecycle

On Service → Reservations you work tabs such as Upcoming, Seated, Finished, Waitlist, or Conflicts—pick the tab that matches the party state you’re fixing.

On this page

On Service → Reservations you work tabs such as Upcoming, Seated, Finished, Waitlist, or Conflicts—pick the tab that matches the party state you’re fixing.

Overview

Parties progress across tabs from staging arrivals through seated service to finished (or cancelled/no-show). Accurate status protects your floor map, wait times, and revenue forecasts.

When to use this

Training hosts or diagnosing table-turn issues.

Step-by-step

  1. Open Service → Reservations in the sidebar (defaults to Upcoming).
  2. Move parties across Upcoming → Seated → Finished (or mark No-show / Cancelled) so downstream reporting stays truthful.
  3. Open a booking’s detail page for party notes, tags, history, and conflicts.

Tips & best practices

  • Accurate party sizes keep capacity models trustworthy.

Common issues

Double booking or conflict

Compare party size to table capacity, review shift caps, and search for duplicate profiles—manual double-entry causes most conflicts.

Party stuck “upcoming” after seating

Advance status during service so waitlists and turns stay accurate—stale states break pacing models.

Walk-in overload

Tie overflow to waitlist instead of informal sticky notes so quoted times stay centralized.

Related links

px