# 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.
- Source: https://amantrika.imswarnil.com/blog/collect-wedding-rsvps-without-whatsapp-chaos
- Author: The Amantrika Team, Amantrika
- Published: 4 July 2026
- Category: Planning
- Tags: RSVP, Planning, Guest list
- Reading time: 4 min
---
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.
Catering is usually priced per plate with a guaranteed minimum. Over-count and you pay for empty seats; under-count and there is a real, visible shortage at the reception. This is the most expensive spreadsheet at the wedding.
## 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.
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.
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.
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.
"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.
Track how many invited guests have not responded and assume a share of them attend anyway. Your caterer has seen this a hundred times and will have a number for your region — ask them rather than guessing.
## 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:
1. **A headcount per function**, which is what the caterer is waiting for.
2. **An out-of-town list with arrival dates**, which drives hotel rooms and pickups.
3. **A contact list for the day itself** — the people someone will need to call when a family cannot find the venue.
4. **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
### How far in advance should the RSVP deadline be?
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.
### What do I do about guests who never respond?
Assume a portion never will and plan for it. A targeted reminder to only the non-responders, about ten days before, recovers most of them. Chasing the whole list annoys the people who already replied.
### Should I ask for a headcount per function?
Yes, if different functions have different catering. A guest attending the sangeet and the reception but not the mehndi is common, and a single yes/no cannot express that.