What a private dining page needs to turn interest into an inquiry
Most private dining pages describe the room. The good ones answer the planner's five questions before she has to ask them.
Brad Nichols · 5 minute read
Private dining is usually the highest-value inquiry a restaurant website can produce. One booked holiday party can be worth more than a month of regular reservations from the same site.
It is also where most restaurant websites do the least work. The typical private dining page is one paragraph, two photos, and a generic contact form that goes to an inbox nobody owns.
The person on the other side is a planner with a date, a headcount, and a budget, comparing three venues on her lunch break. The page that answers her questions first usually gets the inquiry.
The five questions every planner is asking
Can the room hold my group? List each room with its real capacity ranges for seated and standing events, not one vague number for the whole restaurant.
What will we eat and roughly what will it cost? Planners do not need the full menu, but they need event menus or sample packages to know they are in the right building. If pricing stays offline, say what is included and how pricing works.
What does the room feel like, what do I do next, and how fast will you answer? Real photography of the actual room, one obvious inquiry path, and a stated response time cover the rest.
Design the inquiry form like a conversation, not an application
Ask for what you need to respond usefully: name, email, date, headcount, and the occasion. Every additional required field costs real inquiries.
Route the submission somewhere a specific person checks every day, and send the planner a confirmation that tells her what happens next. An inquiry that sits for two days usually became someone else's booking on day one.
The follow-up materials matter as much as the page
When the response goes out, it should carry a clean event packet: rooms, capacities, menus, terms, and photos in one place. If the packet is a decade-old PDF with an old menu, the polished page just wrote a check the follow-up cannot cash.
This is why we treat private dining as a system rather than a page. The page earns the inquiry, the routing protects it, and the packet and response close it.
A quick self-audit
Open your private dining page on a phone. Can a stranger name your rooms, their capacities, and the next step within thirty seconds? Does the form ask fewer than seven questions? Does anyone own the inbox it feeds?
If any answer is no, that is the gap. It is usually a focused project, not a rebuild.
Related service: Private Dining · Keep reading: Why menu information breaks across print, web, QR, and the team · What a restaurant website has to do before the guest ever arrives