Independent restaurants and small venues can take reservation requests on their own site. The form captures headcount and date so you are not rebuilding a Saturday night from Instagram DMs.
Notify the person who writes the book.
Party size drives whether you can say yes.
The date field has no hour; prompt for 7:30 p.m. vs 13:00.
Reply. Do not leave a Friday night hanging.
A reservation form is a request for space: a table, a meeting room, a hire slot. US independents and UK gastropubs both need covers and a time window. Unlike an appointment form, the scarce resource is a room and a party size, which is why this page uses the event pack (attendees + preferred date).
OpenTable and ResDiary confirm inventory. This HTML form does not decrement a floor plan. Treat submissions as requests until the book says yes.
A party of twelve on a Saturday is not a notes afterthought. Attendee count is the product.
Allergies belong in notes, then you still confirm in person. A web form is not a kitchen allergen system.
OpenTable, a phone, and walk-ins. HTML is your branded request path.
Hours, menu, and this form. You confirm by phone or email.
Use when you need real-time inventory and deposits.
Unsearchable. Point them at this page in the bio.
A valid policy. Then you do not need this form—say so on the site.
A Squarespace restaurant site can host the form under the menu. Close it on dates you are shut.
Deposits and card-on-file for no-shows belong in a proper booking product, not this HTML.
Not until you confirm. Say that on the page.
Same form, larger attendee number, more notes. Or a second form for events.
Appointment is a person’s time. Reservation is space and headcount.
Put service (lunch/dinner) in notes or add a select after copy.