Route a whole-restaurant buyout request

The decision this workflow supports

A request for exclusive use of the entire restaurant affects normal service and requires a management decision. The phone flow should identify that scope early rather than treating the organizer as a large-table caller.

Put the review process in place

Record the desired date, approximate event period and reason the organizer wants exclusive use. Direct the inquiry to the person authorized to assess buyouts. Do not quote a minimum spend, agree to close public service or assume a previous buyout establishes current terms.

Worked example for your team

A fictional company wants exclusive use for an evening gathering and asks whether the restaurant can close to other guests. The assistant records the proposed period and approximate attendance, then directs the inquiry to management. It should not infer that a quiet weekday makes a buyout possible. Ask the reviewer to identify who is authorized to assess the proposal and which questions remain unanswered. If the note resembles a normal large-table request, the scope has been lost. The manager needs the exclusive-use expectation before considering any commercial discussion.

Sample wording to approve

“I can pass a whole-restaurant event inquiry to management. Which date and time period are you considering? Management will confirm whether exclusive use can be discussed and on what terms.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need date, event period, guest estimate, exclusivity purpose, and management reviewer. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

The inquiry is marked whole-restaurant scope. No public-service closure is promised. A minimum-spend question stays with management. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides