Ask about alternative dining times without suggesting availability

The decision this workflow supports

A flexible caller may accept a different time, but listing alternatives can sound like offering actual available tables. Record flexibility as the caller’s preference rather than presenting a menu of supposedly open slots.

Put the review process in place

Ask the caller whether they have an acceptable time range. Keep a first choice and a fallback range in the same request. The host team checks availability and decides what to offer; the assistant should not rank times using assumptions about how busy service will be.

Worked example for your team

A fictional guest prefers seven o’clock but could consider a time between six and eight. The assistant records the first choice and fallback range without offering a specific available slot. Staff can use that flexibility when they review the request. Repeat the test with a guest who can only arrive at seven. The summary should not label them flexible merely because the assistant asked about alternatives. A comparison of the two handoffs shows whether the process records the guest’s answer accurately rather than applying a default assumption.

Sample wording to approve

“If your first choice is unavailable, is there a time range you would consider? I will include that preference for staff; I cannot see or hold available tables.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need first-choice time, acceptable range, date, party size, and staff response owner. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

An alternative remains a preference. The assistant does not describe quieter times as available. The staff summary retains the caller’s first choice. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides