Get early access

Telegram chat bots · broadcasts · chat automation · AI

Manage chats. Build the automation.

The canvas and its branches ship today. Running a Telegram bot, sending broadcasts, and answering from your material are at launch; the other channel inputs shown here are on the roadmap.

Get early accessSee how it works

Five inputs. One editable flow.

Ships today

The canvas ships today; every channel input carries its own at-launch or roadmap status.
Telegram botAt launchTelegram accountRoadmapWebsite chatRoadmapWhatsAppRoadmapVoiceRoadmapyesnoConversationarrivesRetrieve fromyour materialAnswerQualifiedBook a callFollow up laterHand overto a personTelegram botAt launchTelegram accountRoadmapWebsite chatRoadmapWhatsAppRoadmapVoiceRoadmapyesnoConversationarrivesRetrieve fromyour materialAnswerQualifiedBook a callFollow up laterHand overto a person

Three places a conversation goes wrong, and none of them are visible.

The branch lives in someone's head

The path that handles a hesitant buyer is real. It is just not written anywhere a second person can read, so nobody else can change it safely.

The handover leaves no record

A person took a conversation over on Tuesday. Which branch gave it to them, and what the bot had already promised by then, took the afternoon to reconstruct.

The edit shipped unverified

The change looked small, so it went out the same hour. The run that shows what it did to the other branches does not exist.

What this is built to do, and how far each piece has got.

Ships today

  1. Ships todayAt launch

    The canvas ships today; Chawo runs the bot and automatically assembles its funnel at launch.

    The canvas holds the flow, branches, and handover point; the bot runs from that design on the Launch plan.

At launch

  1. At launch

    Telegram broadcasts to bot subscribers are at launch.

    The audience is the bot's subscribers, and Telegram is the delivery channel at launch.

  2. At launch

    AI answers from your material are available at launch.

    Retrieval grounds each answer in the documents you supply.

  3. At launch

    MCP setup, funnel export, and import are available at launch.

    Configure Chawo through MCP, then export and import funnels with their settings.

Roadmap

  1. Roadmap

    The Telegram connector and one inbox are on the roadmap.

    Connect a Telegram bot or personal account, view its chats, and work from one inbox.

  2. Roadmap

    Website chat and visitor identification are on the roadmap.

    Add a chat widget to the website and identify the visitor behind the conversation.

  3. Roadmap

    Chawo proposes funnel improvements from your own numbers on the roadmap.

    Give it the statistics and it names where the funnel leaks — the product cannot collect those numbers today.

The exchange, as it is meant to go.

The turns show the intended shape; a recorded exchange replaces them when the app ships.

  1. Customer

    The buyer asked whether a return after sixty days is still covered under the autumn policy.

  2. Bot

    The autumn policy you loaded, the Returns section, covers a return within ninety days of delivery, so sixty days is inside that window.

  3. Customer

    They want to book a call this week.

  4. Handover

    Marina took the conversation over.

  5. Marina

    I have the thread and the Returns section. I will take the booking from here.

Pricing at launch.

Three plans, written down so the numbers have one home. Nothing is for sale today.

Design

$0per month

Launch

$10per month

Own agent

$50per month

Read the plans

Questions worth answering before you ask them.

Does Chawo send messages to my customers?
No. Chawo is where the conversation is designed, run and inspected. Delivery is performed by the runtime that owns the channel.
What does the semi-manual part actually mean?
The handover is part of the script rather than an escape from it. You draw where the bot stops, what it passes on, and what the person sees — and the run ledger records when it happened.
Does it call a model or write to my CRM?
Not today. It reads checked-in redacted or synthetic data and does not contact a live runtime, a model provider, a CRM or an ad platform.
Is there a hosted version I can sign up for?
Not yet. The current build runs locally and answers only over loopback. Early access is how you hear when that changes.
Who is it for?
The person who answers for how the bot behaves and gets woken when it behaves wrong. Today that is most often one operator inside a small sales team.
What happens to a conversation I load into it?
It stays on your machine. There is no upload step, because there is nowhere for it to be uploaded to.

Early access is a list of operators, not a waiting room.

Get early accessRead the product page

The project is raising.

Contact is welcome. The early access list is the channel for now — a separate investor inbox is not built yet.

Leave a contact

Get early access

Tell us where you run conversations today. We write when the hosted build opens, and when Telegram delivery lands.

The form is not connected yet: it lands with the form contour, and a field that silently drops what you typed would be worse than no field. Until then, the address below reaches us.