I Was the Guy Who Said "Just Make a WhatsApp Group" — Here's What Happened
I am the kind of person who solves problems by creating groups.
Need to coordinate the bachelor trip? Group. Deciding on the restaurant for the farewell? Group. Figuring out who is bringing what to the office potluck? Group.
So when my fiancée sat me down three months before the wedding and said, "We need to figure out how we're going to manage the invitations and RSVPs," I had what I thought was a perfectly reasonable suggestion.
"Just make a WhatsApp group," I said.
She looked at me for a long moment. The kind of look that contains an entire argument that she has decided, in the interest of time, not to have.
"Okay," she said. "Let's try it your way."
This is the story of what happened next.
The Group Solution
We had four functions: Mehendi, Sangeet, the main ceremony, and the reception. I created four groups. Named them carefully. Added everyone.
Within twenty minutes, I had already made my first mistake.
I had added my father's college friend — a 68-year-old retired professor — to the Sangeet group. He responded, in all caps, asking what the group was for and why there was so much noise in his phone. Then he left the group. Then he called my father to ask what was happening to his son's wedding that it required so many groups.
My father called me. I muted all four groups.
Week One
The groups were alive with activity, which sounds positive until you understand what the activity actually was.
People were congratulating each other. People were sending good morning messages with flowers and sunrises. Someone — I never found out who — posted a GIF of a dancing cartoon elephant that got 47 reactions. Cousins who had not spoken in three years were having a warm reunion in the Sangeet group.
What nobody was doing was RSVP-ing.
I posted the invitation card. I posted the date. I posted the venue. I posted a clear message: "Please reply here if you're coming, so we can confirm numbers."
Twelve people sent heart emojis. One person asked what the parking situation was. Nobody actually said yes or no.
The Spreadsheet Phase
My fiancée, who had been watching this unfold with the patience of someone who had predicted it exactly, suggested we track RSVPs in a spreadsheet.
I agreed immediately, partly because I had no better idea and partly because I was starting to understand the look she had given me three months ago.
We built the spreadsheet together. Columns for name, function (all four), confirmed yes, confirmed no, pending, dietary restrictions, travelling from outstation. It was a good spreadsheet. Clean. Colour-coded. Absolutely impossible to keep updated.
Every time someone confirmed, one of us had to open the laptop, find the sheet, scroll to the right row, and update four cells. Every time someone's plans changed — and plans changed constantly, because this is India and three months is a long time — we had to find them again and update.
My fiancée was doing most of the updating, because she remembered to do it. I was doing most of the "okay okay I'll do it later" and then not doing it.
By week three, the spreadsheet had 340 rows and was approximately 60% accurate. We knew this because when we compared notes on who was coming to the Mehendi, we had three different numbers: her count, my count, and the spreadsheet's count. None of them matched.
The Follow-Up Phase
Six weeks before the wedding, we started following up individually. This is how you spend your evenings when you are getting married: calling your relatives to ask if they are coming to your own wedding.
Some calls were easy. "Yes, of course we're coming, why are you even asking?" (Because you have not confirmed in three months, Mausi.)
Some calls were complicated. "We are coming, but we are not sure about the Sangeet, it depends on whether [elderly relative] can travel." (Understandable. Mark as pending. Call again in two weeks.)
Some calls were very complicated. "We already told [other family member] we were coming. Did she not pass it on?" (She did not. Nobody passes anything on. That is the entire problem.)
I made 47 follow-up calls over two weekends. My fiancée made 61. We are both introverts. This was not a good time.
What We Actually Needed
Here is what I understood by the end of this process, sitting with 340 half-confirmed guests and a spreadsheet that had become its own source of anxiety:
Wedding RSVP tracking is not a communication problem. It is a systems problem.
WhatsApp groups are excellent for communication — warm, instant, human. They are terrible for tracking structured information like attendance confirmations across multiple functions. When the confirmation is buried under 200 messages of congratulations and elephant GIFs, it is not a confirmation. It is a wish.
What we needed was a wedding guest list app that did the following things: let us invite guests per function (not everyone to everything), let guests confirm per function with one tap, showed us live counts for each function, and let us send reminders only to the people who had not responded — not to the whole group again.
We found Lumhe a month before the wedding. Late enough that we could not migrate everything, but early enough to use it for the reception — our largest function, with 280 confirmed guests and 60 still pending.
The difference was immediate. Guests received a clean link. They tapped it, saw the invitation with all the reception details, and confirmed. No group noise. No buried messages. No spreadsheet. I could see the confirmation count going up in real time, from my phone, while simultaneously doing fifteen other wedding-related things.
The final reception headcount was off by four people. Four. After three months of spreadsheet chaos, we had a number we could actually give to the caterer with confidence.
What I Would Do Differently
If I were starting over — and I sometimes think about this, in the way you think about things you cannot change but have learned from — this is what I would do:
Upload the invitation once. Whatever format — image, video, PDF — create it on whatever tool you like and upload it to Lumhe. Add all your functions: Mehendi, Sangeet, ceremony, reception. Each with its date, time, and venue.
Share a link, not a group. Every guest gets the same clean link. They open it, see the invitation, and confirm which functions they are attending. Simple. Dignified. No group drama.
Track RSVPs per function from day one. Not in a spreadsheet. Not in your head. In a system that updates in real time and tells you, at any moment, exactly how many people have confirmed for each event.
Send reminders to non-responders only. Not another message to the whole group. A gentle nudge to the specific people who have not replied yet. Targeted. Efficient. Not annoying to the 200 people who already confirmed.
I would have saved 47 phone calls, three weeks of spreadsheet management, and one very tense conversation where I finally admitted that the WhatsApp group solution had not been my finest moment.
She did not say "I told you so." This is why I am marrying her.
If you are the person in your relationship who is about to say "just make a WhatsApp group" — this post is for you. Upload your invitation to Lumhe, add your functions, share the link, and track wedding RSVPs in real time from day one.
Your future self will thank you. Your fiancée definitely will.
Lumhe lets you upload any invitation — image, video, PDF, or text — add your event details and functions, share via link on any platform, and track RSVPs in real time. For weddings, engagements, and every occasion worth organising properly.
