Making an online RSVP or order form
Collecting RSVPs for a function or orders for a weekend sale over chat messages works until about the twentieth reply. Then names get missed, quantities are unclear and someone’s “+2” is lost in a long thread. An online form gives every reply the same shape and puts them all in one list. This article shows how to plan a good form, build it, test it and use the replies — the advice applies to any form tool.
Step 1: decide what you need to know
Write down what you will do with the answers. For a wedding RSVP: how many people will come, any food preferences, and how to contact them. For a Diwali sweets order: what, how much, when, where to deliver, and how they will pay. Every question that does not change what you do can be removed. Short forms get more replies.
Step 2: choose the right field for each question
- Full name and phone fields for contact details.
- Radio buttons when exactly one answer is allowed (Attending: Yes / No / Maybe).
- A number or short-text field for quantities (“How many guests including you?”).
- Date and time or an appointment slot for pickup or delivery times.
- Address only if you deliver.
- A free-text answer for anything else (“Allergies or special requests”).
Mark only the truly necessary questions as required. If a question applies only to some people, use conditional logic — for example, show “Number of guests” only when someone answers “Attending: Yes”.
Worked example: a society Diwali sweets order
The residents’ association of a housing society in Sector 70, Mohali, takes orders for sweets from a local halwai. Their form has:
- Name and flat number (required)
- Phone (required)
- Kaju katli — 250 g boxes (radio: 0, 1, 2, 3, 4)
- Mixed mithai — 500 g boxes (radio: 0, 1, 2, 3, 4)
- Pickup or delivery to flat (radio); if delivery, a delivery slot appears
- Note (optional)
The form description says: “Orders close Friday 8 pm. Pay by UPI to the association account after you get the confirmation message. Pickup Sunday 10 am–1 pm at the clubhouse.” Everyone knows what happens next, and the organisers get a clean list to send to the halwai.
Step 3: test before sharing
- Preview the form on a phone — most people will open it there.
- Submit one test reply yourself through the public link.
- Check that the reply appears where you expect and that conditional questions show and hide correctly.
- Delete or mark the test reply so it is not counted.
Step 4: share the link
Share the public link — not the page you edit the form on. Put it in the group message with one line about the deadline. For a notice board or invitation card, turn the link into a QR code and test-scan it before printing. Anyone with the link can reply, so share it only where you want replies from.
Step 5: use the replies
Read replies in a spreadsheet: filter by pickup vs delivery, total the quantities with a SUM, and add a column for “Paid” and the UPI reference. After the deadline, close the form so late replies don’t slip in unnoticed. Send each person a short confirmation of what you received.
Payments: keep them separate and safe
If the form doesn’t take payment, ask people to pay by UPI to one official account after they get your confirmation, then match payments using the UTR in the sheet. Never accept a screenshot alone as proof — see Collecting customer payments safely.
Privacy
Ask only for what you need, say in the form description how you will use the details, and don’t share the replies sheet with the whole group — it contains everyone’s phone numbers. Share a summary instead. See Sharing a spreadsheet safely.
Wording tips that reduce confusion
- Put units in the question: “Boxes of 250 g”, not just “Quantity”.
- Give the deadline and the pickup or event date in the form description, not only in the chat message.
- Use the same option names everywhere — if the menu says “Kaju katli”, don’t call it “cashew barfi” in the form.
- End with a clear line about what happens after submitting, such as when you will confirm.
Doing this with Conserworks apps
C Forms has name, phone, choice, date, time, appointment, address and file upload fields, conditional logic, a Preview mode and a public link; each form also creates a C Sheet workbook where every reply lands as a row. C Graphics can turn the link into a QR code.
Frequently asked questions
Do people need an account to fill the form?
Usually not; most form tools, including C Forms, let anyone with the public link reply.
How many questions is too many?
If a question doesn’t change what you will do, remove it. For RSVPs and small orders, five to eight questions is usually enough.
How do I stop duplicate replies?
Ask for a phone number or flat number and sort by it in the sheet; contact anyone who appears twice.