A practical restaurant group booking enquiry form

A group booking enquiry form should help your team decide what happens next, not ask the organiser to complete your whole event plan. The useful first step is a qualified enquiry: enough detail to check fit and availability, followed by a clear human response.

That distinction matters. Current UK restaurant examples commonly separate ordinary online reservations from larger-party enquiries. For example, Brother Marcus routes parties of up to 22 through online booking and larger groups to an enquiry, while Zaza explicitly tells visitors that submitting its form does not confirm a reservation. Your thresholds will differ, but customers should never have to guess which route to use.

Start with the decision your team needs to make

Before changing the website, map the first operational decision. Usually it is one of four outcomes:

• offer the requested date and space;
• suggest another time, area or branch;
• ask one focused follow-up question; or
• decline quickly because the request falls outside capacity or policy.

Write down what staff need to choose among those outcomes. Anything else can wait until the organiser is ready to proceed. This prevents a long form from becoming a substitute for a sales conversation.

Also set expectations beside the submit button: “This is an enquiry, not a confirmed booking. We aim to reply within one working day.” Use a response time the team can genuinely meet, and provide a phone number for requests inside a defined urgent window.

Use this minimum viable field checklist

For most venues, the first form can be short:

• organiser’s name;
• email address, plus an optional phone number unless calling is essential;
• preferred venue or area, if there is more than one;
• preferred date and approximate arrival time;
• number of guests, or a sensible size band;
• occasion type, including “other” and “prefer not to say” where appropriate;
• seating, private-room or exclusive-hire preference;
• a free-text box for access, dietary or other practical requirements;
• an optional alternative date or time.

Avoid requiring a postal address, every attendee’s name, a full menu choice or payment details simply to ask about availability. The ICO’s data-minimisation guidance says personal data should be adequate, relevant and limited to what is necessary for the stated purpose. Explain why you collect the details, link to your privacy information and review how long unsuccessful enquiries are retained. This is general guidance, not a compliance assessment.

Make dietary and accessible alternatives part of the route

Do not turn a single organiser into the final authority on every guest’s needs. Ask whether the party has dietary, allergy or access requirements that the venue should discuss, then provide a safe follow-up route by phone or email. A generic notes box can also let someone describe a requirement in their own words.

The Food Standards Agency says businesses serving non-prepacked food must provide information about regulated allergens; its current allergen guidance for food businesses recommends written information supported by a conversation. Treat a form response as an alert for trained staff, not as the end of that conversation or a promise that a request can be met.

Keep an accessible alternative visible near the form: a telephone number, monitored email address and the hours in which somebody can help. Make error messages specific, retain entered values after an error, allow keyboard completion, and do not rely on colour alone to identify required fields. Test the actual journey on a phone rather than only reviewing the form in a desktop editor.

Route the enquiry instead of creating another inbox

A form only improves conversion if somebody owns the response. A workable small-venue flow is:

1. Create one enquiry record with a timestamp and reference.
2. Send the organiser an acknowledgement that repeats the request and explains the next step.
3. Route it to the venue or manager responsible for that date.
4. Mark it new, checking, offer sent, confirmed, declined or closed.
5. Set an internal response deadline and alert the duty manager before it expires.
6. Copy confirmed details into the reservation or event system, avoiding duplicate retyping where an existing integration is available.

Use shared booking software, a form tool or a lightweight automation before commissioning a custom build. A spreadsheet can be enough at low volume if access is controlled and every row has an owner. Build something bespoke only when venue rules, pricing or system connections make the existing options genuinely unworkable. BrandFlame’s restaurant and hospitality digital transformation support can help map that decision and integration flow.

Test the process with a worked enquiry

Use a fictional scenario before launch: 28 guests want a Thursday dinner at 7.30pm, would consider 8pm, need step-free access and want to discuss allergy requirements. Check whether the form captures those facts without collecting guest names or medical histories. Then verify that the right manager receives it, the acknowledgement does not imply confirmation, and the organiser gets a useful response through their chosen channel.

Repeat the test for a date in the past, an unavailable party size, missing required information and a keyboard-only submission. Review a sample of real enquiries after launch: which questions do staff repeatedly ask, which fields go unused, and where do enquiries stall? Add or remove fields from evidence, not instinct. The best form is the shortest one that lets the team respond accurately and move a suitable enquiry towards a confirmed booking.