How to collect and manage RSVPs for a big Indian wedding
How to ask for replies on the invitation, what to collect, and how to read the list without a dozen family spreadsheets.
Decide who must reply
A big Indian wedding does not need an RSVP from every person who might hear about it. Decide the list that changes catering, rooms, or seating: the reception, the wedding lunch, or the outstation guests who need a room count. Family who live in the same house do not need a form to tell you they are coming.
Split the ask by function if the guest lists differ. Colleagues at the reception should not be forced through a mehendi headcount. On Maṅgalya, RSVP sits on the live invitation. Guests submit on the page. You sign in with the owner email and open the dashboard to see responses in one place.
RSVP is not part of the ₹799 publish fee. It is an optional ₹399 add-on, turned on when you want the form. Design and preview stay free either way. If you only need a headcount in a family group, you can publish without the add-on.
Say the deadline in the invitation, not only in a voice note. A date ten days before the first function is more useful than “as soon as possible”. People travelling for a Thursday wedding book tickets on a Sunday night. Your number has to exist before that.
Ask for fewer fields
Collect attendance, the function or meal they are coming for, and a phone number you can reach. Add a headcount only if one reply covers a family. Extra questions — song requests, hotel room type, childhood memories — cut the completion rate and do not help the caterer.
Name the meal choice in the words the kitchen uses. “Veg” and “non-veg” are enough for most halls. A Jain option matters if you will actually plate it. Do not offer a choice you cannot serve.
One reply per household is easier to manage than one reply per cousin, unless your seating plan is individual. Say that in the form label: “Reply for your family” or “Reply for yourself”. Ambiguous labels produce double counts.
Guests should not need an app or a Maṅgalya account. They open the link, usually from WhatsApp, and submit. If someone cannot use the form, take their reply yourself and treat the dashboard as the list you trust, not the chat scroll.
Read the dashboard like a host
Check the dashboard on a rhythm, not whenever an uncle forwards a screenshot. Twice a week in the last month, then daily in the last week, is enough for most weddings. Assign one person to own the list. Two siblings updating two sheets is how the chicken count doubles.
Sort by function before you call the caterer. A yes to the sangeet is not a yes to the wedding lunch. If your form did not separate them, you will spend a day calling people back. Fix the form early. The same invitation link can be edited after you have already sent it.
Export or copy the names you will hand to the hall. The dashboard is the source. A WhatsApp group is a conversation. When they disagree, believe the form, then call the three households that look wrong.
Pending names are not a moral failure. Send one reminder with the same link, to the people who have not replied, close to the deadline. Do not repost the invitation into every group every morning. The etiquette guide covers how to share the link without exhausting people.
Side lists that still belong on the page
Room blocks, shuttle times, and “text Priya for the baraat” do not belong inside the RSVP form. Put travel notes on the invitation next to the venue. Multi-venue directions are a ₹79 add-on and a travel kit (airport, station, shuttle) is ₹49 if you need those blocks. The RSVP add-on does not include them.
A photo wall is separate from replies. Guests can share pictures on the invitation. The base publish includes 20 photo wall slots. It will not tell you how many people are eating. Do not use uploaded photos as a headcount.
If a function is cancelled or moved, change the page first, then tell people who already replied yes. Their dashboard row is still a yes to the old plan until you speak to them. The link update does not rewrite their answer.
Keep gift and RSVP language apart. A form that asks for attendance and a UPI id in the same breath feels like a bill. Attendance is for the kitchen. Anything else can live further down the page.
Close the list
On the deadline, freeze the number you will send to the caterer and add a small buffer your hall already expects. New yeses after that are phone calls, not silent form submissions you might miss during the haldi.
Tell the family chat the number once: reception count, wedding lunch count, kids. Invite corrections until a time you name. After that, the person at the door handles walk-ins. An open form on the morning of the wedding collects replies nobody will read.
After the events, the dashboard is still your record of who said they would come. It is not a public guest list unless you choose to show names. Treat phone numbers as host data. The privacy policy describes how Maṅgalya stores RSVP answers.
Turn on RSVP in the editor when you want replies on the page, publish the link, and use the dashboard as the only list. One owner, one link, one number for the caterer.
If a household replies twice, keep the later row and call them once to confirm the headcount. Do not average the two numbers. Write the confirmed count in a note you trust, then stop editing the caterer sheet from memory. The dashboard is there so the wedding week has one list instead of a thread of voice notes.