Home · Use Cases · Weddings & Family Events

Wedding RSVP and guest management for Indian weddings

Baraat, mehendi, sangeet, cocktails, reception. Different guest lists for each. Different venues. Different meal counts to send the caterer. You can juggle it on a family WhatsApp group, or you can put it on a private subdomain where every guest confirms their RSVP, picks their meal, and shows up with a QR pass at the gate.

What you get

Who this fits

• Destination weddings with 200-800 guests across multiple days and venues
• Multi-function Indian weddings where the baraat and reception have very different guest lists
• Wedding planners running 10-30 weddings a season, each on the couple's own subdomain
• NRI weddings where you need to track who's flying in and coordinate pick-ups
• Anniversary parties and family reunions (same toolkit, smaller scale)

A real wedding timeline

Priya and Karthik. 312 guests, five functions, destination wedding in Udaipur. Guest list stretched from Mumbai to Toronto. Muhurat on a Tuesday. Here is what the tool actually did.

T-45 days. Bride's mother uploaded the master guest list from an old family Excel. 312 rows, with plus-ones. We split it into five function-level lists inside the Sub-Events module. Baraat had 180 guests, mehendi 90, sangeet 260, cocktails 200, reception 312. A few uncles were on all five. Two were on reception only.

T-30. Personalised RSVP links went out over WhatsApp using a family broadcast list. Each link carried the guest's name pre-filled so no one had to type anything. First 48 hours, 189 RSVPs. Meal counts flowed in: 214 vegetarian, 78 non-veg, 12 Jain, 8 vegan.

T-14. Seat allocation for reception. Auto-assigned V-1 through V-40 for close family, G-41 onwards for the rest. Groom's parents wanted table 7 for the Delhi cousins. Changed in the dashboard, new pass regenerated, WhatsApp updated. Two minutes.

T-3. Reminder pass sent again. NRI guests who had lost the earlier link found it in the fresh WhatsApp. Photo delivery kit primed for the sat-sang.

Wedding day. Two family members with the Scanner module on their phones at the mandap entrance. QR pass scan, name flashes on screen, welcomed. No printed guest list at the door. Zero gate-crashers. Caterer got the actual meal count for sangeet by 4 PM (198 confirmed showed against 260 invited, a much better number for the biryani).

T+5. Reception photos shared over WhatsApp broadcast, tagged with seat numbers so guests found themselves easily.

What breaks when you use a general tool for weddings

Google Forms is not built for plus-ones. It cannot ask "how many are coming with you" without a follow-up column that nobody fills right. Eventbrite thinks a wedding is a ticketed event and charges 3.5% on your muhurat.

The WhatsApp broadcast list becomes the guest list, which means when Neha aunty misses the mehendi confirmation and her three sons show up anyway, no one has meal count for them. The mandap seat number does not fit on a paper card. The badge printer at the venue is a laser your caterer's brother brought. It jams at guest 87.

Meal counts are a hand-tallied Excel that the caterer keeps asking for a fresh copy of. Baraat and reception guest lists get mixed up because they live in the same spreadsheet with a colour code that gets dropped when someone opens it in Numbers on a Mac.

None of this is a tool problem. It is a five-tools problem, and they do not talk to each other. One tool that knows a wedding is five events with overlapping guest lists is the whole trick.

The modules wedding organisers use most

Common questions