Telegram
Build the Telegram sales flow, run the bot at launch, and read the handover back.
Automation runs from launch — the flow, the bot, the point a person takes over, the run you read back. Today the workbench designs and inspects the conversation; connecting a bot this afternoon is not on.
What the work looks like.
Build the flow
The opening, the qualifying branches, the objection paths and the point where the bot stops — one script on a canvas, with the outline beside it for review.
Run the bot
Automation runs from launch: the Launch plan is the point that starts the bot. Today a run is a local inspection against checked-in data, not a live Telegram connection.
Hand over, then read the run back
The handover is a node with a condition. After an attempt, the ledger holds the path, the outcomes, the timing, the repairs, the handover and the delivery facts, in the order they happened.
The awkward branches are the ones worth drawing.
A bot that handles a ready buyer is easy. The value is in the paths nobody writes down: the person who asks the price first, the one who goes quiet for two days, the one who asks something the script has no branch for. Those are the paths that reach a human, and drawing them is how the handover stops being a surprise.
Automation runs from launch.
Chawo cannot connect to Telegram or send a message today. The workbench designs and inspects the conversation on your machine. The Launch plan is the point that starts the bot, and it is not a checkout.
Channels.
- TelegramIn progressDesign and read Telegram conversations in Chawo. Message delivery is performed by the runtime that owns the channel, not by Chawo.
- WhatsAppPlannedOn the roadmap. There is nothing to connect yet, and we would rather write that than show a logo.
- VoicePlannedThe navigation model already accounts for voice agents. They do not work today.