How Telegram Groups Handle Event Coordination

Telegram Event Coordination August 22, 2026 15 min read By the Ontaym Editorial Team

Telegram hands an organiser more coordination machinery than any rival: pins that beat a mute, forum topics, visible-vote polls, granular admin rights, scheduled messages and a full bot platform. Configured properly, it is the best group chat there is. Here is what each feature actually solves, and the exact point where it stops.

The most configurable room in messaging

A running club decides to move its Sunday sessions off a spreadsheet and into Telegram. Within a week the group has topics, a pinned message, a permissions policy and a poll with visible votes.

It is, genuinely, a well run room. Nobody is confused about where to post, the announcements are legible, and the admin can mute a spammer in two taps.

Then somebody asks how many people are coming on Sunday, and the whole apparatus goes quiet.

That is the shape of this article. Telegram gives an organiser more machinery than any competitor, and most of it is worth using properly.

So this is a straight capability review. Feature by feature, what does it actually solve, and precisely where does it stop?

No complaining. If you are configuring a group this week, you should finish this with a better group.

What is actually in the box

Start with the size of the room, because it sets everything else. Telegram's own FAQ on groups and channels states that groups can have up to 200,000 members each.

The API documentation on channel and group types fills in the detail. A basic group tops out at 200 members, upgrades to a supergroup beyond that, and gigagroups exist for broadcast-style communities that outgrow even 200,000.

Channels are the other half of the story, and the same documentation says they can have an unlimited number of subscribers. If you are still choosing between the two, we argued that one out in the case for channels versus groups for event announcements.

On top of the room sits the coordination layer proper. Pins, topics, polls, quizzes, admin roles, granular permissions, mentions, scheduled messages and a full bot platform.

Each of those is a real tool built by people who thought hard about large groups. Each of them also has an edge, and the edges are all in roughly the same place.

Every feature here organises the conversation beautifully. Not one of them holds a fact.

Pinned messages: the single best move you can make

If you do one thing to a badly organised group, pin something. The FAQ describes it plainly: a pinned message displays at the top of the chat screen, and all members get a notification even if they muted ordinary messages from the group.

Read that second half again, because it is the underrated part. A pin is not just a shelf, it is a delivery mechanism that beats a mute.

That makes it the closest thing Telegram has to an announcement everyone will actually see. For a one-off change of venue on the morning of the event, it is close to perfect.

You can also pin more than one thing. The API reference for pinned messages confirms that Telegram allows pinning multiple messages on top of a chat, with a silent flag for pinning without the notification, and a method to unpin everything at once.

Where a pin stops

A pin is a photograph of a moment. It shows you what somebody typed, not what is currently true.

Nothing on the pin tells you how old it is at a glance, whether it has been superseded, or which parts changed since the last version. If the time moved on Thursday and the pin still says eight, the pin is now confidently wrong to everyone who reads it.

The multi-pin feature makes this sharper rather than softer. Two pins about the same event is exactly the failure mode where half the group reads one and half reads the other.

A pin also has no idea who is coming. It is a message that has been promoted, and a message cannot hold a guest list.

The practical rule is one pin per event, edited rather than replaced, and never a second one. We walked through the mechanics of that in how to organise event information inside a Telegram group.

Topics: separate rooms inside one room

Topics are the feature people underuse most. The FAQ describes them as splitting group discussions into topics, each with its own chat history, shared media and notification settings, like classic forums.

That last phrase is doing real work. A member can mute the general chat and keep notifications on for the one topic they care about, which is a genuine solution to the loudest problem in large groups.

Telegram's announcement of Topics in groups is explicit that the feature is intended specifically for large groups, and that admins enable it in Group Settings and control who may create and manage topics in Permissions.

The forum API documentation adds the useful details. Every forum has a non-deletable General topic, topics can be closed so no further messages can be sent to them, and only users with the manage topics right can create, modify or delete them.

That closing behaviour is quietly excellent for events. Run the planning in a topic, close the topic when the plan is settled, and the argument cannot reopen itself under the answer.

Where topics stop

Topics solve the lanes problem, which is real. A venue debate no longer lands forty messages away from the venue it is about.

What they do not do is change what a lane contains. A topic is still an ordered list of messages, so the current start time is still the most recent message that mentioned a start time.

They also create a discovery cost. A newcomer now has to work out which of eleven topics holds the thing they need, and "it is in the Sunday Runs topic, scroll up a bit" is not an answer to "what time".

And a topic per event does not scale for a group that runs something weekly. You either accumulate dead topics or you reuse one, at which point last month's details sit directly above this month's.

Polls and quizzes: the best in messaging, and still a poll

Telegram polls are the strongest in any mainstream chat app, and it is not particularly close. The Polls 2.0 announcement introduced visible votes, so everyone in the group can see who voted for what, plus multiple answers and a quiz mode with a correct option.

The parameter list in the Bot API reference for sending polls is where the real depth shows. It is worth reading even if you never touch a bot, because those options exist in the app too.

Two of those defaults deserve calling out, because most organisers never change them. Anonymous is on unless you turn it off, and multiple answers is off unless you turn it on.

So the default Telegram poll is a single-choice anonymous vote. That is the least useful configuration for planning anything, and it is what you get by tapping through.

Where polls stop

The revoting default is the interesting one. Regular polls do let people change their answer, which sounds like it fixes the problem that attendance keeps moving.

It does not, because changing a vote is silent. The number quietly ticks from thirty one to thirty, and unless the organiser was staring at the poll at that moment, nobody learns anything.

Compare that with what a real answer mechanism does. Somebody drops out, the record changes, and the change is visible as a change rather than as a slightly different total.

There is a deeper problem underneath the mechanics, which is that a poll answers the question it asked. "Which Saturday suits you?" is a statement about a calendar, and it costs nothing, which is exactly why so many people answer it.

We took that distinction apart properly in why Telegram polls do not give you actual attendance. The short version is that a vote is a preference and an RSVP is a promise.

Use polls for the decision. Stop using them the moment the decision is made.

Admins and permissions: you can genuinely govern a room

This is where Telegram pulls furthest ahead, and it gets less attention than it deserves. The FAQ describes appointing administrators who can mass-delete messages, control membership and pin important messages, with admin privileges defined with granular precision.

"Granular" is not marketing. The admin rights reference lists them separately, including change info, delete messages, ban users, invite users, pin messages, add admins, manage topics, manage calls, anonymous posting and manage ranks.

The same page lists the restrictions you can apply to ordinary members, which is an equally long list. Sending messages, media, stickers, polls, reactions, link previews, inviting users, pinning and managing topics are all separately controllable.

For an event group, three of these matter more than the rest.

• Pin messages. Restrict it to admins, or you will end up with four pins and an argument.
• Send polls. Leave it on for a small group, restrict it for a large one, because competing polls about the same date are genuinely worse than none.
• Manage topics. Give it to two people. Topic sprawl is the most common way a well organised forum group becomes unusable.

Where permissions stop

Permissions govern who may speak and what they may post. They say nothing about who is coming.

There is no permission called "may attend", no cap you can set at forty places, and no right that distinguishes a person on the guest list from a person who joined the group last March. Membership and invitation are the same fact in Telegram, and for anything with a capacity that is a problem.

It is worth naming the odd consequence. You can build a room where only three people are allowed to speak and 200,000 people are allowed to attend, and the second half of that sentence is not a setting you chose.

Mentions: precise, and only in one direction

Mentions are Telegram's targeting tool. The API documentation on mentions describes how incoming messages that mention you carry a mentioned flag, how unread mentions are counted per chat, and how clients offer a button to step back through your mention history.

It also documents mentioning people who have no public username at all, through a name-based mention entity. That is the feature that makes Telegram workable for groups where half the members never set a username.

In practice this is how organisers chase the last four people. Tag them by name, they get a counted, navigable notification, and they are far more likely to reply than to a broadcast.

Where mentions stop

A mention is a nudge, not a record. It creates an obligation on the reader and stores nothing when they fulfil it.

It also does not scale in the slightest. Chasing four people by name is fine, chasing forty is a part-time job, and the documentation describes no mention-all mechanism to escape into.

Which is arguably correct design. A group of 200,000 with an everyone-tag would be intolerable.

The real cost is that mentions turn the organiser into the index. Every unanswered question routes through one human who remembers who has not replied, which is exactly the job a record is supposed to take off them.

Scheduled messages: the closest Telegram gets to a calendar

This one is genuinely underused for events. Telegram's announcement of scheduled messages and reminders explains that you hold the send button in any chat and choose Schedule Message to send at a specified time in the future.

The same post describes scheduling inside Saved Messages, which turns a scheduled post into a personal reminder. And it notes that when a scheduled message or reminder is sent, you get a special notification marked with a calendar emoji.

For an organiser this is a real tool. Write the reminder on Monday while you still care, schedule it for Saturday morning, and stop carrying it around in your head for five days.

Pair it with a pin and you have a reasonable rhythm. One pin holding the details, one scheduled message on the morning saying it is today.

Where scheduled messages stop

A scheduled message fires whatever happens. It has no relationship to the event it is about, so if the plan moves on Friday, Saturday's reminder still cheerfully announces the old time.

That is the failure that hurts, because a scheduled reminder carries more authority than an ordinary message. It arrives at exactly the right moment, which makes people trust its contents.

It is also a message, so it goes to everyone in the room rather than to the people who said they were coming. There is no version of this that only reminds the eleven people who answered yes.

Bots: the escape hatch, and what it costs

Every experienced Telegram organiser reaches this point and says: use a bot. They are right that the platform is capable.

The FAQ describes bots as small programs that run inside Telegram, made by outside developers using the Bot API, able to open mini apps with their own interface. A bot really can take names, cap a list at forty, and message everyone who signed up.

Two documented details matter if you are choosing one. The bot features documentation states that privacy mode is enabled by default for all bots, so a bot added normally sees commands aimed at it rather than the whole conversation.

That default is a good thing for your group's privacy, and it means a signup bot needs people to interact with it deliberately. Turning privacy mode off, or making the bot an admin, hands it the entire group conversation instead.

Where bots stop

A bot fixes the interface and leaves the structure alone. The answers now exist, and they exist inside one bot's private database, on hosting somebody is personally paying for.

The FAQ's own phrasing is the honest warning: bots are made by outside developers. That is the platform's strength and the reason your attendance list has a single point of failure with a name and a day job.

Three limits follow from where a bot sits, and none of them are the developer's fault.

• It stops at the edge of Telegram. The people in your club who are on WhatsApp or on nothing at all cannot answer it.
• Nothing else can read it. The list does not open in a calendar, a spreadsheet or the venue's booking system.
• It costs you the shyest people. Every step between wanting to come and being counted loses somebody, and unfamiliar bots are a real step.

The capability table

Here is the whole review in one place. The middle column is why the feature is worth configuring, and the right column is the sentence nobody puts in a feature comparison.

Read the right column top to bottom and the pattern is unmistakable. Every stopping point is the same stopping point wearing a different hat.

Telegram is superb at moving messages to the right people at the right time. It has no object that represents an event, so there is nothing for any of these features to point at.

What the missing object looks like

This is not a gap anyone needs to invent a solution for. The IETF specified it in RFC 5545, the iCalendar specification, in 2009.

It defines an event as named fields. A start and end time, a location, an organiser, each attendee with a participation status, a revision number and a last-modified timestamp.

The participation status is the field that would change your Sunday. Its default value is NEEDS-ACTION, which means silence has a name and a person who has not answered is not filed alongside a person who has.

There is a companion specification, RFC 5546, covering how invitations and replies travel. So both the invitation and the answer were formalised over fifteen years ago.

Map those fields onto the feature list and the mismatch is obvious. A pin is a location field with no revision number, a poll is a set of attendees with no way to change status, and a scheduled message is a start time with no link to the event that owns it.

The longer version of this argument lives in the difference between a conversation and an event object. It is the idea this whole review keeps bumping into.

How to actually configure the group

None of the above is a reason to configure your group badly. A well configured Telegram group is a genuinely pleasant place to organise something, and the settings take about ten minutes.

1. Decide whether you need topics at all. Below a few hundred members and one event at a time, topics add navigation cost for no benefit. Turn them on when two conversations are visibly interrupting each other.
2. Restrict pinning to admins. One pin per event is the rule, and the only way to keep it is to make everyone else unable to break it.
3. Fix the poll defaults before you post one. Turn anonymous off so you get names, and turn multiple answers on when you are asking which dates work.
4. Use polls for the date and then stop. Once the date is chosen, never quote the vote count as a headcount. It answered a different question.
5. Appoint a second admin with pin and topic rights. Not for moderation, for continuity. One person on holiday should not freeze the group's ability to correct a detail.
6. Schedule the morning reminder, but write it last. Set it once the details have stopped moving, and edit it if they move again.
7. Give the event one address outside the chat. Put the current time, place and answer mechanism somewhere that can be linked to, and let the pin point at it instead of restating it.

Step seven is the one that changes the organiser's week. Retyping a detail creates a second copy that can drift out of date, and pointing at a record creates nothing that can drift.

It feels curt for about a day. Then it feels like someone else took over the admin, which is roughly what happened.

The objections worth answering

"Our group is small, this is overkill"

For a group of nine planning one dinner, it probably is. Everything here scales with how often the group plans, not with how many people are in it.

A club that runs something every Sunday hits the same four questions fifty times a year. That is where configuration stops being fussy and starts being cheaper than the alternative.

"Reactions give us a rough count"

Reactions are a genuinely good social signal and terrible attendance data. A thumbs up on an announcement means the announcement was welcome.

The gap between that and a promise is where over-booked minibuses come from. We looked at that specific confusion in why emoji reactions do not make attendance records.

"People change their minds anyway, so why bother recording it"

Changes are the argument for a record, not against one. A number that moves for a reason you can see is useful, and a number that moves silently in a closed poll is not.

The whole problem of people dropping out late gets its own treatment in how to handle changing RSVPs in group planning. Nothing in Telegram's feature set has an opinion about it.

"We should just move to something built for events"

Almost never worth it, and this is the point most feature reviews get wrong. The conversation in a good Telegram group is not overhead, it is most of the reason people show up.

Moving a community to get a headcount trades something valuable for something small. The gap between chatting and planning is worth reading about in Telegram chat versus structured planning, and the wider version sits in the missing layer between Telegram communities and offline events.

Where Ontaym fits

Ontaym exists for exactly the column on the right of that table, which is the honest reason this article is on our blog.

An event is a record rather than a message. It has one address you can drop into a Telegram group, a topic, a channel or all three at once.

Guests answer by opening a link. No account, no bot to start, no phone number handed to a room of strangers.

Your group stays exactly where it is, with its topics and its pins and its excellent polls. Nothing about the configuration you just did goes to waste.

It is a deliberately narrow scope and it is not right for everything. A ticketed conference belongs on a publishing platform, and coffee with one friend needs nothing at all.

The conclusion, honestly

Telegram is the best-equipped messaging platform for running a group, and you should use its features properly. Restrict the pins, fix the poll defaults, split the topics, appoint the second admin and schedule the reminder.

Do all of that and you will have a well run conversation. That is a real achievement and it is not nothing.

It is also, precisely, a well run conversation. Every feature in this review organises what people said, and none of them holds what is true.

The plan still needs somewhere to live. One time, one place, one organiser, and a list of people who said they are coming that can change right up until Sunday morning.

Configure the room, then give the plan an address. The room was never going to be the address.

Frequently asked questions