Lemonvite Now Works Anywhere in the World
My cousin Dani moved to Lisbon two years ago. Last spring I built her a birthday invite on Lemonvite and typed her Portuguese number into the guest list. I published it feeling pretty pleased with myself. She never got it. She found out about her own surprise dinner three days later, from her sister. The text just went nowhere, because back then we only sent to numbers in the US and Canada.
That gap is closed. As of today, Lemonvite can send invitations worldwide. If your guest is in the US or Canada, they get a text message, the same as always. If they are anywhere else, they get the same invitation over WhatsApp instead. You don't pick the channel. You type in the number with its country code, and we route it for you.
Why a phone number used to be a wall
For years, the honest answer to "can my friend in Mexico City get this?" was no. SMS sounds like it should work the same everywhere, but it doesn't. International texting is a mess of carrier rules and per-country registration, and when it fails it fails silently. So we did the responsible thing and only promised what we could actually deliver: texts to the US and Canada.
The problem is that a guest list rarely respects a border. You have a college roommate in Berlin, or the friend from your study-abroad year who you still want at the wedding. Leaving them on email-only felt like a downgrade, and asking everyone for a backup contact method is exactly the kind of friction a good digital invitation app is supposed to remove.
And most people outside North America already know this in their bones: WhatsApp is how the rest of the world texts. In a lot of countries it's the default inbox, the place where your mom messages you about dinner and your landlord messages you about rent. So instead of fighting international SMS, we send the invitation where those guests actually are.
How it works: SMS here, WhatsApp everywhere else
There is nothing to configure. The rule is simple:
- A US or Canada number gets a standard SMS.
- Any other country's number gets the same invitation delivered through WhatsApp.
We read the country off the number, so the part that matters is the country code. A number saved as a local 9-digit string with no +351 or +44 in front can't be routed correctly, because we can't tell where it lives. Save your guests' numbers in full international format and the routing happens on its own.
Everything downstream stays identical. The guest taps the link and RSVPs from your invitation page in one tap, with no account and no app to install. A WhatsApp guest and an SMS guest show up in the same place on your guest list, and your headcount counts them the same way. As far as your guest can tell, they just got an invite from you, and the delivery channel is something they never have to think about.
The same goes for every message after the first one. When you change the time or post an update, that message takes the same road: SMS for the North American numbers, WhatsApp for the rest. You set up the event once and stop thinking about who is where.
This is the same philosophy behind why we lean on direct, personal invites instead of a social feed: the invitation should land in the one inbox a person actually reads, wherever in the world that inbox happens to be.
What happens when a number doesn't work
Here is the caveat, because I would rather tell you up front than have you discover it the hard way like I did with Dani.
We cannot tell you in advance whether a specific number will receive its message. The only way to actually know is to send and see what comes back. A number might be mistyped, or it might belong to someone who has never set up WhatsApp, and we can't see either case until we try the delivery.
So you publish, and we send. If a message can't be delivered, that guest gets flagged Undeliverable on your list once the send has genuinely failed. The flag is a record of a real bounce, the same way an email bounces back to you, and it appears only after a delivery actually fails. When you see it, the fix is easy. Add an email for that guest, or grab their personal link from their row in the guest list and send it to them yourself through whatever app you both use.
If a guest already has an email on file, you are covered automatically, because email is the backstop when a number can't be reached. That is one more reason to add both a phone number and an email when you have them, especially for the guests who matter most.
A few practical notes
The one thing worth fussing over is the full international number, country code and all. That's the single most common reason an international invite doesn't route the way you expect, so it's worth a second look before you publish.
Everything else just works the way it already did. WhatsApp guests RSVP from the same beautifully designed page you built, with one tap and no login, and they can change their answer later from the same link. Email still carries the invitation for anyone with no phone or a number that bounces, so adding both contact methods only helps.
And there's no second system to learn. You won't find a "WhatsApp mode" to switch on or a separate list to maintain. You build one event and add your guests the way you always have, and we handle who gets a text and who gets a WhatsApp message behind the scenes.
None of this changes the part of Lemonvite people actually fall in love with: describing the event you want and watching Lemonvite's design engine turn it into a custom invitation in a couple of minutes. It just means the people you send it to can now live anywhere. A destination wedding, or a small dinner party where one of your eight favorite people happens to be calling in from another continent: the guest list is no longer limited by a map.
So go ahead and invite the cousin in Lisbon. I finally did, and this time she got it. If you want to put it to work, start an event on Lemonvite and add a number from anywhere you like.