Route large-party and private-event inquiries without making an accidental booking

Define the standard-booking boundary

The threshold for a group inquiry is a restaurant decision, not a universal number. It may depend on service period, location or event space. Write down the point at which the receptionist stops using the ordinary reservation workflow and creates an inquiry.

Do not split a large party into several standard bookings to bypass that boundary. The floor team needs to know that the guests intend to dine together. If an exception is possible, route it to the person who can approve it.

Collect enough detail for a useful response

A basic inquiry can include preferred date, time range, estimated party size, occasion if the caller chooses to share it, and a preferred contact method. Ask only for details the receiving team needs. Avoid collecting payment data, sensitive personal information or long guest lists in a general intake flow.

Distinguish firm requirements from preferences. If the caller needs a private room, record that request without promising a particular space. If the time is flexible, note the range so staff can consider workable options without starting the conversation from zero.

Keep commercial terms with an authorized person

Minimum spend, deposits, cancellation charges, special menus and room availability can create meaningful commitments. The receptionist should communicate only approved information within its assigned scope. It should not negotiate, waive a policy or accept a contract on the restaurant’s behalf.

If the restaurant has a formal event-sales process, direct the inquiry there. Make clear whether the guest is requesting information, holding a date or confirming an event. These are different states and should not be blurred by conversational language.

Related Loman sources: Loman’s SevenRooms reservation workflow

Give the inquiry an owner and status

Assign a named role or monitored queue to group requests. Confirm what the caller hears about response timing, and use only a time window the team can support. Do not give a guaranteed deadline simply because a template includes one.

Test a request that arrives after hours and one that falls just above the standard-booking limit. Verify that the recipient gets the important details and that the guest understands no reservation has been made yet. Review unresolved inquiries regularly so a successful intake does not become an unanswered lead.