- Case study · Bots
- 6 technologies
SenderBot: scheduled mass messaging from multiple accounts
Elvisupdated 5 min read
A bot for mass messaging in Telegram: messages go out from several accounts in parallel and on a schedule, and payment is accepted in USDT.
The challenge
The team sent out Telegram messages on a regular basis. With a single account, everything ran into its limits: a large list couldn't receive the message in the time needed.
Then they added more accounts, but worked with them by hand. Someone switched between accounts, copied the text and kept track of who had already received it and who hadn't. One campaign took hours, and with that approach it was easy to send a message twice or miss part of the list.
They needed a tool where you set up a campaign once: pick the accounts, the text and the time, and the system does the rest without anyone sitting next to it.
The solution
I built a bot on Aiogram for managing campaigns. The sending itself goes through Telethon, meaning it comes from regular Telegram accounts. The accounts work in parallel, and each one takes its own share of recipients. The load is split across all connected accounts, so the limits of one number no longer slow down the whole campaign.
A scheduler sends messages at a set time, so a campaign can be prepared in advance. All campaign data is stored in PostgreSQL, and the database schema changes through Alembic migrations. That way the bot can be extended without losing history.
Payment is built into the bot itself and accepted in USDT. The user pays and launches the campaign in one place, without messaging a manager.
How the system works
How to send Telegram mass messages from multiple accounts
Several Telegram accounts are connected to the bot, and the campaign is split between them. Each sends its share of the messages, all at the same time. It's faster than sending from one account, and the load doesn't fall on a single number.
You manage everything through the regular bot interface in Telegram. You don't need a separate program or server access to start a campaign.
Why a Telegram mass messaging bot beats sending by hand
When you send by hand, you have to remember which account sent to whom. The bot keeps that record in the database, so you can focus on the text and the audience instead of copying messages.
A campaign that used to take hours now takes a few steps to set up in the bot and then runs without anyone involved.
Scheduled Telegram messages
The scheduler starts sending at the set time. You can write the text in the evening and schedule the campaign for the morning, when the audience is more active. While the campaign runs, nobody has to do anything.
Accepting USDT payments inside the bot
The bot accepts payment in USDT on its own. For a service used by people from different countries, that's convenient: no need to connect bank cards or deal with currency conversion.
Payment and campaign launch are in the same interface, so the user goes from order to sending without any middlemen.
Database and future changes
Accounts, campaigns and their history are stored in PostgreSQL. Schema changes go through Alembic migrations, so new features are added without editing the database by hand and without the risk of losing data.
Results
- deliverability
- 95%+
- accounts
- Multi
- 95%+ deliverability
- Parallel sending from multiple accounts
- Scheduled campaigns with no one at the keyboard
Tech stack
- Python
- Aiogram
- SQLAlchemy
- Telethon
- PostgreSQL
- Alembic
Who it is for
Teams and services that send Telegram campaigns regularly and keep hitting the limits of a single account. It also fits anyone who wants to sell messaging as a service paid in USDT.
Project FAQ
What deliverability do the campaigns get?
On this project, deliverability stays at 95% and above. A lot depends on the recipient list and the message text, so I look at the specific task before launch.
How long does it take to launch a bot like this?
The timeline depends on what you need: how many accounts, whether you want payment built in and which campaign reports you want to see. Message me on Telegram, we'll go over the task and I'll give you a timeline.
Can the bot be adapted to my workflow?
Yes. The bot is written in Python with a PostgreSQL database and migrations, so new features are added without rebuilding the whole system. For example, you can change the payment flow or the scheduler logic.
What is the bot built with?
The bot interface is built on Aiogram, and sending from accounts goes through Telethon. Data is stored in PostgreSQL, the database is accessed through SQLAlchemy, and the schema is updated with Alembic migrations.
Ready to automate your business?
A 30-minute call: we go through your processes, pick what to automate first and estimate the timeline.
- CRM
- Traffic
- Bots
- AI
- Analytics
- Integrations
- Websites
Need something similar
- BotsMeowtrics TeamAn HR system for hiring through Telegram: candidates come to the bot, AI reviews their applications, and the team lead sees the hiring funnel and traffic sources.
- Bots · 50+ operatorsOnlyServiceA Telegram bot for monitoring chatters, plus a browser extension: shifts are tracked automatically, and reports show where the revenue came from.
- Bots · auto paymentMila VelvetThe model sells access to a private Telegram channel, and the bot handles the subscriptions: it takes the payment, hands out a personal link, reminds about renewal and removes the fan from the channel when the term ends.
