What a Reservation Request Should Actually Capture
A reservation form that sends an email saying someone wants a table is better than nothing, but not by much. The useful version gives staff enough information to confirm the request without calling the customer back.
July 10, 2026
Start from the reply
The best way to design a request form is to work backward from the answer staff want to send. If confirming a table means knowing the date, the time, the party size and whether anyone needs accessible seating, the form should ask for exactly those things.
Anything staff would have to call back about is a question the form forgot to ask.
Match the request to real hours
A request for a time the kitchen is closed wastes everyone's time. Requests should be limited to the hours the business can actually serve, and those hours should come from the same place the website displays them, so changing one changes both.
Keep it short
Every extra field costs some customers. Ask for what the reply needs, plus a way to reach the person. Leave out anything that would be nice to know but doesn't change the answer.
Put every request in one list
Requests should land somewhere staff can see them, mark them handled and look them up later, not only in one person's inbox. When phone reservations are entered into the same list, there is one record of who is coming instead of two that disagree.
Say what happens next
A customer who sends a request should see a clear message: this is a request, not a confirmation, and here is when to expect a reply. That one sentence prevents most of the confusion online requests cause.