Restaurant Group Enquiries: Capture the Event Before Promising a Table

Restaurant group enquiries often require more than finding an empty table. A caller may need a private space, a set menu, a deposit arrangement or a conversation about a celebration. An answering assistant should capture the event clearly and direct it to someone who can confirm the details.

Start by separating an enquiry from a reservation. If the assistant cannot verify the restaurant's table or event inventory, it should not say that space is held. A complete request can still be valuable when staff are busy during service.

Ask the questions that affect the event

Collect the preferred date and time, approximate party size, type of occasion and the caller's contact preference. Ask whether a private space is essential or simply preferred. These details help staff decide whether the request belongs with the normal reservation team or an events manager.

Avoid turning the call into a lengthy sales questionnaire. If the party size is still approximate, preserve the range rather than forcing the caller to invent a final number. If several dates would work, record them in order of preference.

Do not promise seating arrangements, exclusivity or a specific menu without approved current information. A photograph of a room or an old event package does not establish availability for the requested evening.

Make policy questions visible

Guests may ask about deposits, minimum spend, cancellation terms or bringing decorations. The restaurant should approve which general policies the assistant can explain and which cases require staff review.

OpenTable's event-space guidance recommends a clear owner for private-dining enquiries. The practical point is ownership: someone must evaluate the request and communicate the actual offer.

An assistant should not negotiate a discount or waive a deposit as a way to close the conversation. Record the question and identify who can answer it. Dietary and allergy questions should follow the restaurant's separate approved process rather than being resolved through guesswork.

A hypothetical celebration enquiry

A caller wants dinner for approximately eighteen people on a Friday and hopes for a quiet area. They ask whether a private room is available and whether everyone must choose the same menu. The assistant has the restaurant's public information but no event calendar access.

A useful handover records the date, party-size range, preference for a quiet/private area and the menu question. It should state that availability and terms remain unconfirmed. The guest should hear that the events team will review the request under the restaurant's actual follow-up process.

A poor handover would say “eighteen booked in private room.” That turns two preferences into commitments and leaves the manager to undo an expectation the restaurant never approved.

Keep existing reservations on a separate path

If the caller already has a booking and wants to add guests, treat that as a change request. Do not create a second independent enquiry that staff could mistake for another party.

Collect the relevant reference through the approved process and preserve the requested change. If the assistant cannot modify the reservation, explain that the existing arrangement has not been updated by the call alone.

The AI receptionist guide describes the general answering role. Restaurant group handling requires a specific boundary around tables, event space and authorized commercial terms.

Make the handoff workable during service

Assign an events owner and a backup rather than sending every request to whichever staff member happens to answer. A routing review should include enquiries during a busy service and requests for dates when the events lead is absent.

Track whether staff can prepare a meaningful response from the note and whether the guest understood that no table was held. Your next step is to have the restaurant manager review one fictional group enquiry from first call to written offer, then approve the exact closing language before launch.