How to Collect Wedding RSVPs Online (Without Chasing People)

The RSVP is the part of wedding planning that quietly eats the most time. Not the form — the form takes five minutes. The chasing. The counting. The relative who says “definitely coming” in a group chat at 11pm and is never heard from again. The caterer who needs a number on Tuesday when you have replies from a hundred and twelve of two hundred people.

An online RSVP doesn’t remove the chasing, but it does two things that matter enormously: every reply lands in one place in a consistent shape, and you can see at any moment exactly who hasn’t answered. Here is a system that works, including the parts that aren’t about software at all.

What to ask — and what to leave out

Every extra field costs you replies. This is not a hunch about form design; it is what happens when a guest opens a link on a phone between two other things. Keep it to what you will genuinely act on.

Ask these

• Name. The name you sent the invitation to, so you can match it against your list.
• Coming or not. Two options. “Maybe” is tempting and useless — it becomes a second round of chasing later.
• How many. The number that actually turns up, children included. Say “including children” explicitly or you will be told a different number on the day.
• Which events. Only if you have events with different guest lists — mehendi versus the reception, nikah versus walima. If everyone is invited to everything, skip it.
• A message. Optional, and the one field nobody minds. Couples reread these for years.

Think hard before asking these

• Meal choice. Only if the kitchen is genuinely plating per person. If the meal is a buffet or a sadhya, a dropdown the kitchen ignores just costs you completions.
• Dietary requirements. Worth asking as a free-text field if someone will read it. Ask “anything we should know?” rather than offering a list of categories.
• Phone number. You usually have it. Ask only if you plan to send day-of logistics by SMS or WhatsApp.
• Song requests. Charming, and it belongs at the end where it can’t interrupt the reply.

Don’t ask

• Postal addresses, unless you are posting something.
• Anything with a required field a guest might not be able to answer. One blocked field means one lost reply.
• How they know you. Sweet in theory; it makes the form feel like a survey.

The timeline

Timing is what separates a calm head count from a stressful one. Roughly:

• Three to four months out — save the date. No RSVP yet. You are only asking people to hold the day, which matters most for guests who need to book travel.
• Six to eight weeks out — the invitation and the link. This is when RSVPs open. Much earlier and people intend to reply later, then forget; much later and travelling guests can’t plan.
• Two to three weeks out — the deadline. Late enough that people know their own plans, early enough that you can still give the caterer and the venue a real number.
• Three or four days after the deadline — the chase. Personal messages to the people who haven’t replied. This round is where most of the remaining answers come from.
• The final count. Whatever your venue’s deadline is, work backwards from it and make your own deadline a week earlier.

Chasing the people who never reply

Every wedding has them, and they are almost never being rude — the message arrived while they were driving. What works:

• Message individually, not in a group. A broadcast to forty people gets read as an announcement. A message with the person’s name in it gets read as a question.
• Make it one tap. Send the link again in the same message. Do not make anyone scroll back through a chat to find it.
• Give a reason. “The caterer needs numbers by Friday” works far better than “please RSVP”, because it converts your admin problem into a favour they can do for you.
• Offer the escape hatch. “Just reply here if the form is easier to skip” — some relatives will never use a web form, and a reply by any route is still a reply.
• Delegate the elders. Ask a parent to phone the older relatives. It works instantly and it makes them feel useful, which is its own small gift.

Turning replies into a number you can trust

Your form gives you a total. That total is not your catering number. Adjust it:

• Start with confirmed heads, not confirmed households.
• Add the known non-repliers who are obviously coming. Your grandmother did not fill in a form and is certainly attending. Count her.
• Subtract a realistic no-show allowance. Some people who say yes will not come — illness, traffic, a clashing event. Your venue or caterer will have a local rule of thumb; ask them, they do this every weekend.
• Ask the caterer what the buffer costs. The number that matters is not the guest count but how late you can revise it and what each extra plate costs. Sometimes ordering slightly high is cheaper than the anxiety.
• Export before every conversation. Take the CSV to the meeting. “A hundred and eighty, here’s the list” is a different conversation from “about a hundred and eighty probably”.

How this works on Varumo

The RSVP form is part of every plan — there is no tier where collecting replies is the upsell, because that would defeat the point of having a wedding website at all.

• Unlimited replies. Invite as many people as you like; the count doesn’t change what you pay.
• One dashboard. Name, attending or not, how many, and the message, all in one list you can read on a phone.
• CSV export. For the caterer, the venue, the seating chart, and the thank-you cards afterwards.
• Guest messages. The notes guests leave are kept with the reply, which is where the sentimental value of the whole exercise turns out to live.
• You can switch it off. If your family is doing replies entirely by phone, turn the form off and the section disappears from the page rather than sitting there unused.
• Your own wording. The RSVP heading and prompt are editable — “Will you join us?” can become whatever your family would actually say.

One thing worth planning for: replies only arrive while the site is live. Your plan needs to still be running through the deadline and the chase round, so check how long your plan keeps the site up against your wedding date before you publish — not after.

Common mistakes

• No deadline. Without one, the answer is “later”, indefinitely.
• Asking for a yes instead of a number. The single most expensive mistake on this list.
• Never testing the form. Submit one as yourself before you share the link. Confirm it appears where you expect it to.
• Burying the RSVP. It should be reachable without scrolling through the whole page — most guests come to reply, not to browse.
• Too many required fields. Every one is a place to give up.
• Only the website. Some guests will never use a form. A phone number on the page and a parent making calls covers them.
• Forgetting the messages afterwards. Export them before you stop paying attention. They are the part you will want in five years.

Before you share the link

• Submit a test reply as yourself, from a phone, on mobile data rather than home wi-fi.
• Check the reply shows every field you asked for.
• Read the RSVP prompt aloud. It should sound like an invitation, not a form.
• Confirm the deadline appears on the page, not just in the WhatsApp message.
• Paste the link into a chat with yourself and check the preview card looks right — a broken preview costs you opens.

That’s the whole system. If you haven’t built the site yet, how to make a wedding website is the ten-minute version, the wedding website checklist covers everything else the page should carry, and the template catalogue is where to start looking. If you want the link to be your own name rather than ours, see the custom-domain guide.