How to collect wedding RSVPs without three hundred WhatsApp replies
Why Indian weddings are hard to count, what to ask for instead of a yes or no, and how to get a headcount the caterer can actually work from.
Counting guests at an Indian wedding is harder than at most weddings, for a reason that has nothing to do with technology: invitations are extended to families, attendance is decided by families, and the number changes until the week of the event.
No RSVP system fixes that. A good one just stops you from doing the arithmetic by hand.
Why the WhatsApp method breaks down
It works fine up to about forty guests. Past that it fails in specific, predictable ways.
- Replies arrive across a dozen chats and three family groups. There is no list; there is a scroll.
- "We'll definitely come!" is not a number. How many is "we"? Are the children coming? For which functions?
- Responses to the wrong person. The bride's mother gets half of them, the groom's cousin the other half, and neither has the whole picture.
- Late changes overwrite nothing. A "make that four instead of six" sent three weeks after the original message is simply gone.
- You cannot tell who has not replied, because absence of a reply looks identical to a reply you scrolled past.
Ask for the right things
The single biggest improvement is not the tool. It is what you ask. A yes/no question produces answers you cannot cater from.
| Ask this | Instead of | Because |
|---|---|---|
| How many adults and how many children? | How many guests? | Children's plates are often priced differently, and "guests" gets interpreted inconsistently |
| Which functions will you attend? | Are you coming? | Different functions, different catering, different headcounts |
| Name of the person responding | (nothing) | Otherwise you get a count with no idea whose family it is |
| Phone number | (nothing) | You will need to reach someone about arrival timings |
| Arrival date, for out-of-town guests | (nothing) | Drives hotel blocks and airport pickups |
| Meal preference, if you're catering separately | (nothing) | Only ask if it changes what the caterer does; otherwise it's noise |
Keep it to what you will act on. Every extra field costs you completed responses, and a field you never look at costs you responses for nothing.
Make responding take fifteen seconds
Guests do not abandon RSVP forms because they are undecided. They abandon them because the form asked for eight things while they were standing in a queue.
Put the form in the invitation itself
Not a link to a separate site, not an email address. The guest is already looking at the invitation; the form should be the next thing they scroll to.
Pre-fill everything you already know
If you sent a personalised link, their name and phone number should already be filled in. What remains is a headcount and a function or two — genuinely a few seconds.
Don't require an account
No login, no OTP, no app. Every step between the guest and the submit button costs you responses, and the elderly relatives you most need a count for are the first to drop off.
Confirm on screen, immediately
"Thank you, we have you down for four" prevents the double-submission that inflates your count.
Chase the non-responders, not everyone
The reminder that works is targeted. A message to the whole list irritates the two hundred people who already replied and teaches them to ignore the next one.
A workable schedule:
- On sending: expect a burst of responses in the first 48 hours. This is most of your eventual total.
- Three to four weeks before: a reminder to people who have not responded. This is the one that recovers the most.
- Ten days before: a final, short message to the remaining non-responders. Give a deadline and mean it.
- After the deadline: stop asking and estimate. Some families will simply arrive.
What to do with the responses
A list of names is not a plan. Before the week of the wedding, turn the responses into four things:
- A headcount per function, which is what the caterer is waiting for.
- An out-of-town list with arrival dates, which drives hotel rooms and pickups.
- A contact list for the day itself — the people someone will need to call when a family cannot find the venue.
- A seating or table plan, if you are doing one, built from confirmed numbers rather than the invitation list.
If your RSVP responses cannot be exported to a spreadsheet, you will end up retyping them at the worst possible moment. Check that before you start collecting.
Frequently asked questions
Two to three weeks before the wedding for most caterers, though ask yours — many need final numbers earlier than couples expect, and some accept adjustments up to 72 hours before.
Filed under
Keep reading
Digital or printed wedding invitations: an honest comparison
What each format actually does well, what it costs, and why most Indian families end up using both — with a rule for deciding who gets which.
The ceremonies in a Hindu wedding, and which ones your invitation should name
From roka to vidaai: what each ceremony is, roughly when it happens, and how to put the schedule on an invitation so guests know where to be.
Sharing your wedding invitation on WhatsApp without it getting lost
What to write around the link, when to send it, and why a bare forwarded URL gets ignored by exactly the guests you most want to reach.