I built PartyCall after watching my family spend 3 days calling 200 relatives for a function — here's what I learned about a problem hiding
I want to tell you about a problem that affects hundreds of millions of people in India — and probably more people globally than you'd expect — that nobody has properly solved yet.
The problem
Every time someone organises an event in India — a wedding, a birthday, a corporate annual day, a family function — the guest communication process looks roughly like this:
Someone creates a WhatsApp group. Half the members have it muted. The host starts calling people individually to confirm. This takes days. They track responses in Excel or a notebook. The spreadsheet is wrong within 24 hours. Someone RSVPs yes and then shows up with three extra people. Someone who said no shows up anyway. Leadership asks for a headcount the day before and the number is a guess.
This isn't a niche problem. It's the default experience for anyone self-organising an event above 50 guests in India. And the people dealing with it aren't event planners — they're regular people: a parent planning a wedding, an HR manager handling the company annual day, a small business owner organising a customer meet. People who are doing this on the side of their actual life and job.
Why we built PartyCall
I watched a family member spend three days on the phone calling relatives before a function. Missed calls, callbacks, people who "confirmed" but couldn't be reached again, a spreadsheet that was already out of date. She was exhausted before the event even started.
It struck me as a problem that technology had completely skipped over. Event management tools exist — but they're built for professional event planners with dedicated budgets, not for people organising events themselves without an agency.
We built PartyCall to fill that gap.
What it does
The core flow is simple:
You upload your guest list (CSV, Excel, or add manually)
PartyCall automatically makes voice calls to every guest in their preferred language
Guests confirm by simply saying "Yes" or "No"
You get a live RSVP dashboard — confirmed, declined, no answer, needs follow-up
WhatsApp invites with event details and location links go out alongside the calls
Guests who don't pick up get automatically retried
Multi-language support (English, Telugu, Hindi) because in India, your guest list includes everyone from your 25-year-old cousin to your 75-year-old grandparent, and they're not all equally comfortable in English.
Where we are
We just launched. Web app is live at partycall.ai, iOS app is on the App Store. We're at the very beginning — finding our first users, learning what resonates, and figuring out where we've gotten things wrong.
I'm sharing this here specifically because Indie Hackers has always been where I've found the most honest feedback. Not "looks cool!" feedback — the kind that actually tells you whether you're solving a real problem or just a problem you've convinced yourself is real.
What I'd love from this community
If you've ever organised a large event yourself — in India or anywhere else — I'd genuinely love to know: what was your RSVP process like? Was it as painful as what I described, or did you find something that actually worked?
And if you're the kind of person who likes trying early-stage products and giving direct feedback — please try PartyCall and tell me where it breaks, what's confusing, and what you'd do differently.
Free to try at
🌐 https://partycall.ai
📱 iOS: https://apps.apple.com/us/app/partycallai/id6762263163
Most people would've reached for another WhatsApp blast here. Voice calls in the guest's own language with automatic retries is a different bet, and probably the right one — the 75-year-old relative who never opens the group will still pick up a phone. Getting that multilingual routing right sounds like the hard part.
I like that you started with a real pain point instead of leading with AI. The workflow definitely sounds familiar for large family events.
One thing I'd focus on is finding a very specific wedge instead of "everyone organizing events." For example, weddings in India alone seem like a huge market where hosts are already willing to spend money to reduce stress. If you can become the default RSVP tool for one high-value use case first, it'll probably be much easier to expand into corporate events and other gatherings later.
This is a very real problem, especially in India — the “RSVP chaos” you described is spot on. The voice-call + multilingual angle is a strong differentiator, especially for non-tech-savvy guests.
If I were you, I’d double down on a couple of things:
-Make the confirmation flow feel extremely trustworthy (people need to believe the count is accurate)
-Add “+guest” handling early — that’s a huge real-world edge case
Biggest question I’d have as a user: what makes this better than just a WhatsApp bot + form combo?
Overall though, this feels like a genuinely painful, overlooked problem — you’re not forcing a use case here. Definitely worth testing with real event hosts ASAP.
I like that you're solving the coordination problem rather than just digitizing invitations.
Most people don't struggle with sending invites—they struggle with knowing who's actually coming without spending days following up. Turning RSVP collection into something that updates itself feels like a much bigger improvement than another event management tool.