← Visual research archive

Flow design and review / Current official Studio Flow Builder reference screenshot

Flows became a shared editing surface.

Rasa described Studio 1.0 as a no-code surface for designing, testing, reviewing, and publishing assistants built around modular flows.

Source event Retrospective prepared Not an original historical publication
Rasa Studio Flow Builder showing the My flows table, search field, Create flow button, and Train button
Current official Studio Flow Builder reference screenshot · Rasa · Original source ↗Local visual review · not cleared for production

The documented moment

Rasa published its Studio 1.0 release note on 29 November 2023. It described a visual Flow Builder, a Try Your Assistant panel, an annotation dashboard, a content-management interface, and training/publishing controls. The post said its CALM approach could guide users through defined flows while handling rephrasing and interruptions. Those are vendor descriptions of the release, not proof that every interruption is handled correctly in every deployment. The image is a visually checked current Rasa Studio documentation reference, not a claimed 2023 screenshot; its capture date is unknown.

What a builder can borrow

A flow is not finished when its happy path works. Give the content and operations team a review surface that preserves the user turn, the system interpretation, the selected path, the response, and the next action. Labels should describe an observable defect—missing source, unsafe action, wrong handoff, stale policy, confusing wording—not merely “bad answer.” That gives later editors a route from a conversation record to a concrete change. Keep a version boundary around each change so a team can compare behavior rather than relying on memory of what the assistant used to do.

A useful prototype test

Select ten real or scripted edge turns: an interruption, a correction, an incomplete identifier, a policy exception, and a handoff request. Ask a designer and a QA reviewer to label the trace independently and then compare their proposed fix. If the tool does not show enough evidence to reach a shared conclusion, add it before increasing automation. This is a workflow recommendation, not a claim that Rasa Studio passed this exercise. Confirm current product behavior and access controls against current documentation.

Keep the evidence attached

Source and limits

Behind the Release Notes: Rasa Studio 1.0 ↗ · Rasa · 2023-11-29. Product status and documentation may have changed since this dated announcement. The design lessons are our editorial synthesis.

Source imagery is included for local owner review only. Copyright remains with the respective rights holders; public reuse is not cleared.

Find your next good decision.

Start typing to explore the guides.

76 sourced guides · Escape to close