I also build bots
Notifications, orders taken in the chat, internal tools, content on a schedule, payments. Telegram most often, though the messenger is the smallest part of the job — VK, WhatsApp and Discord are the same product with a different adapter under it. One of mine has posted to a private team every day for a year. The rest of this page is what I could build next.
Something happens in your system and the right people hear about it: a new order, a failed payment, a form filled in, a service down. With a mute switch, because a bot you cannot shut up gets blocked.
A form your customer fills in as a conversation, landing in your CRM, spreadsheet or inbox as one clean record. Nothing for them to install, nothing for you to explain.
Rotas, reports, approvals, access requests, handovers between shifts. The things a team already does by hand in a group chat, done by the chat instead.
Digests, announcements, reminders, a daily post. Written by a model if that is what you want, or put together from your own data if it is not.
Paid access, subscriptions, one-off purchases — through the messenger’s own payment flow or a provider you already have a contract with.
You edit the content, the users, the schedule and the bans from your own chat. No separate panel to log into, and no waiting on me to change a sentence.
Sending on a timetable, in each person’s own timezone, from a worker that a restart or a deploy does not quietly kill.
Long messages get split, rate limits get respected, failed sends get retried, unsubscribes get honoured. Most of the time when a bot lets someone down this is how: the broadcast stops halfway and nobody notices.
Hosting, webhooks, monitoring and the dull infrastructure underneath. Written up on handover if you would rather run it yourself afterwards.
Tell me what the bot has to do and who it is for. You get a working prototype on real data before anything is agreed in detail, because nobody can judge a description, and a bot is cheap enough to build that arguing about it on paper costs more than just making it. After that it is your notes and my evenings until it does the job.
Plenty of what people ask a bot for is better off as a scheduled email, a shared spreadsheet or a button somewhere you already have buttons. If that turns out to be your case, I’ll say so before you have paid for anything. A bot earns its keep when the conversation is genuinely where the work happens — which, for a team that lives in a group chat, it usually is.