a:store — an ecosystem of four bots
// Goal
Automate a seller who lives across dozens of chats: keep up with listings, stop losing direct messages and stop publishing posts by hand on a schedule.
// Brief
Split the work across four bots instead of one overloaded one: search and monitoring, sales and filters, reply tracking, channel publishing — with a shared reporting layer.
How we built it
One bot that does everything inevitably becomes a menu of thirty buttons. So the work is split: sell handles the listing stream and filters, search handles chat monitoring and reports, message handles direct-message follow-up, and setting\channel handles publishing.
The key mechanic in sell is filtering. A stream of listings from other people's chats is useless at a thousand messages a day. The bot states the logic plainly: with no filters you see every new message; with filters you see only matches. Each listing carries three actions — comment, mark as spam, reply privately — and there is a spam list of accounts excluded from the feed.
search walks a list of chats and returns a report: run time, the userbot account, chat count, how many succeeded, how many failed, and a per-chat breakdown. Failures are not hidden — you can see which chat dropped out. It also handles broadcasts across the chat base and the administrator list.
message solves a separate pain: a direct message nobody answered. The bot shows who sent it and how long it has been waiting, with a button to open the chat. setting\channel covers publishing: scheduled posts, moderation before they go out, and timed self-destruction with the exact number of minutes until removal.
Stages of delivery
sell — stream and filters
A listing feed from monitored chats with match filters and a spam list of excluded accounts.
Actions on a listing
Three buttons beside every message: comment, mark as spam, reply privately.
search — monitoring and reports
A pass over the chat list with a report: time, userbot, chat count, successes, failures and per-chat detail.
Broadcasts and admins
Creating broadcasts across the chat base, adding chats and accounts, managing the administrator list.
message — reply tracking
A notification about an unanswered direct message, with sender and waiting time.
setting\channel — publishing
Scheduled posting, moderation before release and timed self-destruction of messages.
Outcome
Four bots with separated roles cover the full cycle: find the listing, reply, keep the conversation, publish on schedule.
Monitoring runs across seven chats with per-chat reporting, and failures appear as their own line.
The bot opens in Telegram.
Other cases
Want the same outcome?
Tell us about the task — we will design, build and ship a solution for it.