Phone bookings are fine until the phone rings during the dinner rush. Then messages pile up in three inboxes and a table gets missed. I would send guests to one link, where every request lands in the same shape.
When and how many
The date, the preferred time, a second time that would work and the party size. These are the facts you check against your table plan.
Where and why
Seating, the occasion and high chairs. A birthday gets the corner table, and the right chairs are waiting.
Needs and notes
Step-free access, dietary notes and special requests. You want to know these before the guests arrive, not at the door.
Who fills it and who reads it
Guests fill it in. The host or manager reads the CSV and replies. A guest's AI might ask "What date and time would you like?" Then "How many people are coming?" Then "Does anyone have allergies?" It shows every answer and sends only after a yes. Read more about agent-fillable forms.
A tip
Be clear on your site that this is a request and not a confirmed table. You reply with a yes or an alternative. The form sends no email to the guest. Put the link on your website and social profile, and read the day's requests while you run the morning routine in your restaurant opening checklist. After the meal, a restaurant feedback form asks how it went. See forms for restaurants and food businesses.
Questions
Does the form confirm a table?
No. It records a request. It has no calendar and cannot tell whether a table is free, so you check your book and reply to the guest yourself.
How do I avoid double booking?
Sort the CSV by reservation_date and arrival_time and compare it with your table plan. The second choice time gives you an alternative to offer.
Can guests mention allergies?
Yes. A notes box takes dietary needs and special requests. Read it before service, and ask the guest to confirm anything serious by phone.