Describe your restaurant and the requests you accept. Makeform creates a restaurant contact form for reservations, questions, private events, and catering, with the details your team needs to reply.
Send inquiries to email, Sheets, or Zapier.
Sample prompts for the builder
Choose a prompt, tailor it, or send it into the Makeform builder. Each example is editable.
Audience
Guests with booking, menu, accessibility, or service questions
Format
Conditional contact form with inquiry routing
Prompt size
355 chars
Example form structure
Conditional contact form with inquiry routing
What can we help with?
Name, email, and phone
Preferred reply method
Visit date, if relevant
Tell us more
Suggested routing tags
Table requests
Private events
General inquiries
Ask for an inquiry type first, then show only the relevant questions.
Step 1
Ask
guest chooses the reason for contacting you
Step 2
Qualify
relevant booking, event, or catering fields appear
Step 3
Route
the request reaches the right restaurant team
Step 4
Reply
staff confirms details and next steps
Why one contact form works
Collect dates, party size, service type, and reply details before the message reaches staff.
Branch into reservation, event, catering, lost-item, or general fields based on inquiry type.
Send table requests to hosts, event leads to coordinators, and general messages to management.
Explain that staff must confirm a reservation, event, or catering request after submission.
Built around restaurant work
Give guests one obvious contact link while collecting a different set of details for each request type.
Menu questions, accessibility needs, lost items, press messages, and other notes with contact details and visit context.
Requested date and time, party size, seating preference, alternate availability, and contact details for a staff reply.
Event purpose, guest estimate, room preference, schedule, meal format, beverage needs, and budget range for qualification.
Service date, venue, headcount, delivery or pickup, dietary details, menu interests, and staffing needs in one submission.
Contact workflow
Start with your real inquiry paths, then make every field, notification, and confirmation support how your restaurant responds.
Share your locations, reservation process, event options, catering coverage, and common follow-up questions.
Keep contact fields universal, then reveal the relevant table, event, or catering questions.
Notify the right team and send guests a receipt with their request and expected next step.
Embed the form, test every path on mobile, and refine fields using recurring follow-up questions.
Contact options compared
Phone, email, and online forms each have a role. A form is most useful when a request needs several details and should reach a specific person.
Field guide
Use these six field groups as building blocks, requiring only what each request needs.
Request type
A specific dropdown controls the questions and routing that follow.
Guest details
Collect a reliable reply channel without asking for unnecessary personal details.
Reservation context
Give hosts enough information to assess availability and offer an alternative.
Event qualification
Structured event details help the coordinator assess fit before follow-up.
Food and access needs
Let guests describe needs for staff review without implying automatic acceptance.
Consent and next steps
Distinguish receipt from acceptance and explain how staff will respond.
Related tools
Use focused forms when a request needs more depth than the contact page.
Collect table timing, party size, seating, and guest details.
Open toolCollect catering schedule, headcount, menu, delivery, and venue details.
Open toolBuild a structured restaurant order flow when guests need to choose items and pickup details.
Open toolGive post-visit feedback its own questions, ratings, visit context, and follow-up choice.
Open toolStart with a broad contact form for other business inquiries and general messages.
Open toolFAQ
Practical answers for restaurant owners and managers building a clearer contact path.
Start with inquiry type, location, guest name, reply details, and a message. Then show reservation, event, or catering fields conditionally.
Yes. Use an inquiry-type dropdown to show a short branch for tables, events, catering, feedback, or general messages while sharing the same contact fields.
No. Say that submission records the requested date and time but staff must confirm availability. Repeat this near the submit action and in the receipt.
Route by inquiry type and location. Include date, guest count, service type, and budget range in event notifications, while keeping table and general messages in separate queues.
Let guests describe needs in their own words and route them for staff review. Confirm receipt without implying that every request is automatically available.
Yes. Embed it on the contact page or link from location, event, and reservation pages. Test every path on a phone before publishing.
Yes. Makeform offers unlimited free forms and responses. The paid tier removes the Makeform badge.
Require only relevant details, use clear categories, validate contact fields, and ask for alternate dates. Add fields when they prevent a recurring follow-up question.
Give every guest request a clear destination.
