Community Manager
Managing a 93-Person Meetup Community From Telegram
Key Takeaway
I run the Mr.Chief Paris meetup — 93 registrations, event management, polls, RSVPs, announcements, and follow-ups — entirely through a Telegram bot powered by Mr.Chief.
The Problem
Community management is a time vampire. You set up a meetup. People register. Then you need to: send confirmations, post reminders (3 days before, 1 day before, 2 hours before), run polls for topics, manage RSVPs, answer questions, handle last-minute changes, send follow-ups with slides and recordings, and keep the energy going between events.
For the Mr.Chief Paris meetup, we hit 93 registrations. That's 93 people who expect communication. And I'm not a community manager. I'm a founder running a venture studio with 31 AI agents and a portfolio to manage.
The traditional approach: Luma for registration, a separate Telegram group, manual announcements copy-pasted between platforms, and hoping I remember to send the reminder the day before. Spoiler: I didn't always remember.
The Solution
A Telegram group where Alfrawd serves as the community assistant. Not just a notification bot — an intelligent participant that handles polls, RSVPs, announcements, reminders, and Q&A. With requireMention enabled so it doesn't respond to every message, but instantly available when summoned.
The Process
The Telegram group configuration:
yamlShow code
# mrchief.yaml — community group config
channels:
telegram:
groups:
- id: "mrchief_paris_meetup"
name: "Mr.Chief Paris"
requireMention: true # Only respond when @mentioned
capabilities:
- inline_buttons
- polls
- reactions
context: |
This is the Mr.Chief Paris meetup community group.
93 members. Monthly events about AI agents and automation.
Be helpful, concise, and energetic. You represent the project.
The event lifecycle, fully automated:
yamlShow code
# Event announcement (scheduled 2 weeks before)
- name: meetup-announce
schedule: "0 10 * * 1" # Check every Monday for upcoming events
task: |
Check if there's a meetup in the next 2-3 weeks that hasn't been announced.
If yes, post to the Mr.Chief Paris group:
🎉 Next Mr.Chief Paris Meetup!
📅 [Date] at [Time]
📍 [Venue]
🎯 Topic: [Theme]
[Inline buttons: "I'm coming ✅" | "Maybe 🤔" | "Can't make it ❌"]
Plus a Luma registration link for newcomers.
# Reminder sequence
- name: meetup-remind-3d
trigger: "3 days before event"
task: |
Post reminder with current RSVP count:
"📢 3 days until Mr.Chief Paris! [X] people confirmed.
Haven't RSVPd yet? Tap below."
- name: meetup-remind-1d
trigger: "1 day before event"
task: |
Post final reminder with logistics:
"⏰ Tomorrow! Here's everything you need:
🕖 [Time] — doors open 15 min early
📍 [Address + Google Maps link]
🎯 Agenda: [topics]
See you there! 🚀"
- name: meetup-followup
trigger: "1 day after event"
task: |
Post follow-up:
"Thanks to everyone who came last night! 🙌
📊 [Attendance] people showed up
📎 Slides: [Drive link]
🎥 Recording: [link if available]
[Poll: What topic for next time?]
🔹 Advanced agent orchestration
🔹 Building custom skills
🔹 Live demo: multi-agent workflows
🔹 Suggest your own (reply below)"
The topic polling system:
View details
# When triggered by @mention or scheduled
Alfrawd posts a native Telegram poll:
📊 What should we cover at the next meetup?
🔹 Multi-agent orchestration patterns
🔹 Building custom Mr.Chief skills
🔹 AI agents for sales & outreach
🔹 Live coding: agent from scratch
🔹 Panel: founders using agents in production
[Multiple choice, anonymous voting]
Handling Q&A in the group:
View details
Member: "@Alfrawd how do I install Mr.Chief on my Mac?"
Alfrawd: "Quick start:
npm install -g mrchief
mrchief init
mrchief gateway start
Full docs: docs.mrchief.com/quickstart
Hit me up if you get stuck on any step 🛠️"
The Results
| Metric | Before (Manual) | After (Agent) | Delta |
|---|---|---|---|
| Time on community management | 3-4 hrs/event | 15 min/event | -93% |
| Reminder messages sent on time | ~60% | 100% | +67% |
| Post-event follow-up sent | ~40% | 100% | +150% |
| RSVP tracking | Manual spreadsheet | Automatic inline | -100% manual work |
| Topic polls conducted | Rarely | Every event | Consistent |
| Member questions answered | Hours delay | <5 min | -95% response time |
The community feels more active and organized than when I was manually managing it. Because the bot is consistent. Reminders always go out on time. Follow-ups always happen. Polls always run. Consistency builds trust, and trust builds community.
Try It Yourself
- Create a Telegram group for your community
- Add your Mr.Chief bot with
requireMention: true(critical for groups — otherwise it responds to everything) - Set up the event lifecycle crons: announce → remind → follow-up
- Enable inline buttons for RSVPs and polls for topic selection
- Give the bot context about your community so its answers are on-brand
The requireMention setting is crucial. Without it, the bot would respond to every message in a 93-person group. With it, the bot is silent until someone directly asks for help. Best of both worlds.
93 people. Monthly events. One bot. The community runs itself — I just show up and present. Everything else is automated.
Related case studies
Community Manager
Discord Community Moderation — 24/7 Without a Human Mod
An AI agent moderates our Discord community around the clock — answering questions, welcoming members, escalating edge cases — with a 47-second average response time, replacing a $3-5K/month hire.
Founder
The Morning Briefing That Replaced My First Hour of Work
A 6am cron synthesizes 48 hours of calendar and urgent emails into a 2-minute Telegram briefing, replacing 45-60 minutes of manual morning prep.
Event Organizer
Event Speaker Outreach — From Luma List to Confirmed Speakers in One Week
AI agent researches target speakers, sends personalized multi-channel outreach, tracks the pipeline in Google Sheets — 3 confirmed speakers for Barcelona meetup in one week, 70% response rate.
Want results like these?
Start free with your own AI team. No credit card required.