How to collect wedding RSVPs online (without losing your mind)

Most Indian weddings are not one event. A haldi on Thursday, mehendi that night, the ceremony on Friday morning and a reception on Saturday is an ordinary plan, and each function has its own guest list. That is why RSVPs get messy: you are not collecting one answer per family, you are collecting one answer per family per function. This guide covers why the usual approaches break, what a good RSVP setup looks like, and how to run one from start to finish.

Why does group-chat RSVP go wrong?

Replies arrive as messages: "we're coming", "4 of us for the reception", "not sure about mehendi". Someone has to read every message, decide who said what about which function, and keep a running count somewhere else. A few things go wrong almost every time:

• Replies get buried. A late answer sits under fifty congratulations and is never counted.
• Answers are vague. "We'll be there" rarely says which function, or how many people.
• The count drifts. Each update to the spreadsheet is manual, so the number you give the caterer is a guess.
• Families see functions they are not invited to. One message to everyone tells everyone about every event, which is awkward when some functions are only for close family.

What are the options?

There are three common ways to collect replies, and each has a place:

• A group chat. Easy to start and familiar to every relative. Hard to count, and every family sees every message.
• An online form. Collects answers in one place, which is a real improvement. You still have to sort answers by function, match them to the right family and add up head counts yourself, and every family sees the same form.
• A wedding RSVP tool. Ties each reply to a guest and a function, so the counts come straight from the replies and each family sees only what applies to them.

For a single-event wedding, a form can be enough. The more functions you have, the more a tool that understands functions saves you.

What should you ask in an RSVP?

Keep it short. Every extra question lowers the number of replies. The essentials:

1. Are you coming, for each function? Ask per function, not once for the whole wedding.
2. How many people? Families often bring parents, children or a grandparent, and the caterer needs the real number.
3. Any dietary needs? Vegetarian, Jain, no onion and garlic, allergies: the kitchen needs to know in advance.
4. A message for the couple (optional). Many guests like to send a blessing with their reply.

Avoid asking for things you will not use. Every question should change a plan.

When should you send it, and when should replies close?

Send RSVP links once your functions, dates and venues are fixed. Changing a venue after families have replied creates confusion. Set a reply date that leaves time for your caterer's final count, which is often a week or two before the wedding, and follow up personally with families who have not answered a few days before that date. A short, warm message from the couple or a parent works far better than a public reminder in a group.

How do you handle elders and guests who are not online?

Some relatives will never open a link, and that is fine. A younger family member can reply on their behalf from the same link, because the reply belongs to the family, not to one phone. For guests who prefer a call, add their answer yourself so the count remains complete.

How do you handle extra guests?

Decide before you send links. If a family is invited as four people, put four as their party size, and let the reply say how many are actually coming. If someone asks to bring an extra guest, settle it with them directly and update the party size, rather than leaving it open for everyone.

How do you set up RSVPs in Mangalyam?

1. Add your functions. Haldi, mehendi, ceremony, reception: each with its date, time, venue and map link.
2. Add your guests. Give each guest a side and a party size.
3. Invite each guest to their functions. Not every family is invited to every function.
4. Share each family's link. It shows only the functions they are invited to. They reply from the link, with no app and no account, and can add how many are coming, any dietary needs and a message.
5. Watch the replies come in. The RSVP view shows who is coming to each function and the head counts.

What do you do with the replies?

Replies are only useful if they turn into plans. Once most families have answered:

• Give each caterer the count for their function, not one number for the whole wedding.
• Share dietary needs with the kitchen for each function.
• Plan seating and transport from who is actually coming, function by function.
• Follow up with families who have not replied, using the list of guests still waiting for each function.

What if a family does not reply?

You can see who has not replied for each function and follow up with just those families. Most late replies come after one personal message, so a short list of names to call is worth more than a reminder to everyone.

Can you change the plan after sending links?

Yes, but tell families. If a function moves or a venue changes, update it before families plan their travel, and send a short message to the families invited to that function so nobody turns up at the old place.

A simple RSVP checklist

• Functions, dates and venues are fixed.
• Every guest has a side and a party size.
• Each guest is invited only to the functions they are part of.
• The RSVP asks per function, the head count, dietary needs and an optional message.
• A reply date is set, a week or two before the caterer needs the count.
• Families who have not replied get a personal follow-up.
• Final counts go to each caterer per function.

See RSVP in Mangalyam for the details, or create your account and set up your functions today. Mangalyam is free for couples.