How to Plan a Whole Event Without Sharing Contact Information
You know her from a running club's Discord, not from real life, and now the group wants a proper trail day. Turning that into a plan usually means a group chat, and a group chat means eleven strangers trading numbers. It doesn't have to.
Quick answer
A whole event, invites, RSVPs, updates and day-of coordination, can run on one shared page instead of a group chat, so nobody in the group has to exchange phone numbers to take part.
This matters most for online communities meeting in person, hobby meetups with strangers, and dating-adjacent group hangouts, where guests know each other by username or by vibe rather than by contact details.
The event's actual requirements, a time, a place, a way to answer, never included a phone number in the first place. That requirement came from the group chat, not from the event.
You met her in a running club's Discord, not at a party
Three months of Saturday morning runs, a shared group chat, and you still do not have her number. You have her username, her pace, and the fact that she always brings the good electrolyte tablets.
Now the club wants to do a proper trail day, further out, with a car share and a pub afterward. Somebody has to turn "let's do a big one" into an actual plan, and the obvious move is to start a group chat.
That is also the moment eleven people who know each other as usernames become eleven people who know each other's phone numbers. Nobody asked for that trade.
The event and the address book got welded together
An invitation used to answer one question: what is happening, and how do I say yes. Somewhere along the way it started answering a second question nobody asked it to: who else is coming, down to their number and their profile photo.
Those are genuinely separate pieces of information. You can know the trail starts at nine without knowing the phone number of the person who suggested it, the same way you can accept a wedding invite without being handed the seating chart in advance.
Knowing you are both going is not the same as knowing how to reach each other.
A group chat cannot make that distinction, because a group chat is a room, and a room shows you who is standing in it. The event details and the guest list arrive as one bundle, whether or not anyone wanted the second half.
Three scenarios where that bundle is actually a problem
This is not an abstract privacy worry. It is a specific, recurring shape, and it shows up in the same three situations again and again.
The online community meetup. A hobby forum, a Discord server, a subreddit for people who collect the same odd thing.
You know these people by handle and by opinion, and that has worked fine for a year. The moment someone proposes an in-person meetup, the group either has to trade numbers or has to trust one organiser to hold everyone's contact details in a group they did not choose.
The hobby meetup with strangers. A pottery class, a five-a-side game, a language exchange.
Half the room found it through a listing rather than a friend. General safety guidance for meeting people from online spaces, including from Get Safe Online's advice on making online friends the safe way, is consistently to go slowly on personal details until you actually know someone.
A shared group chat skips that entirely and hands out numbers on day one, to everyone, before a single person has decided they actually want to be found.
The dating-adjacent group hangout. A friend-of-a-friend situates six people at a bowling night specifically because it is lower stakes than a one-on-one date.
Adding everyone to a chat to sort logistics quietly undoes the entire point. Now the group has each other's numbers regardless of how the evening goes, which is exactly the outcome the low-stakes format was supposed to avoid.
What actually has to travel, and what doesn't
Strip an event down to what a guest genuinely needs and the list is short. Where, when, what to bring, and a way to say yes or no.
None of that requires a phone number. Not the organiser's, not the other guests'.
| What's genuinely needed | Why it's needed | What a group chat also demands |
|---|---|---|
| A way to reach this one guest | So updates land and questions get answered | A phone number, visible to every other member too |
| A yes, no, or maybe | So the organiser has a real headcount | A reaction or reply buried in general chatter |
| The current time and place | Plans move, guests need the latest version | Whichever message someone happens to have scrolled to |
| A record of who is actually going | For the organiser, and nobody else | A member list every guest can see about every other guest |
Look at that last column and the pattern is obvious. Every extra thing a group chat demands is a side effect of how chats are built, not a requirement of the event itself.
The organiser becomes the risk, not just the guests
There is a second cost that rarely gets named, and it lands on whoever agrees to run the group chat. The moment they add eleven people, they are personally holding eleven phone numbers on behalf of a community they do not own.
If one of those eleven turns out to be someone others would rather not have their number, the organiser cannot undo that. The number is already saved on ten other phones, and there is no recall button for a phone book.
Compare that to what an event page asks the organiser to hold.
| Responsibility | Group chat add | Shared event page |
|---|---|---|
| Collecting everyone's number to invite them | Required before anything else can happen | Never required |
| Who can see whose number | Every member sees every other member's | Nobody's number is collected to attend |
| What happens if someone drops out badly | Their number stays on ten phones regardless | They simply stop being on the guest list |
| Undoing a mistaken add | Not really possible once numbers are shared | Removing access to a link is immediate |
| Liability if a guest complains about exposure | Falls on whoever ran the group | Nobody's contact details were ever exposed |
None of that is the organiser's fault, exactly. They picked the tool that was already open, the same as everyone always does.
It is still their name on the group, and their judgment on the line if a guest later feels uneasy about who has their number now. A page removes that particular kind of responsibility from a volunteer who never signed up to be a data custodian for a hobby club.
What happens when the community spans three apps
Online communities rarely live on one platform anyway. The forum posts on the website, the fast chatter happens on Discord, and half the older members only really check a group on Signal or WhatsApp because that is what they had installed first.
Trying to run one event through a single group chat then forces a second, uglier choice: which platform gets to be the "real" one, and who gets left out because they were never in that particular room. A link sidesteps the whole argument, because it opens the same way regardless of which app carried it there.
Post the same link in the Discord announcements channel, the WhatsApp splinter group and the email list nobody reads anymore, and every one of those audiences lands on the identical page. No one has to join anything they were not already in to find out where Saturday happens.
The middle piece: a page instead of a room
The fix is not complicated, and it is not new. Instead of adding people to a room, you give the event one address, a page, and you point people at it.
The page holds what is actually true right now: the time, the place, who has answered. Anyone with the link can see it and respond, without seeing a member list, and without anyone collecting their number to invite them.
Some platforms already build a version of this into their own RSVP flow. Partiful's own help pages confirm that guests can RSVP to an event through the browser without installing the app, which is exactly the shape that matters here: answer without joining anything permanent.
WhatsApp has moved a little in the same direction for its own Communities feature. Enabling phone number privacy there means, according to reporting on the rollout, that a member's number stays visible only to admins and people who already saved them as a contact, rather than to the whole room.
That is a genuine improvement, and it is telling that the fix was to hide the number rather than to stop collecting it. A dedicated event page skips the question by never asking for the number at all.
How this actually runs, start to finish
Picture the trail day again, run the page way instead of the group-chat way.
- The organiser creates one event page with the trailhead, the time, and the pub booking, and shares the link in the existing running club chat.
- Each runner answers on the page, privately, without their name appearing to the other ten as a clickable contact.
- The organiser sees the real headcount, sorts the car share by who is driving, and posts that back to the same page.
- Updates go to the page, not to a new thread, so a changed meeting point reaches everyone who checks, instead of getting buried under trail chatter.
- After the run, the page's job is done. Nobody is left holding ten phone numbers they collected for one Saturday.
The running club chat never had to change. It kept doing what it is actually good at, which is talking about running.
What day-of coordination looks like without a group
The morning of the event is where this gets tested properly. Someone is running late, the trailhead parking is full, and the meeting point needs to shift fifty metres down the road.
In a group chat, that update is one more message competing with everything else being said that morning. On a shared page, it is one edit, and anyone who opens the link sees the current answer rather than a chronological pile they have to sort through.
This matters more, not less, for the community and hobby scenarios above. A late change among eleven trail runners who all know each other is annoying. The same late change among six people who met on a hobby forum a month ago, some of whom cannot easily identify each other's faces yet, is the difference between everyone arriving and someone standing alone at the wrong end of a car park.
The two objections worth answering directly
"Isn't a link just as easy to lose as a message?"
A message scrolls away under whatever gets said next. A page does not, because it is not competing for space in a feed, it is sitting at one fixed address.
The organiser can repost the same link as many times as needed without repeating the details themselves. Every repost points at the current version, not a copy that might already be stale.
"People will just add each other anyway once they meet"
Probably, and that is fine. The difference is who decides and when.
Meeting someone at the trailhead and swapping numbers because you got on is a choice both people made in person. Being added to a group by a third party before either of you has said a word is not the same thing, even though the end state looks similar on a phone screen.
Where this sits next to the rest of the privacy question
This piece has stayed narrow on purpose, on running a whole event through a link rather than a room. The broader argument for treating invitations and conversations as different jobs entirely is made in full in how event invitations can protect everyone's privacy, and the specific mechanics of what adding someone to a group actually requires are covered in how to invite people without exposing phone numbers.
There is also a useful habit sitting underneath all of this, which is refusing to let a conversation double as your record of who is coming. A conversation and an event object are not the same thing, and a hobby meetup with strangers is exactly where that confusion costs the most.
The hesitation people feel right before tapping "add" is not a small thing either. Why adding someone to a group chat is always slightly awkward is worth reading if you have ever paused mid-add and could not say exactly why.
The awkward middle: knowing a face but not a name
There is a specific social discomfort this solves that is easy to miss until you have lived it. You have run alongside someone for three Saturdays, you know their laugh, and you genuinely do not know their surname.
Asking for their number at that point feels bigger than it should, because you are not really asking for a number. You are asking to move from "person I see at running club" to "person who can text me," and that is a real step, not an administrative formality.
A shared event page lets both of you skip that step entirely while still doing something together. You RSVP, they RSVP, the trail day happens, and neither of you had to decide anything about the other beyond showing up.
If a friendship grows out of that, the number gets exchanged the ordinary way, in person, when it actually means something. Nobody has to force the decision early just because the group needed a headcount.
What this looks like for the organiser who hates admin
Some people avoid organising group events for years for exactly this reason. Not because planning is hard, but because being the one who holds everyone's number, fields the "wait what time again" messages, and gets blamed when the plan changes twice is genuinely unpleasant work.
A page does not eliminate the work of deciding where to go and when. It removes the specific, draining part where you are simultaneously the venue researcher, the group's unofficial address book and the person everyone messages individually because the group thread moved too fast to follow.
People who have quietly stopped organising anything for their community are not lazy. They correctly identified that the job came with costs nobody warned them about, and opted out rather than pay them again.
When a group chat is still the right call
None of this means group chats are wrong. A tight friend group planning their fifth trip together should absolutely just use the chat they already have, because everyone in it already has everyone else's number and nobody minds.
The line is roughly this: if everyone invited already knows everyone else, the room costs nothing extra. The moment even one guest is new, or would rather not be findable by strangers indefinitely, a page beats a room.
Online communities meeting in person for the first time almost always sit on the wrong side of that line, whether anyone has said so out loud or not.
A short checklist before you build the next group
Before adding anyone to a chat for your community's next meetup, run through a short list of questions. It takes less time than the argument about which pub to pick.
- Does everyone on this list already know everyone else, or are some of them strangers to each other?
- Would each person be comfortable being findable by the rest indefinitely, not just for one event?
- Is there a plus-one, a new member, or someone from a different part of the community mixed in?
- Does the event actually need a room, or does it just need a headcount and a place to check the details?
If the honest answers are "mostly strangers," "no," and "yes," reach for a page rather than a room. If everyone already has everyone else's number and nobody minds, the chat you already have is still the fastest option, and there is no need to overthink it.
Where Ontaym fits
Ontaym is built for exactly this middle case, which is the honest commercial reason this article exists. An event gets one page with the details and a way to answer, shareable in whatever chat the group already uses.
Guests reply without an account and without their number going anywhere near anyone else on the list. The organiser gets a real headcount, and everyone else gets to keep being usernames to each other until they decide, on their own terms, not to be.
The one thing to remember
An event and a group chat are not the same object, and treating them as one is what quietly forces everybody to trade numbers just to find out where Saturday's run starts. Give the plan its own address instead.
Let the community chat keep doing what it is good at, and let the page hold what is actually true. Nobody has to become findable by ten strangers just to go for a run.
Frequently asked questions
Can you really run an entire event without anyone sharing a phone number?
Yes. A shared event page can hold the invite, collect RSVPs, carry updates and coordinate the day itself, all through one link, without collecting anyone's number to do it. The only thing a phone number was ever solving was getting people into a group chat room, which the page replaces.
Isn't a group chat just easier for a hobby meetup?
It is easier for the organiser to set up, which is exactly why it's the default. It is not easier for a guest who would rather not be findable by five strangers indefinitely just because they showed up to one pottery class.
What about online communities like Discord servers or forums?
Those groups often work well as usernames and opinions for months before anyone meets in person. The moment a meetup gets planned, a shared event page keeps that arrangement intact, so members stay usernames to each other unless they choose otherwise on the day.
Does this apply to dating-adjacent group hangouts too?
It applies especially well there. Group hangouts are often chosen specifically because they're lower stakes than a one-on-one date, and adding everyone to a chat to sort logistics quietly cancels that out by giving everyone each other's number regardless of how the evening goes.
What happens to day-of changes, like a moved meeting point?
The organiser edits the page instead of posting a new message. Anyone who opens the link sees the current details, rather than having to work out which of several messages in a thread is the one that's still true.
Do guests need to download an app or make an account?
No, that's the point. Platforms built around this pattern, including Partiful's own help documentation, confirm guests can respond through a browser without installing anything, which matters for a group where half the people barely know each other yet.
Is a group chat ever still the right choice?
Yes, when everyone invited already knows everyone else and nobody minds being findable by the group. A close friend group planning its fifth trip together loses nothing by using the chat it already has.
Won't people just swap numbers anyway once they meet?
Often, and that's fine. The difference is that it becomes their choice, made in person after actually meeting, rather than a decision made for them by whoever set up the group chat before anyone arrived.
Give your next plan one address instead of one more thread.
Plan it with Ontaym