Restaurant Wait-Time Updates: Keep the Clock and Party Size Clear

A restaurant guest hears “twenty minutes” and starts watching the clock. If the party size changes or the estimate is revised, that phrase can become confusing. Does it mean twenty minutes from arrival, or another twenty minutes from now? A useful waitlist update makes the reference time clear and gives the guest a definite next contact without promising an unconfirmed table.

Confirm the request before checking the wait

Read back the number of people who need seats, the outlet and any seating preference. If three guests become five, update the same request through the approved process. Do not leave an old three-person entry active beside a new five-person entry. Ask the responsible host or supervisor to check suitable availability for the revised party.

Oracle's waitlist documentation distinguishes party size, estimated wait and table preferences. Its estimate depends on factors including availability and preferences, and a requested table is not guaranteed. Your restaurant may use another system, so follow its approved method rather than copying software controls from a different property.

Separate an estimate from an update commitment

Record when an estimate was given and what it meant. “Approximately 15–20 minutes from 19:00” points to 19:15–19:20. “Another 20–25 minutes from 19:10” points to 19:30–19:35. Neither is proof that a table will be ready then. Use the range or wording your outlet authorizes, based on a current check rather than a guessed number.

You can also agree a next update time. That is a commitment to contact the guest, even if there is no change. It is different from a guaranteed seating time. Confirm the approved contact method and keep the waitlist record current. The O*NET host profile describes coordinating with service staff and assigning suitable tables; the communication exercise below is original training material.

Worked example: three guests become five

Fictional training scenario: Request W218 is entered at 19:00 for three guests. The current estimate communicated is 15–20 minutes. At 19:08, the guest says two more people will join. The host confirms a total of five and asks the supervisor to review the request.

1. At 19:10, the supervisor's current check supports an estimated additional wait of 20–25 minutes for five. Update W218 and record the time, revised party size and estimate; preserve the earlier entry in its history.
2. Explain: “For five guests, our current estimate is another 20–25 minutes from now. I will update you again at 19:20.” Check that the guest understands and wishes to remain on the list.
3. At 19:20, no suitable table is ready. Make the promised contact, explain the current position and agree the next update under the outlet's process. Do not repeat the original arrival-time estimate as though nothing changed.
4. At 19:28, the supervisor confirms a suitable table is ready and allocated. Contact the party through the agreed channel. Record the actual seating at 19:31 and close or update W218 as the system requires.

Check your next waitlist update

• Correct request, current party size and outlet confirmed.
• Seating preferences recorded without an unsupported guarantee.
• Estimate based on a current authorized availability check.
• Reference time clear: arrival-time estimate or additional wait.
• Next contact time and method agreed and recorded.
• Actual seating recorded separately from the earlier estimate.

Practise with a timeline

Draw the example's times on paper and ask a partner to explain each change as the host. Then ask which statement promises a callback and which describes an estimate. Build related communication skills through HCA food and beverage training, and compare hosting responsibilities in current hotel vacancies.