Restaurant Reservation Form Template
Party size, seating time, dietary notes, and the occasion flag your floor team loves — reservation requests your host stand confirms in minutes.
Request a table. Tell us when and how many, and the host stand will confirm by text or call — usually within the hour during service.
A restaurant that takes reservation requests by form instead of phone rescues its two scarcest resources at once: the host's attention during service, and the guest's patience at 3pm when nobody answers because service hasn't started. The form works the hours the phone can't, and it arrives at the host stand as structured cover counts instead of a voicemail to decode. The trade is one honest asterisk — the table is confirmed by reply, not by submission — and this template says so at every step.
Why these fields. Party size is a dropdown with a deliberate ceiling: eight-plus routes to "we'll call to arrange," because large parties involve minimums, set menus, and table merges that no form should improvise. The mobile number is required and email is not — restaurants run on same-day channels, and the running-late text or the "we can seat you twenty minutes earlier" call is worth more than any inbox. The occasion question is the floor team's favorite field: a birthday flag costs the guest one tap and turns into a candle in a dessert, which is the cheapest loyalty program in hospitality. The dietary field, phrased "at the table" rather than per-person, collects the whole party's needs in one line and gives the kitchen its heads-up when the prep list is written, not when the order is fired. Seating preference sets expectations honestly — the patio option's own label carries the weather caveat.
What we left out. Credit-card holds and deposit collection — card-on-file no-show policies need a payments relationship a form should not fake; state the policy in your confirmation call if you run one. Also exact-table pickers and floor maps: guests choose vibes, hosts choose tables.
Who uses this. Independent restaurants without a reservations platform, wine bars and chef's-counter rooms where seats are few and calls are constant, cafés taking weekend brunch requests, and pop-ups whose "phone line" is one owner's cell. Supper clubs with twelve seats a night arguably need it most.
Make it yours. Put the form behind a "Reserve" button with the popup embed, or inline on your site — it inherits your colors and type, so it reads as the restaurant, not a third party. Turn on notifications so requests ping the manager's inbox between services, and use duplicate prevention to stop the double-tap request that books two tables for one couple. If a holiday service sells out, a close rule stops requests at your cover cap and shows a warm message with the next open date.
The confirmation text is hospitality. It arrives fast, names the time, and sounds like a person. That is the first course, served before anyone sits down.
Frequently asked questions
Is the table held the moment a guest submits?
No — the host stand checks the book and confirms by text or call. The ending tells guests exactly that, so nobody arrives holding an unconfirmed time.
Why route large parties to a phone call?
Eight-plus covers usually mean minimums, menus, and merged tables — decisions that need a conversation. The dropdown says so up front, which sets expectations kindly.
Can we stop requests once a holiday service is full?
Yes — set a close rule to cap responses or close at a set time, with a custom message like "New Year is fully committed; December 28–30 still has tables."
How does this look on our website?
Use the popup embed behind a "Reserve" button, or the inline embed on your contact page. Set your accent color and font so the form matches the room.