inyeet

How to track wedding RSVPs without 50 phone calls

A bride and groom laughing with family under a marigold wedding mandap

The notebook, the Google Sheet, and three WhatsApp groups

Last December, my cousin Riya sat at my dining table with her fiancé Karan and a fat spiral notebook. Haldi, sangeet, shaadi, reception — four days, four separate headcounts. Riya's side of the guest list alone ran past 180 names: friends, relatives from three cities, and a set of elders who have never once replied to a WhatsApp message but will happily call at 10:30 pm to ask "beta, khana vegetarian hoga na?"

Karan had a Google Sheet with colour codes. Riya had a WhatsApp group for the cousins, another for office colleagues, and a third her mother had created without telling her. The caterer wanted buffet counts by Thursday. The decorator needed chair counts by Tuesday. And nobody — literally nobody — knew whether the Sharma family from Lucknow was coming with four people or seven.

Riya looked at me and said, "Tu toh tech mein hai, kuch kar na."

I'm Hrishikesh, and I've been that person at every family function, trying to make sense of RSVPs. I eventually built Inyeet because the usual systems kept breaking in very Indian conditions. But before I get to that, let's be honest about those systems and where each one breaks.

The four classic RSVP systems (and where each breaks)

1. The notebook and the phone-call spiral

You write names in a ruled diary — neatly at first, then scratches and arrows after the third call with a distant uncle.

What works: it feels personal. Elders love it. You can note the odd request ("beta, thoda achar bhej dena return gift mein").

Where it breaks: there is exactly one notebook, and your partner, your parents and the decorator all need live information. You end up WhatsApping photos of torn pages, and the caterer still calls at midnight. For a multi-function shaadi, a notebook becomes a bottleneck after the first twenty guests.

2. The Google Sheet shared with the family

One spreadsheet, four tabs, colour-coded columns: "Shaadi – yes", "Sangeet – maybe". Then someone sorts a single column alphabetically and quietly destroys the whole thing.

What works: it's shareable and free.

Where it breaks: half the relatives won't open a sheet link, and the other half type in the wrong cell. Headcounts drift — a family writes "2" and arrives as 5, and you find out halfway through the paneer tikka. Very few wedding guests will open a spreadsheet on their phone, hunt for the right tab, and type "yes".

3. WhatsApp group polls

You make a group and post a poll: "Sangeet — yes / no / maybe?" It looks like the modern solution.

What works: everyone sees it, and replies are quick.

Where it breaks: polls don't capture headcounts. A "yes" from Gupta uncle could mean one person or six. Votes are public inside the group, so the neighbour who spots your uncle's "no" will discuss it at the next puja. And a wedding with four functions needs a poll per function, per group — chaos by design.

4. Calling everyone personally

What works: you get undeniable confirmation. Nobody ignores a call from the host.

Where it breaks: it's time you don't have two weeks before the wedding — fifty calls at ten minutes each is a full working day. And guests change their minds: Tuesday's "yes" becomes Friday's "maybe" once chacha realises a flight ticket is involved. By the third round of follow-up calls, even your favourite mausi stops picking up.

What actually works for Indian families

After watching Riya's notebook drown, we took a different approach: keep the warmth of WhatsApp, remove the broadcast mess, and give the host one screen that shows exactly who is coming to which function and how many plates to order.

The method works with any tool that gives you private invite links and a live dashboard. I'll describe the flow we built into our app, because it's what I know deeply — and it's what solved Riya's exact problem.

Step 1: upload the card you already have

You don't need a new design. Whatever you got from the print shop, Canva or your designer friend — upload it, and it becomes the invite page your guests see. (We don't design cards. If you don't have one yet, get it made first and come back.)

Step 2: add guests the human way

Type or paste names and WhatsApp numbers. For a family, add the one person whose number you actually have — Sharma uncle — and let him answer for everyone under his roof. You don't need to chase his children's numbers.

Step 3: send personal invite links from your own WhatsApp

This fixes the dignity problem. Every guest gets a personal message from your WhatsApp — not a business API broadcast — with your card, a short note, and a private link. The link opens a page where they respond for each function: no app install, no login, no account. And if the link gets forwarded to a cousin who wasn't on the list, they hit a friendly identity check, so your headcounts stay honest.

Step 4: watch the dashboard, not your phone

The dashboard updates live: opened / yes / no / maybe / pending, with family headcounts per function. At a glance you know the Sharmas said yes to haldi with three people, maybe to sangeet, no to reception. That number flows straight into your plate count and your Thursday call with the caterer. The full flow is on our how it works page.

The moment Riya's father saw the dashboard, he didn't say "nice app." He said, "Ab Panditji ko bata sakte hain ki shaadi mein kitne log baithenge." That's the real win.

And the elders who only confirm by phone? Take those calls happily — those five are the calls worth making. The tool's job is to eliminate the other forty-five.

The follow-up timeline that saves your wedding week

Even with clean invite links, some guests stay pending. That's not rudeness — it's an aunt waiting on her son's leave approval, a friend pricing train tickets. The trick is to nudge gently without becoming a reminder pest.

Here's the rhythm that has worked in our beta events — not a law, just a pattern that keeps the mood light and the numbers honest.

Days before Action Who gets it What you send
T-14 First check-in Guests who haven't opened the link A warm one-to-one "did the invite reach you?" — concern, not pressure.
T-7 Caterer-deadline nudge Everyone still "maybe" or "pending" "We're giving final numbers this week — ek quick yes/no bata do?"
T-3 Headcount confirmation Confirmed guests with incomplete counts A short ask for exact numbers per function, with their invite link.
T-1 Last call, no guilt Anyone still "maybe" "Totally fine if you can't make it — just tell us for the food."

Shift the days to match your own caterer and pandit deadlines. The one rule: never send a blanket broadcast. Every nudge goes one-to-one and points to the guest's own invite link, so it feels like a family check-in, not a marketing drip.

Nudge scripts you can copy tonight

Here are three I've used myself and pushed onto cousins. Short, warm, nothing like a form letter. Paste the guest's private link where marked. (Our app fills each guest's link in automatically; with any other method, paste it yourself.)

1. For the guest who hasn't opened the invite (T-14)

English:

Hi Uncle, just checking — did the wedding invite come through on WhatsApp? Sometimes links act funny, so if you haven't seen it, tell me and I'll resend. No rush — just wanted to be sure you have the details.

Hinglish:

Namaste Uncle, bas check kar raha tha ki aapko shaadi ka invite mila ya nahi. Kabhi kabhi link theek se nahi khulta — batao toh dobara bhej doon. Koi jaldi nahi, bas confirm karna tha.

2. For the "maybe" guest one week out (T-7)

Hinglish:

Hi [Name], caterer uncle kal count maang rahe hain aur humara math kharab ho raha hai 😅 Ek baar yes/no bata do, taaki hum plates ka jugaad kar sakein. Plan clear nahi hai toh 'maybe' hi rehne do, koi pressure nahi — bas rough idea de do: [link]

That smiley does real work. I've watched it defuse pressure instantly.

3. For the confirmed guest who hasn't given a headcount (T-3)

English:

Hey, so glad you're coming for the sangeet and reception! Quick help — we're finalising chairs and dinner plates. Could you tap your invite link once more and confirm how many of the family are joining each function? Ten seconds, promise. Thank youuu!

The extra "u" in "thank youuu" is not a typo. It makes the message sound like a real person under pressure — which you are.

When not to use an app (including ours)

A tool should never be more work than the problem it solves.

If your guest list is under ten people — a small ceremony and a lunch at home — you don't need an RSVP tracker. Call them. The warmth of a direct conversation beats any dashboard.

If everyone on the list lives within two kilometres, knock on doors over a weekend and you'll have your counts.

Where a tool like Inyeet genuinely fits is the sprawling multi-function wedding: two families, fifty to three hundred guests, elders who confirm by phone while their kids open the link, and a caterer saying "final count, Thursday 6 pm." There, the dashboard saves more than time — nobody wants to begin married life with a fight over who forgot to update the sangeet sheet.

FAQ

Do guests need to download an app or create an account?

No. They tap the link, see your card, tap yes/no/maybe for each function, and enter how many family members are coming. It works in any phone browser. Only the host uses the app — it's on Android, currently in private beta, and the early access list is open.

My card is already printed — can I still use it?

Yes. Upload the card you already have and we put it in front of your guests with the RSVP buttons. We deliberately don't do card design — you've already paid someone talented for that.

Can my parents or fiancé track RSVPs too?

The dashboard lives with the host who set up the event, which is a real limitation today. What families in our beta do is make it an evening ritual: open the dashboard together, argue about the Chawlas, make decisions. Surprisingly effective — and weirdly calming in the middle of the chaos.

The real win is headspace

When Riya stopped calling and let the dashboard do the math, she didn't become a super-efficient event manager. She got an hour back every evening — an hour she spent talking to Karan about the honeymoon instead of the Chawla family's headcount. That's what a good RSVP system buys you: the bandwidth to be a host, not a project manager.

If you're in that spiral right now, the features page shows exactly what the live dashboard tracks. I've also written about why guests don't RSVP — the psychology behind the silence — and about planning a guest list for family functions, so the "we forgot the neighbour's nephew" moment never happens to you.

Weddings are loud, unpredictable and deeply human. Your RSVP system should quietly handle the numbers so you can handle the hugs.

Hrishikesh Roy

Founder, Inyeet

Building tools that make Indian celebrations easier to host. Every guide here comes from real events — ours and our beta hosts'.

Put this into practice at your next event.

Get early access