Mtiririko is a visual builder for WhatsApp conversations. Drag steps onto a canvas, wire them together, publish — and inbound messages walk the graph: menus and questions, a payment, an order, a record in your own Data tables, an AI agent for the part a script cannot do, and a hand-over to a person when it should.
Runs on WhatsApp in this release. Other channels are on the roadmap; the builder refuses to publish a flow bound to anything else.
What you can build
- Seven groups of steps — Say, Ask, Think, Decide, Wait, Do, Route — from a plain message to buttons, lists, native WhatsApp forms, files and locations, AI replies and bounded agent hand-overs, conditions and loops, delays and opening hours, API calls, SMS and email, orders and payments, Data-table reads and writes, approvals, locks and transactions.
- Triggers — a keyword, the first message ever from a contact, a tap on a button sent earlier, a record changing in a table, or a colleague starting it by hand. Ordered across your flows, with an overlap check.
- A gallery to start from — a welcome menu with opening hours, a shop that takes orders and payment, a support desk that answers from your knowledge base.
- The Studio — simulate a run on a handset before anyone real sees it, time a question out, make any step answer the way you choose, save a run as a test that gates every publish, replay a real conversation to reproduce a problem, and read where customers drop off.
- Versions — every publish is a version; running conversations finish on the version they started; an earlier version can be put back.
- Over MCP — the
flowsserver gives Claude, ChatGPT or your own agent 32 tools to read, draft, validate, simulate and (with your say-so) publish flows.
What it costs
Messages a flow sends are charged like any other WhatsApp message from your wallet; a flow stops rather than sending on an empty balance, and the owners are told. AI steps bill like inbox replies. Payments, HTTP calls, email and webhooks are on the Starter plan and above.
What we keep
Step traces for 30 days, the answers a conversation stored for 30 days after it ends, the conversation record for 180 days, the 50 most recent versions. Answers are masked on every screen unless you hold the PII permission, encrypted at rest, and deletable per person on request.
Caveats at ship time
- WhatsApp only. Messenger, Instagram, SMS and email renderings are decided but not built.
- The builder's controls are in English; validator messages and everything a customer reads are bilingual.
- Payments settle through the platform's gateway; a workspace's own gateway is enabled on request.
- A flow sends its own templates outside the 24-hour window only when you have mapped an approved template to the message's purpose.