Blunt version: the reason twelve people missed the mehndi isn't that you invited them badly. It's that you sent a JPEG into a group with 94 members at 11 PM.
This is the sending half of our complete mehndi invitation message guide.
Why image-only invitations fail on WhatsApp
WhatsApp compresses images aggressively. Your beautifully designed mehndi card, viewed on a five-year-old Android in a group chat, becomes a blurry rectangle where the venue is illegible.
Then there's the practical stuff:
- You can't copy an address out of a picture. Guests have to retype it into Maps, so they don't. They ask you instead.
- Images fall out of chat history. Some phones auto-delete media to save space. Two weeks later the invite is a grey box saying "media not found."
- You can't search an image. A guest looking for the time scrolls through 300 messages, gives up, and messages you.
- Screenshots of screenshots. Somebody forwards a screenshot of your image. Quality halves each time.
Send the image if you want — it looks lovely. But send the text underneath it. Every single time.
The three-message method
This is the whole system, and it takes about twenty minutes total.
Message 1 — the group announcement (2–3 weeks out)
Posted once into the family group and once into the friends group, in different tones. This one sets the date in people's heads. Nobody RSVPs off it, and that's fine — it isn't supposed to make them RSVP.
Our celebrations begin! [Name]'s mehndi is on [Day, Date] at [Time], [Venue]. Full details below — please save the date.
Message 2 — the individual invite (7–10 days out)
Sent one-to-one to anyone whose presence you actually care about. Two lines. Personal. This is the message that produces attendance.
Really want you at my mehndi — [Day, Date], [Time], [Venue]. Let me know if you can make it?
The difference in response rate between a group post and an individual message isn't marginal. People reply to messages addressed to them. Everyone knows this and almost nobody does it, because sending forty individual messages feels like a chore. It's a twenty-minute chore that decides your headcount.
Message 3 — the 48-hour reminder
Short. With the map pin attached as a location, not as text.
Mehndi is day after — [Time] onwards at [Venue]. Pin below. See you there!
Attach the pin using the paperclip → Location → Send this location. A pin opens directly in Maps. An address typed into a message does not.
Link, image, or PDF — which format to send
| Format | Readable on old phones | Copy-paste address | Survives forwarding | Tracks who's coming |
|---|---|---|---|---|
| Plain text message | Yes | Yes | Yes | No |
| Image / JPEG card | Poorly | No | Degrades | No |
| Needs a viewer | Yes | Yes | No | |
| Digital invite link | Yes | Yes | Yes | Yes |
| Video invite | Yes | No | Large file, often skipped | No |
The honest recommendation: text plus a link. The text carries the details for anyone who won't tap. The link carries the design, the map and the RSVP for everyone who will.
A digital mehndi invite from Eventic generates that link with the timings and location built in, and the responses collect in one list — which is the difference between telling your caterer "about 120?" and telling them 118.
Group message or individual message?
Both, and in that order. Here's the split that works:
Group message is for: setting the date, creating excitement, reaching people you can't message individually without it being weird (distant cousins, the extended family group).
Individual message is for: anyone travelling in, anyone whose absence you'd actually notice, elders (a group forward to an elderly relative reads as careless), and anyone you need a real yes or no from.
One caveat on family groups: forwarding the same invite into six different groups means some relatives receive it four times. Mildly annoying, mostly harmless — but if there's a family sensitivity about who was told first, order matters more than you'd think. Elders first. Always.
Timing: when to send each message
| Guest type | First message | Individual invite | Reminder |
|---|---|---|---|
| Out-of-town guests | 3–4 weeks before | 2 weeks before | 3 days before |
| Local family | 2 weeks before | 7–10 days before | 48 hours before |
| Friends | 2 weeks before | 5–7 days before | 24–48 hours before |
| Office / acquaintances | 10 days before | Not needed | Not needed |
Send in the evening, between 7 and 9 PM. Messages sent at 11 PM get buried by morning, and messages sent at 10 AM on a weekday get opened at work and forgotten. This isn't science, it's just what consistently works.
Getting an actual headcount
The part everybody underestimates. You cannot count "coming!!" replies scattered across four group chats and arrive at a real number.
What people actually do: message everyone individually two days before asking if they're coming, then add up the yeses on a piece of paper, then add ten percent for the people who said yes and meant maybe, then give the caterer that number and hope.
What works better: put the RSVP where the invite is. If your invite is a link, tracking responses in one place means the list builds itself as people tap, and you're not reconstructing it from memory at midnight.
Either way — get a number 48 hours before the function, not 12. Caterers can adjust for 20 extra guests with two days' notice. They cannot do it with two hours'.
Small things that go wrong
- Wrong date in one version. You'll send the invite in three tones. Copy-paste the date line identically into all three rather than retyping it. Retyping is how "14th" becomes "4th."
- Venue name without the locality. There are four banquet halls called Rajwada. Add the area.
- No dress code mentioned. Guests will ask. Add one line: "bright colours, avoid black."
- Forgetting the groom's side. If it's a joint mehndi, coordinate who's inviting whom before either family sends anything.
- Sending only in Hindi, or only in English. Match the script to the recipient — there are ready Hindi and Hinglish versions here if you need both.
And if the mehndi is one of several functions, don't send five separate messages on five separate days. Send the combined schedule once and a short reminder per function — the wording for that is in our combined haldi and mehndi invitation guide.
Send it to yourself first. Open it on your own phone, in the group, the way a guest would. Every invitation disaster in history could have been prevented by ninety seconds of doing that.
People Also Asked
Explore common questions related to this blog.
Send the wording as text, attach the invite image or link below it, and send the venue as a location pin in a separate message. Post it in the group once, then message key guests individually, then remind everyone 48 hours before.
Completely normal now, including for elders. For very senior relatives, a phone call followed by the WhatsApp message is the version that avoids any hurt feelings — the call is the invitation, the message is the reference.
Only alongside text. Video invites are large files, often skipped on limited data, and impossible to copy an address from. Lovely as an addition, risky as the only version.
Three. Announcement, individual invite, and a 48-hour reminder. Four or more and people start muting you, which defeats the purpose entirely.
