Waitlist and RSVP forms without buying another tool

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: You can collect a waitlist or RSVP list with a plain form on your own website, as long as it saves every entry somewhere you can read, emails you when one arrives, and lets you cap or close signups by hand. Free options include the form built into your website platform, Tally (a free online form builder), a spreadsheet-backed form, and Luma (a free event page and guest list service). A built-in form usually does not send confirmation emails or enforce a seat limit, so plan those two jobs yourself.

Ranjit Bhinge

You want a signup or RSVP list for an event or launch without paying for one more tool, and you want to be sure nobody slips through.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Decide what the list must do before you pick a form. A waitlist only needs name, email and a time stamp. An RSVP also needs a headcount and often a seat limit. Neither needs payments or a calendar of time slots, and if yours does, you need a booking tool, not a form. If you are collecting any entries at all, the two things that fail most often are the notification that never arrives and the list nobody exports. Both are fixed with a test and a habit, covered below.

This page covers the free and built-in options, how to handle capacity, confirmation emails, export and spam, a made-up worked example, a weekly test plan, and who should use a different tool. For the general case of lead and quote forms, see forms, booking and payments on your website and a landing page with a built-in form.

This page may contain affiliate links from which Blur Studio earns commissions.

Your options, from least to most effort

OptionCost (as of November 2026, check each vendor page)Good forWatch out for
A form already built into your website platformUsually included in your planSimple lists on your own page and domainSeat limits and confirmation emails are often manual
Tally, a free form builderFree plan: unlimited forms and submissions within its fair usage guidelines. Pro $24 a month, Business $74 a month (monthly figures)Waitlists and RSVPs you embed or linkIts pricing page does not mention spam filtering, so check
Typeform, a form builder with one-question-at-a-time formsFree: 10 responses a month. Paid plan prices differ between the plan cards and the comparison table on the page, so check the vendor pageShort forms with a polished lookEach submitted response counts, including test submissions on a published form
Luma, a service for event pages and guest listsFree: unlimited events and guests, up to 500 invites or newsletters a week, 5 percent platform fee on paid events. Plus $59 a month billed annually, per its page, in US dollarsEvents where you want a guest list and remindersIt is a separate page, not your own site. Card fees are extra on paid events
Eventbrite, a ticketing marketplaceFree events at no cost. Paid tickets carry service fees (3.7 percent plus $1.79 per ticket, plus 2.9 percent payment processing, per its page, currency not named)Public events with ticketingDo not call it free if you sell tickets
Mailchimp (email marketing) or HubSpot (a customer database, or CRM), email and CRM toolsCheck the vendor pageWhen you already use them and want signups to land in your email listHubSpot forms on an outside site need its tracking code installed and the page domain added, or submissions can be marked as spam
A form by hand: email link, spreadsheetFreeUnder 30 people, onceDuplicates, typos and no record

If your site is a static site on Netlify, its built-in forms feature is another no-backend route, covered in Netlify Forms. A fair rule: the less you want to move, the more the built-in form wins. The more you need reminders, ticketing and a guest-facing page, the more a service such as Luma wins.

If your website platform has a built-in form

On Ploy, an AI website builder and host, forms built into a Ploy site capture submissions automatically. Per Ploy's docs, you review them at Sites, your site, Dashboard, Submissions, and add the email addresses that should get alerts through Notifications in the upper right. If the form has an email field, the notification uses the submitter's email as the reply-to address. Facts to plan around, as of November 2026:

  • Forms are available on all plans. CRM routing follows plan: per Ploy's plan table, HubSpot and Attio are on Pro, Mailchimp and similar tools are listed at Pro and above, and the pricing page shows Free at $0, Starter at $50 a month, Pro at $300 a month and Enterprise by quote. Check the pricing page for your plan.
  • Text only. Built-in submissions have no file fields, and each submission can be up to 128 KB. Larger ones are rejected and the form shows an error. Files go to a database table with a File column instead.
  • No booking engine. Ploy lists integrations with Calendly and Cal.com (two scheduling tools that give people a booking link), but a form is not a calendar. Do not promise time slots from a Ploy form.
  • Not confirmed in the docs: an automatic confirmation email to the person who signed up, built-in CAPTCHA, a consent checkbox, and form-level rate limits. Ploy's database docs say public forms that accept files should have spam protection and suggest asking Ploy's Agent to add it, which tells you spam protection is not on by default for that case.

Submissions from the editor preview or the Preview address are saved and emailed like live ones. So test entries will sit in your real list until you delete them. Mark test rows clearly, for example "TEST do not use" in the name field.

Capacity limits, done by hand

A free form rarely stops accepting entries at a number. Use one of these.

  1. Count and close. Check the entry count each morning. When you hit the cap, replace the form with a message such as "This event is full. Join the waitlist" that points to a second form. Put a calendar reminder at 80 percent of capacity.
  2. Over-accept on purpose. If you usually see about 25 percent no-shows, accept somewhat more than the seat count. Use your own past events, not a general figure.
  3. Two lists. Make "RSVP" and "Waitlist" two separate forms or a field named "list". When someone cancels, email the first waitlist person.
  4. Use a service that enforces it. If you need a hard limit with automatic closing, use an event tool, such as Luma, and check its page for how it handles capacity.

Confirmation emails

People who sign up expect a reply. If your form cannot send one, you have three workable choices.

  • A thank-you message on the page after submission, stating the date, place and "we will email you the week before". Tell them to check spam.
  • A manual email to each person, from a saved template, for lists under about 40 people.
  • An email tool or automation that sends on each new entry. Before you build it, check how the form hands data to it. Look at your plan: for Ploy, Mailchimp for waitlist signups is listed at Pro and above in the plan table. A connector tool such as Zapier (a service that links apps) has its own task limits, so check the vendor page.

Send from an address on your own domain, and send a test to a Gmail and an Outlook inbox. If you are unsure why form emails go missing, see the forms not sending checklist.

Export, privacy and spam

  • Export. Before launch, find where the export button is, and export once. If your platform stores submissions in a database table, check the export limits for that table. Ploy's database docs list a CSV export of up to 10,000 rows per view and say a CSV is for interchange, not backup. I would not assume the same applies to the Submissions list, so check with Ploy for that view.
  • Privacy. A guest list is personal data. Collect only what you need, say what you will do with it, and delete it after the event if you said you would. Rules differ by place, so check local law. See the privacy law page.
  • Spam. Public forms attract bots. Add a honeypot (a hidden field that only bots fill in) or a CAPTCHA (a puzzle that people can pass) if your tool offers one, and read how to stop spam on a contact form. Sort your list by email once a week to find duplicates and obvious junk.
  • Do not rely on email alone. The notification email is a convenience. The saved list is the record.

A worked example with made-up numbers

A bakery plans a 40-seat tasting night. Past events had about 20 percent no-shows (their own made-up figure). They decide to accept 48 RSVPs, then open a waitlist.

DayEvent (made up)Action
Day 1Form goes live. Test entry submittedCheck owner inbox and spam folder. Delete test row
Day 331 RSVPsExport list as a backup. Remove 2 duplicates
Day 648 RSVPsSwap the form for a "full, join the waitlist" form
Day 96 cancellations by emailEmail the first 6 waitlist names, fill seats
Day 14, event dayArrival list printedPrinted from the saved export, not from email

The cost was zero new tools, about 15 minutes of checking spread over two weeks, and a text reminder the day before. If 8 of the 48 fail to turn up, 40 people attend and every seat is used. If only 3 fail to turn up, 45 arrive for 40 seats, so the waitlist should stay closed until you see real cancellations. The numbers would change per event, so rebuild the sheet each time.

Weekly test plan with pass and fail rules

  1. Submit a test entry from a phone on mobile data. Pass: success message shows. Fail: error or blank page.
  2. Check the owner inbox and spam folder within 5 minutes. Pass: notification arrived. Fail: nothing, so check the notification address and the spam folder.
  3. Check the saved list. Pass: the entry is in the list with the right fields. Fail: missing, so the form is not saving.
  4. Check the confirmation email, if any. Pass: arrives in Gmail and Outlook inboxes. Fail: lands in spam or never comes.
  5. Check the CRM or email list, if connected. Pass: contact appears. Fail: missing, so check the connection and your plan.
  6. Test again after any site change. Edits and redesigns are when forms break.
  7. Export once a week. Pass: file opens with all rows. Fail: row count lower than the list, so fix before the event.

Who should use something else

  • Anyone who needs payments or time slots. Use a booking or ticketing tool. A form on a Ploy site is not a booking engine, and Ploy's docs do not describe built-in payment collection.
  • Events over a few hundred guests, or ones with reminders, check-in and ticket scanning. Use an event platform and check its fees.
  • Teams that already live in a CRM. Use that CRM's own form, and follow its embed rules.
  • Anyone who needs file uploads in the form, such as ID copies. That needs a different setup. Check how files are stored and who can open them.
  • Anyone whose site is staying on another platform. Moving a site only for one form is not worth it. A free standalone form, embedded, is enough.

How I'd approach this

I would start with the form your site already has. If it saves entries, emails you and lets you export, use it and handle capacity and confirmations by hand. If it cannot, embed a free Tally form or send people to a free Luma page, whichever matches how much of the event you want to run. If you are building or rebuilding the site anyway, a platform such as Ploy has forms on every plan, so you can try the form for free before you decide on a paid tier. If you need a custom signup, quote or booking flow, or a form that keeps failing fixed, Blur Studio builds and repairs those, see what a custom build includes.

First-week plan. Day 1: write down the three things the list must do (fields, cap, confirmation). Day 2: pick the form and build it with the fewest fields. Day 3: run the seven-step test and delete the test rows. Day 4: set the notification addresses (two people, not one) and write the thank-you message. Day 5: put the cap date and the 80 percent reminder in your calendar. Day 7: export once, open the file, and set a weekly repeat.

Related guide: A Directory of Team Members, Properties or Distributors on Your Site.

Related guide: How to Store Form Entries and Leads as Rows You Can Use.

A closely related page covers the same ground from another angle: Ask AI About Website Visitors Without Opening a Dashboard.

For the next step, see How to Edit Website Pages From Your Phone.

I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.

Questions people ask

What is the simplest way to build a waitlist on my website?

A form with name and email that saves every entry and emails you. Use the form your platform already includes, or a free Tally form embedded on the page. Test it from a phone and check the spam folder before you share it.

Can a website form limit RSVPs to a set number of seats?

Many free forms do not enforce a limit. Check the count yourself and swap the form for a waitlist form at your cap, or use an event tool that enforces capacity. Check the tool's page for how it handles this.

Does a Ploy form send a confirmation email to the person who signs up?

Ploy's docs describe notification emails to you, with the submitter's email as the reply-to when the form has an email field. They do not describe an automatic confirmation email to the submitter, so write a thank-you message on the page and plan a manual or connected email. Compare plans on the Ploy pricing page.

Is Typeform free for waitlists?

Typeform's free plan allows unlimited forms but only 10 responses a month, and test submissions on a published form count. Paid plan prices show differently on the plan cards and in the comparison table of its pricing page, so check the vendor page.

Is Luma or Eventbrite free for events?

Luma's free plan has unlimited events and guests and up to 500 invites or newsletters a week, with a 5 percent platform fee on paid events. Eventbrite lets you publish free events at no cost, but paid tickets carry service and payment fees. Check each page for current terms.

How do I stop spam signups on a waitlist?

Add a honeypot field or CAPTCHA if your tool offers one, sort by email for duplicates once a week, and do not trust an unfiltered list. See how to stop spam on a contact form.

Can I collect payments or bookings with a plain form?

No. A form records details. Payments need a payment provider and bookings need a scheduling tool. Ploy's docs list no built-in booking engine and link Calendly and Cal.com for that. See forms, booking and payments.

Is a guest list personal data?

Yes. Collect only what you need, say what you will do with it, and delete it when you said you would. Rules vary by country and state, so check local law and your platform's current terms.

More in this topic: Websites: forms, directories and editing on the go (5 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…