I once watched a groom send his wedding invite to 340 people in one evening. A 28 MB video, fired into a hastily created WhatsApp group. By morning: forty "Congratulations!!" messages, three complaints about mobile data, one uncle who left the group loudly, and exactly zero recorded RSVPs. The caterer got a guess, not a headcount.
WhatsApp is how Indian wedding invitations travel now. That part is settled. What is not settled, judging by every family group I am in, is how to do it well: what format to send, to whom, in what order, with what message, and how to actually collect the yes/no/how-many that the whole exercise exists for.
This is the playbook I give friends. It takes one evening to execute and saves you three weeks of tallying replies by hand.
Send a link, not a file
You have four options: an image (JPEG of the card), a PDF, a video invite, or a link to a wedding website. The first three all share the same flaw: they are dead ends. A guest sees them, says "lovely", and moves on. Nothing is captured. When the venue changes, and something always changes, the old file keeps circulating forever.
A link is alive. It opens a page with every event, a map, the dress code, and an RSVP button that writes into a dashboard you can read. Update the page and every copy of the link updates with it. The forwarded-five-times problem becomes a feature instead of a bug.
If your family loves the video invite, keep it, but put it on the website and share the link. The video plays there without eating anyone's data allowance, and the RSVP button sits right under it.
Fix the preview before you send anything
When a link lands in WhatsApp, the little preview card decides whether it gets tapped. Names, date, and a warm image: tap. Grey box with a bare URL: ignored, or worse, treated as a suspicious link by every relative over fifty.
Before mass-sending, message the link to yourself and look at the preview. It should show the couple's names, the wedding date, and a clean image at WhatsApp's small square size. If your wedding website tool does not let you control this preview, that is a real limitation, not a cosmetic one.
Test on both a phone and WhatsApp Web. Then open the link with wifi off. If it loads in under three seconds on mobile data, you are ready.
Broadcast lists, not groups
Do not create a group to send your invite. A group shares every guest's phone number with every other guest, invites seventy reply-all congratulations, and guarantees that one uncle asks a question at 6 AM that notifies everyone. Guests quietly resent being added.
Use broadcast lists instead. A broadcast sends individually, each guest receives a personal-looking message, replies come only to you, and nobody sees anyone else's number. One catch people forget: broadcasts only deliver to people who have saved your number, so send from the phone the family actually uses, or split the list between bride's side and groom's side phones.
Segment into three or four lists: close family, friends, parents' circle, colleagues. Not for logistics, for tone, which is the next point.
Write three versions of the message
The same link needs different clothes for different people. For elders, formal and from the family: "With the blessings of our parents, we would be honoured by your presence at Sahil and Rina's wedding. Details and RSVP here: [link]". For friends: "We're getting married! Everything you need is here, please RSVP so we can feed you properly: [link]". For colleagues, short and warm.
Never send a bare link with no message. That is what spam looks like, and it is what forwards look like. Two sentences of context transform the exact same link into an invitation.
For the twenty most important people, grandparents, family elders, closest friends, send a personal message or make a phone call first, and let the link follow. The link is logistics. The call is the invitation.
Time the send, then run exactly two reminders
Send the main wave four to six weeks before the wedding, on a weekend morning when people actually read messages. Earlier than that and people say "months away" and forget; later and outstation guests cannot plan travel.
Then two reminders, no more. At two weeks: a gentle nudge to everyone who has not RSVP'd, "We're finalising the caterer's count this week, would love to know if you can make it: [link]". At four or five days: final logistics to confirmed guests only, venue pin, parking note, timing changes.
This is where the dashboard earns its keep. Because RSVPs are recorded against names, you can see exactly who has not responded and nudge only them, instead of blasting all 300 people a third time. The couples who skip this end up doing headcount archaeology through chat scrollback at midnight.
Keep a lane for the offline guests
Every list has fifteen or twenty people who will not tap a link: elderly relatives, the family priest, one aunt who believes links are how phones get hacked. Do not fight it. Print a small run of cards for them, or deputise one cousin as the phone-RSVP desk whose number appears on the invite.
Their responses go into the same dashboard, typed in manually. One headcount, one source of truth, and the caterer gets a number instead of a shrug.
Final Thoughts
The short version: send a link, not a file; fix the preview first; use broadcast lists, never a group; dress the link in a real message with three tones; send once and remind twice, targeting only the silent; and keep a human lane for the offline few.
ShaadiOra websites are built for exactly this flow: WhatsApp-ready link previews, sub-three-second mobile loads, per-event RSVP into a live dashboard, and a free Imperial Heritage template to start with. Build yours in an evening at shaadiora.com/builder.
Frequently Asked Questions
Is it better to send a wedding invitation as a link or a PDF on WhatsApp?+
A link. PDFs and images cannot collect RSVPs, cannot be updated after forwarding, and give WhatsApp no proper preview. A wedding website link shows a rich preview, opens instantly, updates everywhere when details change, and records every RSVP in one dashboard.
Should I use a WhatsApp group or broadcast list for wedding invitations?+
A broadcast list. Groups expose every guest's number to strangers and drown everyone in reply-all messages. Broadcasts deliver individually and replies come only to you. Note that broadcasts only reach contacts who have saved your number, so send from a number guests know.
When should I send my wedding invitation on WhatsApp?+
Four to six weeks before the wedding for the main send, ideally on a weekend morning. Follow with a reminder at two weeks for non-responders only, and a final logistics message four to five days out for confirmed guests. Destination weddings should add an earlier save-the-date.
What message should I write with a wedding invitation link?+
Two or three sentences matched to the audience: formal and family-voiced for elders, warm and casual for friends, brief for colleagues. Never send a bare link, context is what separates an invitation from a forward. Personal calls still matter for the closest twenty people.
How do I track who has not RSVP'd on WhatsApp?+
Manually, you cannot at any real scale, which is the core problem with image and PDF invites. A wedding website records each RSVP against a name, so you can filter for non-responders and nudge only them instead of re-blasting the entire list.
Kabir Mehta
Head of Product
Curating high-aesthetic Indian wedding styling guidelines, tech-enabled RSVP dashboards, and digital invitation designs to make your special wedding day seamless and memorable.
