What we doPricing Talk to us Log in

Your app, on every chat interface.

Launch your app on WhatsApp, iMessage, or Telegram in minutes.

Flow asks a few questions, then builds it.

Three ways in

Start from anything.

An app, a server, a stack of endpoints, or a sentence on a napkin. Pick one and the conversation above picks up from there.

I have an app

Web or mobile. Give us the URL and we learn what it does and what people do in it.

Start here

I have an MCP/API

Point us at your tools or docs. We turn them into an agent people can talk to.

Start here

Just an idea

Flow builds it on mock data first so you can text it, then swap in real APIs later.

Start here

Logged-in actions and payments need your own API credentials. Tell us what you have and we'll say plainly what's missing.

Examples

On WhatsApp, a parcel pickup bot books a bike courier from Indiranagar to Koramangala and sends the rider's details.

On iMessage, a travel bot finds a walkable hotel in Lisbon for two nights under 150 euros and books it.

On Telegram, a customer moves a Thursday haircut to Saturday at 4:15 PM with Ritu.

Flow launches on WhatsApp, Telegram, Slack and iMessage.

The system behind
every reply.

Get started

Example: a customer asks to move a Thursday haircut to Saturday after 4; the agent offers 4:15 or 5:30 with Ritu and books 4:15.

01

AI orchestrator

A human-like chat experience. It handles shorthand, second thoughts and two languages in one sentence, then does the thing.

Example memory: usual stylist Ritu; prefers Saturday afternoons; card ending 4411 on file; asked about the serum twice.

02

Built-in memory

It remembers each customer's chat between conversations, on each channel.

Example test run: changes their mind mid-booking, asks for a refund after delivery, types in Hinglish half in shorthand, pays then changes address; 1,186 of 1,200 passing.

03

Tested on hundreds of simulated users

Every release, before a real customer ever types.

Example insights: check order status 4,120; reschedule a booking 3,050; where is my refund 2,140; talk to a human 780.

04

Insights on what's actually happening

What people ask for, what they buy, and the exact sentence where they give up.

Use cases

Apps people are rebuilding as a thread.

Anything you'd have shipped to an app store. No install, no onboarding.

  • Personal AI assistants

  • Ride booking

  • Meal planning

  • Taxes & accounts

  • Doctor visits

  • Travel & stays

  • Workouts

  • Community engagement

Pricing

Starts small. Grows when you do.

Usage scales with the conversations your customers actually have. Start free, move up when the volume does — and stay put if the cheaper plan is still the right one.

Free

$0 forever

Put it in front of real people on Telegram and see whether they use it.

Get started
  • Telegram
  • Base usage included
  • Mock-data prototype to try first
  • Community support

Self-serve

Recommended

$29 /mo

The surfaces your customers actually use, with room to grow into.

Get started
  • WhatsApp, iMessage and Telegram
  • Higher usage included
  • Extra usage billed as you grow
  • Email support

Custom

Let's talk

Bigger volumes, tighter requirements, or a surface we have not shipped yet.

Talk to us
  • Every surface, approvals handled
  • Custom usage limits and SLAs
  • Security and data review
  • Priority support

In every plan

  • Your brand on the thread
  • Every action logged
  • Mock-data preview before you commit
  • No lock-in — your data exports
FAQ

Questions,
answered.

Do I need to have an app already?

No. Point Flow at a web or mobile app, an OpenAPI spec or an MCP server and it builds from that. With none of those, it starts on mock data so you can text your app the same day and swap in real APIs whenever you have them.

Do I need engineers to set it up?

Not to get something live on Telegram — Flow handles the surface, the agent and the deployment. Real data, logged-in actions and payments need your API credentials, which is usually an afternoon for whoever owns your backend.

How does it handle orders and payments?

Actions run against your real systems, never guessed, and every one is logged so you can audit it. Before a release goes out, Flow runs it against hundreds of simulated users on the paths that matter — ordering, rescheduling, refunds, and people changing their mind mid-sentence.

What about platform approvals?

Every surface has its own review and its own rules. Flow prepares and submits what each one asks for, and shows you where each submission stands. The timelines belong to the platforms, so we don't promise them.

Does it remember a customer between conversations?

Yes. On each channel, the bot remembers the customer's chat there, so they can pick up where they left off. You can delete everything it keeps about a customer at any time.

Who owns the conversations and the data?

You do. The threads, the contacts and the orders are yours and export at any time. We do not sell data and we do not train public models on your customers.

What happens after I answer the questions?

Nothing to install and no call to sit through. We read what you told us and come back to you by email, usually within a business day, with what we'd build and what it would take.

Surfaces around it: WhatsApp, Telegram, iMessage and Slack.

Launch your app
where people already chat.

A few questions about what you're starting from. No card, no demo call.

Get started Talk to us