HTML Waitlists

HTML waitlist signup form template.

Use this short waitlist workflow to collect a reachable email address and enough preference data to send a relevant launch update without building a signup backend.

Fields

What this form captures

  • Name and email address
  • Product or plan of interest
  • Launch timing and referral source
  • Explicit launch-update consent

Workflow

How to use it with FormsFort

  1. Send a confirmation email when someone joins the list.
  2. Group signups by product interest for a targeted launch announcement.
  3. Record the referral source for campaign reporting.
  4. Remove or export a subscriber through a webhook when the launch list changes.

Copy-paste HTML

Backend-ready form code.

Replace YOUR_ACCESS_KEY with your FormsFort public access key, then deploy the form on your site.

<form action="https://api.formsfort.com/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
  <input type="hidden" name="subject" value="New waitlist signup" />
  <input type="hidden" name="list" value="product-waitlist" />

  <label for="waitlist_name">Name</label>
  <input type="text" id="waitlist_name" name="name" autocomplete="name" required />

  <label for="waitlist_email">Email address</label>
  <input type="email" id="waitlist_email" name="email" autocomplete="email" required />

  <label for="waitlist_product">What would you like to try?</label>
  <select id="waitlist_product" name="product_interest" required>
    <option value="">Choose an option</option>
    <option value="starter">Starter plan</option>
    <option value="team">Team plan</option>
    <option value="integrations">Integrations</option>
  </select>

  <label for="waitlist_timing">When do you need it?</label>
  <select id="waitlist_timing" name="launch_timing">
    <option value="as-soon-as-available">As soon as it is available</option>
    <option value="next-quarter">Next quarter</option>
    <option value="just-looking">Just looking</option>
  </select>

  <label for="referral">How did you hear about us?</label>
  <input type="text" id="referral" name="referral_source" />

  <label for="waitlist_consent">
    <input type="checkbox" id="waitlist_consent" name="launch_updates" value="yes" required />
    Email me when this product is available.
  </label>

  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off" />
  <button type="submit">Join the waitlist</button>
</form>

Production notes

Make it reliable before launch

  • Submit from the real production domain and confirm delivery logs show the expected origin.
  • Keep hidden fields for routing and context, not secrets. Public access keys are identifiers.
  • Use allowed domains, honeypots, rate limits, and optional CAPTCHA for public forms.
  • Test uploads, webhook payloads, spreadsheet rows, and autoresponder copy before publishing.

FAQ

Common questions

Can one waitlist form serve several products?

Yes. Keep the product interest select and list hidden field, then use those values to segment notifications or route the signup to separate webhook workflows.

Why include consent on a waitlist form?

A dedicated checkbox makes the purpose of the email explicit. Keep the label next to the control and only send launch updates to people who opted in.

How do I prevent duplicate signups?

Use the email as the matching value in your connected CRM or spreadsheet workflow. FormsFort receives each submission and gives the downstream system the fields needed to deduplicate.