Restaurant reservation form
A restaurant reservation is a small contract: a guest commits to a time and party size, and you commit to a table. This form collects name, phone and email, party size as a number so a typo cannot seat the wrong number of guests, a date and time, and an optional notes field for special occasions or allergies. It flows straight to a webhook or Slack channel so the host sees it immediately.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
Number field prevents party size confusion
Party size is a number field, so "four" or a blank never reaches your reservation list, and the host never has to guess whether the party is 4 or 14.
Send reservations straight to your system
Point the form at a webhook and each reservation is delivered the moment it is placed; a Slack channel works the same way so the host can confirm it right away.
No card required.
Restaurant Reservation
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add name, email and phone fields for the guest — phone especially, so the restaurant can reach them if they are running late.
- Add a number field for party size, so a text answer never reaches your list.
- Add a date field for the preferred date and a time field for the preferred seating time.
- Add an optional textarea for special requests — allergies, a birthday, a high chair.
- Send each reservation to a webhook or Slack channel so the host can confirm it immediately.
Fields in this form
7 fields, using 7 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Guest name | Short text | Yes |
| Yes | ||
| Phone | Phone | Yes |
| Party size | Number | Yes |
| Preferred date | Date | Yes |
| Preferred time | Time | Yes |
| Special requests or dietary restrictions (optional) | Long text | Optional |
What goes wrong with this form
Specific to a restaurant reservation form, not general advice about forms.
Party size as a text field
Use a number field; a text field lets through "four people" or a blank, meaning the host has to call back and ask.
Forgetting to ask for phone
Email is not enough for day-of coordination — phone is how a host recognises a guest running late or texting about a change.
Treating the notes field as a substitute for asking at the table
The notes field is a helpful heads-up, not a guarantee — train staff to ask about allergies directly, since a guest may forget to mention one in the form.
Questions about this form
What should a restaurant reservation form collect?
Guest name, email, phone, party size as a number, preferred date and time, and an optional notes field for allergies or occasions. Do not ask for card details — take payment at the table or by phone if you need a guarantee.
Why use a number field for party size?
Because it is validated in the browser — "four people" or a blank is rejected before it reaches your list, so the host never has to call back and ask.
Can the form hold a credit card to guarantee the reservation?
No. This form collects the reservation details only. If you need a guarantee, call the guest to confirm ahead of time or set a cancellation policy — the form's job is to capture the request, not to charge a card.