Ask anyone who has planned an Indian wedding what the hardest headcount in the world is, and they will describe the fortnight before the wedding: the caterer needs a final number, per function, and the family is still reconstructing who said yes — in which phone call, in which group chat, to which aunt. An online RSVP does not remove the warmth of asking. It removes the archaeology. The reply lives inside the invitation itself, and every answer lands in one place.
What the guest sees
The guest opens the invitation link — the same link that showed them your names, the programme and the venue — and near the end finds the reply section. It asks for the few things that matter: their name, whether they are attending, how many are coming with them, and which functions they will join. There is no app to install and no account to create; the whole reply takes under a minute, on the phone already in their hand. That simplicity is the entire secret. Every extra step invented by invitation software — sign-ups, passwords, separate RSVP websites — is answered by real guests in the simplest way possible: they do not reply at all.
What you see
On your side, the replies gather into one live list: who has replied, who is coming, how many seats each reply represents, and — quietly the most valuable view — who has not replied yet. Instead of a spreadsheet rebuilt nightly from call notes, you watch the number settle. When the caterer asks for the count, you read it off. When a venue's capacity is tight, you see the pressure coming weeks early, while it can still be solved gracefully.
Per-function replies — the Indian detail
A single yes/no is not enough for a wedding with five functions. A guest may attend the reception but not the Sangeet; an outstation family may arrive only on the wedding day. So the reply should be collected per function: attending the Haldi? the Mehndi? the ceremony? the reception? Those four answers are four different catering and seating numbers. This one design decision — replies per event, not per wedding — is the difference between a list that looks tidy and a list that is actually true. It is why our invitations, such as the Pearl design, collect the reply inside the full programme rather than on a separate card.
Setting the deadline properly
Ask for replies two to three weeks before the wedding. Earlier, and guests answer carelessly because their own plans are not real yet; later, and your caterer's deadline has already passed. Keep a small buffer between the RSVP date you print and the date your vendors truly need — life will fill it. And word the request kindly: a line such as "Kindly respond by 2 April, so we may keep a seat and a plate ready for you" gets more replies than any bold red deadline, because it tells the guest what their answer is for.
Reminders without awkwardness
Some guests will not reply, and chasing them is where families bruise feelings. The civilised order is: one gentle reminder message to everyone who has not replied, a week before the deadline — short, warm, with the link again, because the original is buried under a month of chats. After that, the very short remaining list gets personal phone calls, ideally from whoever invited them. Elders who do not use links are not a problem to be solved by software: a son or niece can open the invitation and reply on their behalf, and their name joins the same list. The honest comparison in our digital vs printed invitations guide makes the same point from the other side — print has no reply mechanism at all, which is why the phone calls were invented.
The short version
Online RSVP works when the reply is inside the invitation, takes under a minute, counts guests as well as names, answers per function, and shows you one settling list — including who is still silent. Set the deadline two to three weeks out, remind once with warmth, and give the remaining few a phone call, which is what those calls were always for. When you are ready to see it from your guests' side, make a free demo and send the link to your own phone first.
Common questions
Do guests need an app or an account to RSVP?
No. The invitation opens from its link in any phone browser, and the reply form sits inside the invitation itself. A guest types their name, taps whether they are attending, and sends — no app to install, no account to create, no password to forget. If a guest can open a link, they can reply.
Can one person reply for the whole family?
Yes, and in Indian families that is how it usually happens: one reply per household, with the number of guests attending stated in it. The form should always ask how many are coming, not just whether — a yes from a family of five and a yes from a single cousin are very different numbers for your caterer.
What about guests who never reply?
Every system leaves a small remainder — typically the eldest relatives and the busiest cousins. The value of collecting replies online is that you can see exactly who they are, in one short list, instead of wondering about three hundred names. Those few get a personal phone call, which is what those calls were always for.
See a reply being collected: open the Pearl invitation and scroll to its reply section — that is all your guests will ever have to do. Or create your free demo and test the full journey on your own phone.