Skip to content
Bot Studio / Visual automation

Visual flows, saved versions, test runs and debugger

Map a conversation into a clear flow.

Build a visual path for routine WhatsApp conversations, with the person and the next action kept in view. Bot Studio is being prepared and audited for Chatflow's launch.

Example flow · not a product screenshot
Order enquiryIllustrative draft
01 / TRIGGERCustomer sends a messageStart when an order question arrives.
02 / CONDITIONCheck the requestRoute an order question to the relevant path.
03 / ACTIONSend a reply or assign a teammateKeep the next step tied to the conversation.
Example only. The full set of flow steps, run history, and analytics is still being specified and checked for launch.
01 / Why it helps

A place to design what happens next.

01

Shape a visual flow

Arrange supported conversation steps, save drafts and publish a checked version. Native actions include replies, conditions, waits, labels, assignment and handoff.

02

Check each run

Inspect recorded steps and outcomes in the Flow Debugger. Test runs are kept separate from customer runs.

03

Learn where flows stall

Recorded runs show custom events, paths, completion and failures. Analytics reports its observation window and does not fabricate activity.

02 / Studio direction

Design, test, then understand the result.

  1. 01

    Draft the route

    Start with a message trigger, connect the relevant conditions and actions, and save the visual flow as a draft.

  2. 02

    Test before publishing

    Test the saved draft without sending customer messages, review the trace, then publish or pause. Validation explains any unsupported steps.

  3. 03

    Inspect the outcome

    Use run history and step outcomes to inspect what happened. Interrupted effects stop for review rather than blindly repeating a customer message.

03 / Availability

Supported steps and connection requirements

Visual Bot Studio uses saved, versioned flows with bounded execution and durable waits. Live replies require a connected WhatsApp number and the applicable service window or approved template. Third-party connectors and unsupported nodes remain visibly unavailable. Arbitrary code bots stay disabled. Knowledge-based Agent Studio remains separate and planned.

Start a conversation

Plan the flow. Keep the conversation human.

Book a demo