Help a guest who cannot find a reservation reference

The decision this workflow supports

A guest may need help about a reservation but have no reference number available. Blocking the conversation entirely is unhelpful, while pretending to locate a booking from a name alone is misleading.

Put the review process in place

Collect the minimum caller-reported details staff need to investigate, such as the booked name, intended date and approximate time. Mark the booking as unverified. Do not reveal whether another person has a reservation or read back information from unrelated requests.

Worked example for your team

A fictional guest remembers the booked name and date but cannot find a confirmation reference. The assistant records those details as caller-provided clues and takes the question for staff. It does not claim to have found a reservation. Test another caller who asks whether a named friend has booked. The assistant should not disclose anyone else’s arrangements. The distinction matters: collecting information from a person seeking help is different from revealing restaurant-held information. Staff verification should happen through the restaurant’s established process after the handoff.

Sample wording to approve

“You can still leave a question for the host team. What name and visit date should they use to investigate? I cannot verify the reservation here, but staff can follow up.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need caller-supplied booking name, intended date, approximate time, question, and callback contact. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

The caller can proceed without a reference. The note is marked unverified. No other guest’s reservation information is disclosed. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides