A contact form for restaurants, next to the booking widget

What a restaurant form should actually ask

The form earns its place by sorting the non-booking traffic before you read it:

Every field you add costs completions, so this list is deliberately short; everything else is a question for the reply. The snippet below is the whole form; build a styled variant in the free form generator or start from a template.

<form action="https://formgong.com/submit" method="POST">
  <input type="hidden" name="access_key" value="fk_your_access_key">
  <label>Name <input type="text" name="name" required></label>
  <label>Email <input type="email" name="email" required></label>
  <label>Phone <input type="tel" name="phone"></label>
  <label>What is it about?
    <select name="topic">
      <option>Group event</option><option>Catering</option><option>Private hire</option>
      <option>Press</option><option>Supplier</option><option>Other</option>
    </select>
  </label>
  <label>Date <input type="text" name="date"></label>
  <label>Guests <input type="number" name="guests" min="1"></label>
  <label>Message <textarea name="message" required></textarea></label>
  <div style="position:absolute;left:-9999px" aria-hidden="true">
    <input type="text" name="botcheck" tabindex="-1" autocomplete="off">
  </div>
  <button type="submit">Send</button>
</form>

Three places the form can live

Most restaurant sites are a builder page or just a Google profile and Instagram; the form fits each case.

• On your website: paste the form where the enquiry should happen. It is your HTML, so it inherits your design; the HTML docs list the hidden fields (redirect, subject, language).
• Without a website: every form also exists as a hosted page at formgong.com/f/<key>, built from the same saved design, plain HTML. That link goes in an Instagram bio, a Google Business Profile booking link, or a message, and submissions arrive exactly like the embedded form's.
• From a preset: the catering request template creates the form with these fields in one click, connected to your account.

Where the enquiry lands, and how fast you see it

Each submission is delivered to email and, on every plan including Free, to Telegram, with Reply and Mark handled buttons in the chat. Nobody in a restaurant sits at email during service: Telegram on the owner's or manager's phone is the difference between quoting the 30-person dinner tonight and finding the enquiry on Thursday. Every submission also sits in the dashboard inbox with CSV export, so a filtered email is never the only copy, and the free plan takes 1,000 submissions a month, which covers most small businesses with room to spare.

Spam is filtered server-side before it reaches you: a honeypot field, content checks, and optional Cloudflare Turnstile you switch on per form without touching the code. Flagged submissions land in a Spam folder you can review, so a real enquiry misjudged by the filter is one click away, not lost.

Bookings, menus and what stays out of the form

Honest boundaries: table reservations belong in the booking widget, and putting a "book a table" option in the contact form creates double-booking chaos, so the dropdown above deliberately has no such option. Menu PDFs belong on the site, not as an autoreply. And if most of your enquiries are actually phone calls, keep the number prominent next to the form rather than hoping the form replaces it; the form's win is the written record for events and catering, where "what exactly was agreed" matters weeks later, sits in the dashboard inbox, and exports to CSV when the accountant asks.

What did we miss for your business?

If your restaurant form asks something this page does not cover, or a field here earns nothing in your experience, write to support@formgong.com. These pages get better from working owners' corrections.