Someone joins the waitlist for your repair booking app. The page thanks them. Later, you open your signup list and their email address is missing. Before you share a waitlist, check both sides of that moment. The person should know what to expect, and you should be able to find their answer without asking them to sign up again.
Start with Tally when you need a short form and a list you can copy to Google Sheets. Typeform also connects to Sheets and can show one question at a time. Check its account allowance before sharing widely. Fillout fits when your organizer wants specific answers in an Airtable or Zite Database table.
What should your first waitlist ask?
Collect an email address so you can tell people when booking opens. Ask one optional question only if its answer will change what you do. “Would you prefer a weekday or a weekend?” can help you choose which times to offer first. You can ask for the actual appointment time after you open bookings.
Say what happens after they submit. If you plan to send one launch email, tell them “You joined the waitlist. We’ll email when repair bookings open.” Check the saved list before you rely on the confirmation.
Where will you find the signup?
Start with the list inside the form tool. A spreadsheet or database connection can put a second copy in a place your team already uses. That extra copy is worth setting up when it changes who can act on the responses or what they need to do next.
| Tool | Where to look first | How to keep or connect a copy |
|---|---|---|
| Tally | Open Submissions for the form. | Download a CSV or connect a Google Sheet to receive new submissions. |
| Typeform | Open Results, then Responses. | Export answers as CSV or XLSX, or connect a Google Sheet. Filters and selected rows can limit the export. |
| Fillout | Open Results for the form. | Download a CSV. Clear filters to include all results. To route answers to another table, connect Airtable or Zite Database. |
A CSV is a file of rows and columns you can open in a spreadsheet. It is useful when you want to keep your own copy, even if you never connect the form to another service. A connected spreadsheet or table has its own sharing settings. Check who can open that copy.
For a public Fillout waitlist connected to Airtable, choose the action that creates a record. The update action is for someone editing an existing record. An Airtable update link can expose information from that record beyond the fields visible on the form. Keep it out of a public signup flow.
What happens when you want to stop at ten submissions?
There are two limits to check. A plan allowance tells you how many responses an account can collect. A closure rule tells one form when to stop taking new entries. A response can count toward both.
- Tally lists unlimited submissions on Free under its fair use policy. Its form settings include manual closure and a maximum number of submissions for automatic closure. Set the limit before sharing if you want a fresh form to stop after ten entries.
- Typeform documents ten responses a month across the account on its Free plan. Typeform sometimes tests different plans, so open the organization menu in your workspace and choose Plan & billing to see your allowance. If your account allows ten and another form used eight, two remain for the waitlist. When the account reaches the limit, its forms go private until the allowance resets or you upgrade. Typeform documents a separate automatic closure option on Business. That option counts new submissions from when you save the setting. You can also close an individual form by hand.
- Fillout Free includes 1,000 completed responses a month across the organization. Its per-form setting can close one form at a chosen count up to 1,000 finished submissions. Existing finished entries count toward that setting, and it does not reset each month. To reopen a form that hit its limit, raise or remove the limit, then turn off Close form and save. Fillout says collection can continue above the plan allowance, with possible restrictions after repeated overuse.
These are the November 2026 plan and closure rules. They count submissions under the tool’s rules. If the same email appears in two rows, you have two responses to review. Count people separately when you decide who to invite. A waitlist confirms interest. Your booking app still has to confirm who gets an actual appointment.
How can you test one signup before sharing?
Use a disposable form you have never shared, with email actions and live tables disconnected. Use made-up answers and a test email address you control if the form needs a deliverable address. Keep the copied data in a private test file. Use Preview to check the questions and ending. To verify that an answer reached the organizer, check the saved response. A live test can use part of the plan allowance. Check what is left first if the account already has forms people use. If you cannot isolate the form or its connections, write down the expected results and stop before submitting.
- Try the respondent link. Open it signed out, as a new visitor would. Make sure it opens the form without giving access to the response list. Submit one dummy signup with a test address and a preference, such as “weekend.” If you repeat the check, use a fresh test address or clear the old test entry first.
- Find that exact signup as the organizer. Check that the confirmation says what happens next, then look up the dummy email in the form’s saved responses. Download a copy and confirm it contains the same address and preference.
- Check the extra copy only if you need it. Connect a separate test spreadsheet or table and confirm its sharing settings only allow the organizer to open it. Submit a new dummy signup and check for one matching row in each place.
If you plan to close automatically, use an otherwise empty disposable form on a plan that supports the rule. Try a small cap, verify that the last allowed signup appears in the organizer’s list, and open the form again as a new visitor to check the closed message.