The Indian wedding RSVP guide.

Each event gets its own guest list and its own RSVP on one wedding website. You build a single master guest list, mark which households are invited to the mehndi, sangeet, haldi, ceremony, and reception, then send each household a private link. Guests reply yes or no for every event they are invited to, choose meals where food is served, and add dietary notes once. OfficiallyTogether keeps live per-event counts so your caterer gets accurate numbers for every function, not one blended total that hides who is coming to the sangeet versus the reception.

Yes, and most Indian weddings depend on it. Visibility is set per guest and per household: close family often see the full multi-day program, while extended family or reception-only guests see just the events meant for them. Each household opens a private link tied to their invite, so nobody sees a function they were not invited to and you avoid the awkward moment when someone asks why they were not on the mehndi list. That per-guest visibility is what makes a 300-guest, three-day wedding manageable without maintaining separate spreadsheets for each day.

Send each household a private RSVP link instead of asking for replies in a group chat or shared spreadsheet. With around 330 guests at a typical Indian wedding (WeddingWire India, 2024), scattered replies bury themselves fast. A link opens in any browser, shows only that household's events, and collects attendance, party size, and meal choices in one dashboard. Families often reply together, which matches how South Asian households actually coordinate, and you stop retyping answers from screenshots into a sheet.

For each event a guest is invited to, ask for attendance, the number attending within their allowed party size, and a meal choice where a meal is served. Collect dietary notes and allergies once in plain language, not medical codes guests will not understand. Keep optional fields short, like one song request, so older relatives can finish in under a minute. Ask separately per event rather than one blanket yes, because the mehndi headcount and the reception headcount are never the same number and your caterer needs both.

Ask for replies three to four weeks before your first event, or four to six weeks out if a caterer needs an early headcount for a plated dinner. Set the deadline per function on your wedding site so guests see it when they reply. Send one warm reminder a week before the date and a short final nudge a few days out, each with the same direct link. That rhythm catches the last ten percent without nagging the three hundred who already replied, and leaves you time to finalize seating and meals before the first haldi or mehndi.

Yes. You can build your wedding website, add every event, and collect per-event RSVPs for free on OfficiallyTogether. Optional paid packs add extras like advanced planning tools, but the core site, guest list, and RSVPs cost nothing and no credit card is required to start. That matters for multi-day weddings where you are already spending across several functions: the RSVP layer should not add another vendor invoice before you know your final headcounts.