WhatsApp gets the attention, but for structured client work Telegram is quietly the stronger platform: real multi-device support, groups with topics, and a bot API that's a decade ahead. Most agencies use a tenth of it.
Photo: Yuri Samoilov, CC BY 2.0
The setup that scales
One group per client, one topic per project (or workstream). Topics give you what email threads and WhatsApp never could: the estimation discussion, the design review and the bug reports live in the same group without drowning each other. The client adds whoever they want; you control your side.
Two rules keep it sane:
- Decisions leave the chat. Anything agreed in a topic becomes a ticket or a scope note the same day — chat is where decisions happen, not where they're stored.
- The group is the client's space. Internal debate goes in your own channels; what the client sees is status, questions and answers.
What bots should and shouldn't do
Telegram bots can read topics, post, and pin — which makes them the natural bridge to your board. The right jobs: turning messages into tickets, answering status questions from live data, flagging out-of-scope asks, and staying silent when a message is addressed to a human — the discipline that separates a useful agent from a muted one.
The wrong job: negotiating. Anything about money, dates or scope commitments gets drafted for a human to approve, not fired off because the model was confident.
Set up this way, Telegram stops being "another inbox to check" and becomes the front end of your project system — the client just thinks you're unusually responsive.
← All posts