How to Automate Telegram

Telegram reaches the people who are not at a desk

Telegram is a free messaging app with groups, channels and bots, and for a lot of businesses it is the quickest way to reach someone who is nowhere near a computer. Drivers, engineers, site managers, kitchen staff and shop owners all have it open already.

It matters most where email is not really read and a desktop chat tool would never get installed. A crew of eight has a group. The owner has a channel where the day's numbers get posted. A supplier set up a bot that nobody ever configured properly.

Delivery is the appeal. A message lands on a phone in a pocket in about a second, costs nothing, and needs no licence and no company login. For a small operator that is often the only channel that genuinely works.

The person on site finds out last

The gap is never the sending. It is the knowing.

Someone at a desk checks whether the payment cleared, then types it into the group. Someone opens the job system to see which visits are booked for tomorrow and pastes the list in at nine at night. Someone notices at four in the afternoon that a delivery never left, four hours after the courier site said exactly that.

The information already exists. It is sitting behind a login on a screen nobody had open, waiting for a person to go and look before anyone else can be told.

By the time the group is told, the fact is often hours old, and the person it mattered to has already driven to the wrong place or waited for a part that was never coming.

A bot only says what it is handed

Telegram gives you real building blocks, and they are more capable than most people use.

The Bot API will post into a group or a channel on demand, run scheduled messages, offer buttons and keyboards, and take commands from members. Channels broadcast to any number of subscribers. A group can be quietly automated by a bot nobody has to think about.

What a bot cannot do is find anything out. It is a mouth, not a pair of eyes. Something has to hand it the figure, and that something is either a developer wiring up an API, assuming the system you care about even has one, or a person reading a screen and typing.

For most small operators it is the second, which is why so many of these groups are a stream of forwarded screenshots.

So the bot ends up as a megaphone for whatever a human already went and read, which is useful, but it is not automation.

The group can carry the day's facts

The posting has never been the problem. The reading in front of it is, and once a browser does that reading the group changes character.

Tomorrow's jobs, posted at six the evening before, read out of the scheduling system the office uses. The payments that failed overnight, named. The three deliveries that have not moved since yesterday, checked on the courier site by reference number. The stock lines that will not last the week.

It works the same way for the things people ask about all day. Whether the part arrived. Whether the invoice got paid. Whether the customer replied. Whether tomorrow is still going ahead.

Two things are worth deciding early. Post exceptions rather than everything, because a group that pings all day gets muted and then nobody sees the one message that mattered. And keep what goes to the crew separate from what goes to a customer: the crew group can run on its own, a message to a client should not.

Something has to go and look first

A bot will happily post the figure. Getting the figure is the part that still involves a person and a browser tab.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the scheduling system, the bank, the courier site or the supplier portal, reads what is on the screen, and hands the result to your bot to post into the group.

It runs on your schedule in your own private environment, and you can watch a run and stop it mid-way. Anything that would reach a customer is drafted and waits.

The workflows below are already built, and each shows exactly what it opens.