Most RSVP tools were built for a Western wedding: one ceremony, one dinner, one number. Ask them to handle an Indian wedding — a haldi, a mehndi, a sangeet, the ceremony, a reception — and they quietly fall apart. The problem isn't the tool being bad. It's that an Indian wedding asks a fundamentally different question, and a single headcount can't answer it.
The multi-event problem
Picture your guest list. Your college friends are coming to the sangeet and the reception, but not the daytime rituals. Your parents' colleagues are reception-only. Your extended family is there for everything. The bride's side and the groom's side overlap on some events and not others. There is no single number that describes “who's coming” — there are as many numbers as there are functions.
Why a single RSVP fails
When you ask guests one yes-or-no question for the whole wedding, you force them to flatten a complicated answer. A guest who can only make the reception ticks “yes” — and now they're in your haldi count too. Multiply that across hundreds of guests and your numbers become fiction. The caterer for the mehndi lunch is cooking for a crowd that's actually at work that afternoon; the reception is under-catered because half the “yeses” were really reception-only all along.
The downstream cost is real money and real stress. Catering is usually priced per plate, per event. Decor and seating scale with headcount. Guess wrong in either direction and you either waste budget or run short in front of your guests.
How per-event RSVP works
The fix is to ask the right question. Instead of “are you coming to the wedding?”, you ask “which of these events will you join?” — and let each guest answer for each function. That's the whole idea behind online RSVP that tracks every event: one invitation, but a separate response for the haldi, the sangeet, the ceremony, and the reception.
For the guest it's effortless — a few taps on the invitation they already opened. For you, the payoff is enormous: every function gets its own accurate count, updated live as people respond, with no mental arithmetic on your part.
Getting accurate caterer counts
This is where per-event RSVP pays for itself. A week before each function, you can hand your caterer a number you actually trust — not a hopeful guess, but the live confirmed count for that specific event, with dietary preferences attached. You can see who's still pending and send a targeted reminder only to them. And because the data is per event, you can plan seating, favours and logistics for each function independently.
The quiet benefit: better guest experience
There's a softer win, too. When guests can say “I'll be at the sangeet and reception but not the morning rituals” cleanly, they feel respected rather than pressured into an all-or-nothing answer. They're more likely to respond at all, and to respond honestly. You get better data; they get a thoughtful invitation. Per-event RSVP isn't just an operational upgrade — it's the version of RSVP that an Indian wedding was always asking for.