Telegram communication bot for teams
My role:
Solution Designer
Information Architecture
Information Architecture
Information Architecture
Information Architecture
Information Architecture
Information Architecture
Information Architecture
The task: design and build a Telegram bot that routes all incoming messages into one shared channel — so every team member sees every conversation and no one has to share their personal account.
Context
A small nonprofit with two coordinators was handling all communication through personal Telegram accounts. Neither had full visibility into what the other had already answered, and messages regularly got buried under personal chats. They needed a lightweight structure inside the messenger they already used — not another tool to learn and pay for.
The key constraints were clear from the start:
The solution had to live inside Telegram
Admin personal accounts had to stay private
Multiple admins needed to respond and see the full conversation history
Media support was essential: photos, voice messages, video notes, documents
The team had to use it without technical knowledge
The Process
I started by mapping how communication actually flowed — who writes, how often, and where things fall through the cracks. Based on that, I designed a topic-based architecture: each new user who writes to the bot gets a dedicated topic inside a private Telegram group, admins reply directly in the topic, and the bot sends their response back. The user never sees the group or anyone's personal account.
Development
I wrote the bot in Python using aiogram and PostgreSQL. This wasn't a no-code constructor — the requirements called for a custom build.
What I built:
Automatic user registration on first contact
Topic creation in the admin group for each new conversation
Two-way message routing: user → topic, admin reply → user
Full media support: photos, videos, documents, audio, voice notes, video circles
Retry queue for reliable message delivery
Graceful error handling: lost topics get recreated automatically
How it works
The organization shares the bot's username instead of personal accounts
A client writes to the bot
The message appears as a topic in the team's private group
Any admin can reply
Full conversation history stays visible to everyone
The team works in familiar environment, without adding any new tools to the workflow.
Result: Using the bot team no longer spends time coordinating who replied to whom, and every conversation is visible to everyone in real time. It cut the time coordinators spent on internal communication by roughly 60%, freeing them to focus on their actual work.
Information Architecture
Information Architecture
Information Architecture
Information Architecture
