Reservations & order management · Restaurants & foodservice
Fill every cover without dropping a booking.
Resy and OpenTable pings stack up next to voicemail, DMs, and DoorDash tickets. A 20-top deposit goes uncollected and the kitchen learns the allergy at the pass.
The reality
Covers are a coordination problem.
A large party books across two channels, the deposit link gets forgotten, and the floor plan still shows the table as a two-top at 7pm. Off-premise orders land in three tablets at once, allergens never reach the line, and the host stand reconciles all of it by memory during a rush.
The operator owns the booking from first request to the kitchen brief. It confirms the cover in the POS, takes the deposit, rebuilds the floor plan for the party size, and pushes the allergen and timing notes to the expo screen before service starts.
How the operator runs reservations & order management
Booking RES-2208 · Confirmation
confirming- Party of 18 — Saturday 7:30pm
- Deposit link sent — $300
- Card on file — capturing
01Confirm and take deposit
Reads the request across Resy, DMs, and phone, confirms party size and time, and collects the large-party deposit.
Floor plan · Saturday dinner
sequencing- Tables 14–16 combined for top
- Adjacent two-tops shifted to bar
- Turn times recalculated — 7:30 seating
02Rebuild the floor plan
Updates the seating chart in the POS, combines tables for the party, and reflows the rest of the book around it.
Kitchen brief · BOH
briefing- Two shellfish allergies flagged to line
- Set menu, four courses, fired at 8
- DoorDash + Toast tickets merged to queue
03Brief the kitchen
Pushes allergens, course count, and timing to the expo screen and coordinates the off-premise tickets into one queue.
The outcome
−60% of reservations-admin work off the team
Tables and orders managed without gaps
- Deposits collected before the party arrives, not chased after a no-show
- Allergens and timing reach the line before the table is seated
- The floor plan matches the book, so the host stand stops improvising
Common questions
Reservations & order management
- What does the Reservations & order management operator do?
- The operator owns the booking from first request to the kitchen brief. It confirms the cover in the POS, takes the deposit, rebuilds the floor plan for the party size, and pushes the allergen and timing notes to the expo screen before service starts.
- What impact does the Reservations & order management operator have?
- −60% of reservations-admin work off the team. Tables and orders managed without gaps
- How does the Reservations & order management operator work?
- Reads the request across Resy, DMs, and phone, confirms party size and time, and collects the large-party deposit. Updates the seating chart in the POS, combines tables for the party, and reflows the rest of the book around it. Pushes allergens, course count, and timing to the expo screen and coordinates the off-premise tickets into one queue.
More operators in Restaurants & foodservice
See the full catalogue →