How to Keep Event Information Organized in a Telegram Group

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

Telegram gives you topics, multiple pins, scheduled messages, channels and bots, and most groups use about a tenth of it. Here is a setup you can copy in twenty minutes, feature by feature, with an honest account of the one thing it still cannot do.

Forty people, one Saturday, and a group that already works

A running club of forty people has a Telegram group. Every few weeks they organise something bigger than a Tuesday jog: a trail day, a coach, a pub afterwards.

The plan always gets made. It also always gets made twice, because by Thursday three people have asked what time the coach leaves.

Here is the thing worth saying out loud before anything else. That group is not badly run, and Telegram is not a badly built app.

Telegram has more organising machinery than any messaging app in wide use. Topics, multiple pins, scheduled messages, channels, granular admin rights, an entire bot platform.

Most groups use about a tenth of it. This article is the other nine tenths, arranged into a setup you can copy in twenty minutes.

Every feature claim below was checked against Telegram's own documentation on the day of writing, and the links go to that documentation. At the end there is an honest paragraph about the ceiling, because there is one.

What you are actually organising

Before touching a setting, be clear about what has to end up where. A group planning a real-world event is running four different conversations in one room.

There is deciding, which is loud and useful: dates, venues, whether the pub is any good. There is the current truth, which is short and boring: it is on this date, at this place, at this time.

There is the answer, which is who is coming. And there is everything else, which is the chatter that makes the group worth being in.

Those four things need different treatment. Deciding wants a busy thread, the current truth wants to sit still, the answers want to be countable, and the chatter wants to be left completely alone.

Almost every messy planning thread is one of those four leaking into another. The setup below is mostly about keeping them apart.

Turn on topics, and use exactly three

Topics are the single biggest improvement available to a busy Telegram group, and most groups never switch them on. Telegram describes them as splitting a group into separate threads, each with its own chat history, shared media and notification settings, in its FAQ on groups and channels.

An admin enables them in Group Settings. The announcement post for topics in groups also notes that admins control who is allowed to create and manage topics through the Permissions screen.

Use that permission. An open topic list turns into fourteen abandoned threads within a month, and a group with fourteen topics is less organised than a group with none.

Three is the right number for a group that runs events. More than that and people stop knowing where to post, which sends everything back into the main thread by default.

The General topic is worth understanding properly, because it behaves differently from the ones you create. Telegram's technical documentation on forum topics says every forum has a General topic that cannot be deleted, only hidden.

So General is where the group already lives, and you are not going to move it. Leave it as the chatter room and build around it.

The same documentation covers two features that matter more than they sound. Topics can be pinned to the top of the list, and topics can be closed, which prevents further messages from being sent to them.

Closing is the useful one for events. When the trail day is over, close its topic instead of deleting it, and the history survives without anyone posting into a dead plan six weeks later.

Why not one topic per event?

Because it feels tidy for two events and becomes a graveyard by the fifth. New members open the topic list, see nine entries, and cannot tell which one is happening this month.

One rolling "Next event" topic keeps the answer to "where do I look" permanently the same. If your group genuinely runs several events at once, then one topic per live event is fair, and the discipline is closing each one the day after.

Pinning: what to pin and how many is workable

Telegram lets you pin more than one message. The API documentation on pinned messages states plainly that multiple messages can be pinned at the top of a chat, with a method to unpin them all at once and a search filter for listing every pin.

The fact that you can pin many is exactly why you should not. Two pins is a header, five pins is a filing cabinet, and a filing cabinet nobody opens is the same as no pin at all.

One pin per live event. If you need a second, make it the venue map and nothing else.

Pinning is also louder than people expect. The Telegram FAQ notes that when a message is pinned, all members get a notification even if they muted ordinary messages.

That is a genuinely useful property and a genuinely easy way to annoy forty people. Use it deliberately: pin when something changes that everyone must know, and pin silently or not at all for cosmetic edits.

You get one loud channel to the whole group. Spend it on the coach leaving an hour earlier, not on a typo.

Writing a pinned post that stays true when things change

This is the part with actual craft in it. Most pinned posts are written as an announcement, which is a message about a moment, and then they are asked to serve as a reference, which is a thing about now.

Those two jobs want opposite writing. An announcement is excited and full of context, and a reference is short and structured and slightly dull.

Write the pin as the reference. Put the excitement in a separate message underneath, where it belongs.

The structural trick is to write only facts that would need editing if they changed, and to put each on its own line. Prose hides changes, and lines expose them.

Here is the shape that survives contact with a moving plan.

• A title line with the event name and nothing else.
• Date, time, place, on three separate lines, each stated once.
• The meeting point, written as a place a stranger could find, not "the usual corner".
• What to bring, as a short list.
• How to say you are coming, as one link or one instruction.
• A last updated line with the date you last edited it.

That last line does most of the work and costs one second. Telegram messages can be edited after sending, and edited messages carry a small "edited" label, as Telegram's post introducing message editing describes.

The label tells a reader that something changed. It does not tell them what, or when, or whether the version they memorised last week is the one on screen.

A manual "last updated 14 March" line closes that gap for free. It is the cheapest honesty available inside a chat app.

Two rules that keep the pin honest

Never state a fact twice in the pin. If the time appears in the title line and again in the details, you have created two things to edit, and one day you will edit one of them.

Never write anything in the pin whose truth depends on the reader's calendar. "Next Saturday" is a landmine, "Saturday 14 March" is a fact.

When something does change, edit the pin, then post one short message in the topic saying what changed and that the pin is updated. The edit fixes the record and the message does the telling, which are two different jobs.

Do not post the new details in full. The moment the new time exists as a separate message, you have two copies that can drift apart, and this is exactly the failure we took apart in the piece on creating one source of truth for a group event.

Scheduled messages, or how to write Thursday's reminder on Monday

This is the most underused feature on the list. Telegram lets you hold the send button in any chat and pick a time in the future, as described in the blog post introducing scheduled messages and reminders.

That same post notes the message arrives with a calendar marker so people can see it was planned. Which is fine, because a reminder that looks like a reminder is not embarrassing.

The organising move is to write every reminder at the moment you create the event, while you still have all the details in your head. Then stop thinking about it.

A schedule that works for most events looks like this.

Four scheduled messages, written once, and the organiser never has to remember a thing. This alone removes most of the low-grade admin that makes running events feel like a job.

One warning. Scheduled messages send whether the plan changed or not, so if the venue moves on Wednesday you must go into the scheduled list and fix the ones you already wrote.

Put that on your own checklist as part of changing anything. An automated reminder confidently announcing the old address is worse than no reminder at all.

Reminders inside a chat also behave differently from reminders attached to an event, which is a distinction worth knowing before you rely on either, and we pulled it apart in event reminders against ordinary chat notifications.

Adding a channel next to the group

Once a group passes roughly a hundred active people, the announcement problem changes shape. A message that everyone must read cannot survive in a room where everyone can reply.

Telegram's answer is a channel, described in its FAQ as a tool for broadcasting to large audiences, with an unlimited number of subscribers. Posts are signed with the channel name rather than the person, which quietly removes the "who is in charge" question from every announcement.

The powerful part is that a channel can be linked to a discussion group. Telegram's documentation on discussion groups explains that when a supergroup is linked to a channel, channel posts are automatically forwarded into the group and pinned there.

Read that again, because it is the bit people miss. Posting once in the channel produces the announcement, the auto-forward and the pin, in one action.

The same documentation explains that comments on a channel post are the message thread of that forwarded message in the linked group. So discussion of each announcement stays attached to the announcement instead of scrolling away from it.

That is a genuinely good structure, and it is roughly the best a chat app can do. The announcement is legible, the replies are attached, and the pin happens without anyone remembering to pin.

When a channel is overkill

Under about fifty people, do not bother. A channel adds a second room, a second thing to join, and a second place a newcomer can fail to find.

The honest test is whether announcements are currently getting buried. If the group is quiet enough that a pinned message stays visible for a week, you already have what a channel would give you.

If you are weighing it up seriously, the full argument lives in our comparison of Telegram channels against groups for event announcements. The short version is that a channel fixes distribution and changes nothing about who is coming.

Where a bot genuinely helps, and where it is showing off

Every Telegram thread about organising eventually produces the same suggestion. Use a bot.

Bots are real and powerful. The FAQ describes them as small programs running inside Telegram, built by outside developers on the Bot API, and they can do considerably more than most people assume.

They are also the most over-recommended solution in community organising. A bot is a good answer to a repetition problem and a poor answer to a one-off problem.

The middle row is where most groups get it wrong in both directions. Small groups build a bot for a single event and large groups refuse to build one for a monthly recurring problem.

There is also a cost that never appears in the feature list. Every step between "I want to come" and "the organiser knows" loses you people, and starting a private chat with an unfamiliar bot is a real step.

Members who have lurked happily for a year are precisely the ones who will not take it. Which is a shame, because they are also the ones you most wanted at the trail day.

The whole setup, in order

Here it is as a procedure. It takes about twenty minutes once, and a couple of minutes per event afterwards.

1. Enable topics and restrict who can create them. Group Settings turns topics on, and the Permissions screen controls who can create and manage them. Leave that to admins.
2. Create exactly two topics beside General. Name them "Next event" and "Announcements", and pin both to the top of the topic list. General stays as it is, because it cannot be deleted and it is where your group already lives.
3. Lock the Announcements topic to admins. One post per event, no replies. The moment discussion is allowed there, it becomes a second General.
4. Write the pin as a reference, not an announcement. Title, date, time, place, meeting point, what to bring, how to say you are coming, and a last updated line. Each fact appears exactly once.
5. Pin it once, in the Next event topic. One pin per live event. Remember that pinning notifies everyone, including the people who muted the group.
6. Schedule the reminders immediately. Hold send, pick a time, write four messages: one week out, two days out, the night before, ninety minutes before. Do this while the details are still in your head.
7. Put the answer somewhere countable. A poll is fine for choosing a date and poor for attendance, so the "how to say you are coming" line should point at something that can be changed later by the person who wrote it.
8. Handle changes in one place. Edit the pin, update the last updated line, fix any scheduled messages that now say the wrong thing, then post one short message saying what changed.
9. Close the topic when it is over. Closing preserves the history and stops anyone posting into a finished plan. Then reuse the same topic for the next event.

Step seven is the one that will not sit still, and it is worth being straight about why. Everything above it is organising messages, and step seven is asking for something a message cannot be.

A poll is the obvious tool and it answers the wrong question. Voting that a Saturday works is a statement about your calendar, and we went through that mismatch properly in why Telegram polls do not give you actual attendance.

What this setup fixes, and what it does not

Run the nine steps and a genuine amount of pain disappears. The details stop getting buried, newcomers can find them without asking, reminders happen without an organiser remembering, and the chatter stops competing with the plan.

That is most of the day-to-day friction, and it is worth the twenty minutes. It also has a ceiling, and the ceiling is not a Telegram problem.

Everything above is organisation of messages. A very well organised message is still a message, and a message can contain a fact without holding one.

Three specific things stay broken no matter how well you configure the group.

Nobody can query it. The pin cannot answer "how many are coming" or "who has not replied", because a pinned post is text and not a set of fields. A human has to read the thread and count, which is the job the notebook was doing.

Change is announced, not applied. Editing the pin updates one message, and it does not update the version living in forty people's memories from last Tuesday. The edited label proves something moved without saying what.

It stops at the edge of Telegram. Anyone in your group who is on WhatsApp instead, or on nothing, is outside the entire structure. Half of real groups have at least one person like that.

The underlying reason is the same one that shows up in every messaging app. A chat stores history, which is everything said in order, and a plan is state, which is the few things true right now.

We took that distinction apart in the difference between a conversation and an event object, and it applies to a beautifully configured Telegram group exactly as much as it applies to a chaotic one.

Worth knowing too that the record you are hand-building has been specified since 2009. RFC 5545, the iCalendar specification, defines an event as named fields: a start and end, a location, an organiser, each attendee with a participation status, a revision number and a last-modified timestamp.

Look at the pin format above and you will notice it is a hand-typed imitation of that list. The last updated line is a manual last-modified field, and the title, date and place lines are manual versions of the rest.

The field that has no equivalent anywhere in a chat is the per-person status, whose default value is NEEDS-ACTION. That default gives silence a name, and in a group of forty, silence is most of your data.

Where Ontaym fits

Ontaym exists for the gap this article ends on, which is the honest reason we wrote it.

An event is a record rather than a message. It has one address you can drop into your Next event topic, your Announcements channel, or a WhatsApp thread with the three people who never joined Telegram.

Guests answer by opening a link, without an account, a bot or a phone number handed to thirty nine strangers. When the coach time moves, you change it once and every copy of the link is now correct, because there was only ever one copy.

Your group stays exactly where it is. The topics, the pins and the scheduled reminders in this article are all still worth doing, and the pin simply becomes one line pointing at the record instead of a hand-maintained imitation of it.

It is a small scope and it is not right for everything. A ticketed conference belongs on a publishing platform, and a group of six friends deciding on Thursday needs none of this.

What to do this week

If you take one thing from all of this, take the separation. Chatter, details, and answers are three different jobs, and the misery comes from making one room do all three.

Turn on topics tonight, because it costs nothing and it is reversible. Write one pin as a reference rather than an announcement, and add the last updated line.

Schedule the four reminders the moment you create an event, not the week of it. That single habit removes more organiser stress than any other change on this list.

Then notice which questions still arrive. If they are about excitement, lifts and what the pub is like, your group is working exactly as it should.

If they are "how many are we", "is that still on", and "did the time change", those are not organisation problems. Those are the four facts asking to live somewhere a message cannot take them, and the fix is to give the plan one address and let the group point at it.

The group gets no quieter afterwards, which surprises people. It just stops doing paperwork.

Frequently asked questions