Planning an Event When Nobody Uses the Same App
Twelve guests, four different messaging habits, and one dinner nobody can plan in a single group chat. The advice to 'just make a group' quietly assumes everyone already made the same app choice you did, and for most real families and friend groups, they haven't.
Quick answer
A group chat can only reach the people already inside it, and most real groups of any size aren't all on one app. Pew Research found that only 32% of U.S. adults use WhatsApp, so building a plan entirely inside it already excludes a majority.
Standards like RCS and the GSMA's Universal Profile exist specifically because phone-to-phone messaging between different systems wasn't reliable on its own. None of that reaches someone using only email or a phone call, though, which is a gap no single messaging channel closes.
A shared link sidesteps the whole issue, because it isn't a conversation tied to any one app. The same address opens for the WhatsApp cousins, the email-only aunt, and the grandparent who needs it read aloud and typed in by someone else.
Twelve people, four different apps, one dinner
Look at any real friend group and count the messaging apps in play. There's WhatsApp for most of them, iMessage for the ones with iPhones who never installed anything else, and at least one person who just uses regular texts.
Somebody's aunt only checks email. Somebody's cousin insists on Signal.
None of that is unusual. It's just what a normal group of adults actually looks like once you stop assuming everyone made the same choice you did.
The group chat solution assumes a group that doesn't exist
The standard advice for planning anything is "make a group chat." That advice quietly assumes everyone you're inviting is reachable inside the same app.
For a lot of groups that's just false. Pew Research Center's most recent survey on American social media use found that 32% of U.S. adults report using WhatsApp, which means a majority of American adults don't, and that's before you count the ones who use it but wouldn't want a group with fourteen strangers-of-friends in it.
Make a WhatsApp group for a family reunion and you've already lost the aunt who only does email. Make it in iMessage and you've locked out anyone with an Android phone, because a green bubble in a group thread behaves differently and drops features the moment one non-Apple device joins.
What actually breaks when the group isn't one group
The obvious failure is that some people never see the plan at all. The less obvious failure is worse: the plan exists in two or three separate, disconnected versions.
The WhatsApp side plans dinner at seven. The iMessage side, informed later by someone relaying details, hears seven thirty.
Nobody lied. Two different conversations about the same event drifted apart the moment they stopped being the same conversation, because there was never one place both sides were actually reading.
A group chat can only reach the people already inside it. An event can't afford to be that picky about who shows up.
The retyping tax nobody accounts for
Somebody always ends up as the relay. They're in both the WhatsApp thread and the family email chain, so they retype the plan from one into the other, by hand, every time something changes.
That's a real cost, paid quietly, usually by the same person every time. It's also the exact point where details drift: a time gets fat-fingered, an address gets abbreviated differently, a headcount gets forgotten.
The relay isn't being careless. They're doing, by hand, the job of keeping two disconnected systems in sync, which is a genuinely hard job even for software built specifically to do it.
| Method | Requires an account | Requires the same app as the host | Reachable by someone using only SMS |
|---|---|---|---|
| WhatsApp group | Yes | Yes | No |
| iMessage group thread | Yes (Apple device) | Mostly | Partially, with feature loss |
| Email chain | An email address | No | No |
| A shared event link | No | No | Yes |
Why "just use SMS then" doesn't actually solve it
Plain text messages reach the widest possible audience, which is exactly why people fall back on them for the one holdout who won't install anything. The trouble is what a group text loses along the way.
Apple's own description of iOS 18 explains that "when messaging contacts who do not have an Apple device, the Messages app now supports RCS for richer media and more reliable group messaging compared to SMS and MMS," which is Apple admitting, in its own release notes, that plain SMS group messaging was never fully reliable to begin with. RCS helps, but it depends on both phones and both carriers supporting it properly.
The specification behind that improvement, the GSMA's RCS Universal Profile, describes its own goal as delivering "a consistent and advanced messaging experience" specifically because messaging between different operators and devices wasn't consistent before it existed. That's a whole industry standard built just to patch over app fragmentation at the network level.
None of that reaches your aunt who only checks email, or the friend who's kept the same flip-phone habits since 2009 despite the smartphone in her pocket. A standard fixing phone-to-phone messaging doesn't touch anyone who isn't messaging at all.
A family reunion, told from four separate directions
Picture a reunion with eighteen people across three generations. The cousins are all in a WhatsApp group. The parents' generation mostly uses a family email thread that's older than some of the cousins.
One grandparent doesn't use messaging apps at all and gets everything by phone call from a designated relative. A cousin's new partner, invited for the first time, uses neither WhatsApp nor that email address, just regular texts.
The venue changes two weeks before the date, because the original restaurant loses its liquor licence. That update goes out in the WhatsApp group instantly, gets forwarded to the email thread a day later by whoever remembers, reaches the grandparent by phone call sometime after that, and never quite reaches the new partner at all.
Four separate versions of "did you hear the venue changed" traveling through four completely different channels. Nobody owns the mistake, because nobody was ever in a position to see all four channels at once.
What a link does that a group chat structurally cannot
A group chat's whole value is that everyone in it shares the same ongoing conversation. That's also its limit: it only reaches the people who are already members of it.
A link doesn't have that limit, because it isn't a conversation at all. It's an address, and an address works the same whether it arrives by WhatsApp, by text, by email, or read aloud over the phone and typed in by hand.
Send the same link to the WhatsApp cousins, paste it into the family email thread, and read it out to the grandparent who'll ask someone to type it in. All three land on the identical page, showing the identical, current details, with nobody relaying anything by memory.
Why this isn't really an app problem
It's tempting to blame the fragmentation itself, as though the fix is getting everyone onto one app. That's not realistic, and it isn't really the point.
People choose messaging apps for reasons that have nothing to do with your event: family habit, a phone their employer issued, a friend group that settled on Discord years ago for reasons nobody remembers. Asking eighteen people to switch apps for one reunion is a bigger favour than asking them to click a link.
The actual problem was never which app people use. It's that the plan itself was only ever stored inside one of those apps, instead of somewhere none of them needed to own.
"Can't I just make a group chat and ask everyone to join?"
You can ask, and some people will. Reliably, some percentage won't, either because they don't want another app, don't trust it, or genuinely can't be bothered for one event.
Every person who doesn't join is now invisible to the plan, and has to be manually updated by somebody else every time something changes. That's the retyping tax again, just moved earlier in the process.
"What about a shared calendar invite instead?"
Calendar invites carry real structure, the kind formally defined by the IETF's RFC 5545, which is exactly why they work so well between colleagues who all use compatible calendar software. They also arrive looking and feeling like a meeting request, which is an odd tone for a birthday dinner.
They also assume the recipient's calendar app can read the file properly, which isn't guaranteed the moment someone's on an unusual client or checking email on a work device that blocks attachments. For friends and family, that's a real enough failure rate to notice.
"Isn't this just a case for using email for everything?"
Email reaches almost everyone, including people with no interest in messaging apps at all. It's also the slowest channel for anything that changes more than once, because nobody reliably reads a follow-up email the same day it lands.
The venue-change story above is really an email-lag story as much as an app-fragmentation story. Whatever channel you pick as the single one, it will always be missing somebody, which is the actual argument for a link that doesn't require picking a channel at all.
The apps people actually mean when they say "just message me"
"Just message me" sounds like one instruction. In practice it resolves to a different app for nearly everyone who says it, because it means whichever app they personally already have open.
Lay out what a handful of common platforms actually require before someone can even see your event, and the differences stop being minor.
| Channel | Assumes the recipient has | Fails silently for |
|---|---|---|
| "I'll WhatsApp you" | The app installed and an active number | Anyone who's never installed it |
| "I'll text you" | A phone number and cell signal | Nobody, mostly, but loses formatting and RSVPs |
| "I'll email you" | An email address they actually check | Anyone who treats email as a spam folder |
| "I'll send you the link" | Any device with a browser | Almost nobody, which is the point |
Notice the pattern in that third column. Every named app or channel has some group of people it quietly drops, and everyone assumes it's somebody else's problem until it's their aunt.
The moment a mixed group actually notices the gap
Most of the time nobody clocks any of this, because the group happens to skew toward one app anyway and the gap stays invisible. It surfaces the instant somebody genuinely outside that skew gets added late.
A new partner joining a long-running friend group. A colleague's plus-one who's never met anyone else coming. An elderly relative added to a reunion nobody planned around them for.
That person becomes a test case for every assumption baked into the plan. If the whole thing lives inside one app's group thread, they either join an app they didn't want, or they rely on someone else relaying details forever.
What actually needs to be true for a mixed group
Strip away the specific apps and the requirement is short. Whoever gets the news, however they get it, should end up looking at the exact same details as everyone else.
- Put the current facts in one place before you send anything. Decide where the plan actually lives, separate from any one app's group thread.
- Send that address through whatever channel reaches each person. WhatsApp for the cousins, email for the parents, a read-aloud phone call for the grandparent who needs it typed in by someone else.
- Let every channel point at the same place instead of repeating the details. A relayed link stays correct. A relayed paragraph, retyped from memory, usually doesn't.
- Update the one place, not each channel separately. When the venue changes, everyone who opens their link again sees it, without needing a second round of calls and forwarded emails.
The organiser who ends up fluent in four apps
Every mixed group produces one person who quietly becomes the translation layer. They're in the WhatsApp thread, they check the family email, they take the grandparent's phone calls, and they're the one who remembers to loop in the cousin's new partner.
That role is invisible until it isn't. The moment that person goes on holiday, or simply forgets one relay, the version of the plan that reaches each channel stops matching the others.
It's not a fair job to hand one person by accident, which is usually how it happens. Nobody sits down and decides who the relay will be, it's just whoever happens to be in the most channels at once.
Why a link doesn't need a translation layer at all
A link removes that role entirely, rather than making it easier. There's nothing to translate, because the same address means the same thing in every channel it travels through.
The grandparent's phone call still needs someone to read the address aloud and help type it in, which is real work and worth naming honestly. What it doesn't need is that same person remembering to also call back every time a detail changes, because the link they already have keeps showing the current version on its own.
That's a smaller job than being a full-time relay, and it's a job that ends the first time it's done, rather than repeating every time something moves.
Where the mismatch actually shows up on the day
It's rarely dramatic. It's a person quietly standing at the wrong entrance, or asking a question that was answered days ago in a thread they were never part of.
Nobody's angry about it, usually. It's just a small tax, paid over and over, by whoever happens to be on the wrong side of whichever app the plan happened to live in that week.
Ask any organiser who's run the same annual event for a few years running and they'll usually name this exact pattern without needing to think about it. It's rarely the big things that go wrong, it's a slow trickle of people quietly missing details that everyone else considered obvious.
Where Ontaym fits
Ontaym exists specifically for the group that isn't on one app. An event lives at a single address that opens the same way regardless of whether it arrives through WhatsApp, a text message, an email, or read aloud over the phone.
Nobody needs an account to see the current plan or to answer whether they're coming. The link does the same job for the cousin on Signal, the aunt who only checks email, and the grandparent whose phone gets dictated to.
That's a narrow fix on purpose. It doesn't ask anyone to change which app they already use, only gives the plan itself somewhere to live that none of those apps had to own.
What this looks like from the guest's side
Put yourself in the shoes of the guest who's on the wrong app for once. You've heard about the event secondhand, from a relative rather than the actual host, and you have no easy way to double check anything.
Asking a follow-up question means going back through whoever relayed it, then waiting for them to check the original group on your behalf. That's a real chain of favours for something as simple as confirming a start time.
Most people just show up with whatever secondhand version they were given, reasonably, because chasing it down feels disproportionate. That's the actual cost of app fragmentation, paid quietly by the person furthest from the original conversation.
The question worth asking before the next group event
Before defaulting to "let's make a group chat," ask whether everyone you're inviting is actually reachable inside one app. For most real groups, past a certain size, the honest answer is no.
If it's no, the group chat was never going to be the plan's real home, no matter how good it is at holding the conversation. It was just the loudest option in the room.
Giving the plan its own address, separate from any single app, isn't a workaround for that problem. It's just building the thing the group chat was never actually built to be.
Nobody needs to change which app they already use for that to work. The plan just needs somewhere to live that doesn't belong to any single one of them.
Frequently asked questions
How do you plan one event when guests use different messaging apps?
The reliable approach is to give the plan a single address that isn't tied to any one app, then send that link through whatever channel reaches each person, whether that's WhatsApp, email, plain text or a phone call. Everyone ends up looking at the same current details regardless of how the link reached them.
What percentage of people actually use WhatsApp?
Pew Research Center's most recent survey found that 32% of U.S. adults report using WhatsApp, which means a majority of American adults don't. Assuming a WhatsApp group will reach an entire family or friend group is a bet that fails for most of the room.
Why doesn't a group chat work for a mixed group?
A group chat only reaches people who are already members of it, so anyone using a different app, or no app at all, is invisible to the plan by default. Somebody usually ends up manually relaying updates to them, which is slow and prone to drift.
Does RCS solve the problem of messaging across different phones?
It helps phone-to-phone messaging between an iPhone and an Android device work more reliably than plain SMS, which is why Apple added it in iOS 18. It doesn't reach anyone who isn't using messaging apps at all, such as someone who only checks email.
Isn't a calendar invite a good fix for a mixed group?
Calendar invites carry real structure, defined by the IETF's RFC 5545, and work well between people whose calendar apps are compatible. They can fail quietly for anyone on an unusual client, and they read more like a meeting request than an invitation to a family dinner.
Why not just use email since almost everyone has an address?
Email does reach nearly everyone, but it's slow for anything that changes more than once, since people don't reliably read a follow-up the same day it arrives. A change can sit unread in an inbox for days while a WhatsApp group already knows.
What actually breaks when a plan is announced across separate channels?
The channels drift apart rather than staying in sync, because each one only gets updated when somebody remembers to relay the change to it by hand. A time or venue announced in one channel can simply never reach someone relying on a different one.
Does everyone need to download something for a shared link to work?
No, which is the main advantage over asking a whole group to join one app. The link opens in a browser regardless of which messaging app, or non-app channel, carried it there.
Give your next plan one address instead of one more thread.
Plan it with Ontaym