How to Plan an Event in a Telegram Group (With a Real Headcount)
Trying to plan a group event over regular Telegram messages means asking "who's coming?" and then manually counting replies scattered through the chat. EventRSVPProBot turns that into one card with a live headcount, so anyone can glance at it and know exactly who's in.
This works for anything a group organizes — a game night, a dinner, a meetup — and doesn't require making anyone an admin or setting up a poll first.
Because the headcount lives on the event card itself instead of scattered across replies, whoever's organizing can make a call — do we have enough people, do we need to move the time — just by glancing at the card instead of scrolling back through the chat.
This also removes the awkwardness of chasing individual people for an answer: the card sits in the group as a passive prompt, and most people will tap a button without needing to be asked twice.
Steps
- Decide the time and title, then post it. /event tomorrow 19:00 Dinner at Marco's posts the event card immediately with three buttons: ✅ Going, 🤔 Maybe, ❌ Can't.
- Set your UTC offset so times land right. Run /tz +2 (or whatever your offset is) once — this makes "at 19:00" and other relative times parse and display correctly for your local time instead of UTC.
- Let people respond by tapping, not typing. Group members tap a button on the card; there's nothing to type or reply to. The card's counts update immediately, in place, for everyone to see.
- Check the full list of upcoming plans with /events. If the group has more than one thing planned, /events lists them all with id, time, and current Going count so nothing gets buried in chat.
- Cancel it if the plan falls through. The creator runs /cancel with the event's id (from /events) to mark it cancelled — it stays visible in history rather than disappearing outright.
Good to know
- Free groups can have 3 active events going at once — enough for most groups planning one thing at a time, or a couple in parallel.
- Pro (one-time 150 Stars per group) removes that 3-event cap and adds an automatic reminder posted to the group an hour before each event starts.
- The bot reads flexible phrasing for when: relative ("in 2h"), a clock time, "tomorrow", a weekday name, or a full date — so you don't need to memorize a strict format.
- Each bucket on the card shows up to 30 names before switching to a "+N more" count, so even a large group's card stays readable.
- There's no separate step for "closing" an event before it happens — the card just keeps accepting and updating RSVPs right up until the event's time passes, so late responses still count.
FAQ
- Do I need to make the bot an admin to post events?
- No — /event works as a regular group command; the bot doesn't need any special permissions to post or update the event card.
- Can more than one person plan events in the same group?
- Yes — anyone in the group can run /event, and each event tracks its own creator, who is the only one able to cancel that specific event.
- What if two people want to plan things happening around the same time?
- Each /event creates its own separate card and headcount — free groups can run up to 3 active events at once, so overlapping plans don't conflict.
- Does the bot remind the group before the event?
- Only Pro groups get an automatic reminder, posted an hour before the event starts. Free groups rely on the event card itself as the visible reminder.