# Record and edit flows

> Build the flows the agent replays in a live demo. Import a recording or add steps by hand, then edit selectors, fallbacks, narration and settle times.

Source: https://talkdemo.com/help/product-and-flows/record-and-edit-flows · Updated 2026-11-20

## Key takeaways

- A flow is a recorded path through your product, such as creating a report, that the agent replays step by step. Preview it, or run it in a test call, before prospects see it.
- Each step has an action, a selector, fallback selectors tried in order, the narration the agent speaks, and a settle time.
- Flows never sign in or type passwords. The agent signs in with the sealed demo login on Product before any flow runs.
- The intent description tells the agent when to pick the flow, so write it the way a prospect would ask.
- Best for roles is an optional list of roles or keywords. When a prospect's role or use case matches, the agent shows that flow first.

Flows are how the agent shows your product reliably. Someone on your team records a path once, such as "create an invoice", and TalkDemo stores each step. In a demo, the agent replays the flow while it narrates, then answers questions on the screen it ends on.

**Who can do this:** Admin, Member. Viewers can see flows. · **Plans:** live product mode (Growth and up).

## Create a flow

The **Flows** tab opens with every flow of the agent in one list: its name and prospect question, status, steps, health (success rate and last replay), **Source** (Scratch, Recorder, Claude Code or Import), when it was updated, and hints such as "1 step to review before it can be active" or "Drafting narration". Search by name or question, and filter by status (archived flows are under **Archived**). Click a flow to open it.

1. Open **Agents**, choose the agent and open **Flows**. Save your demo tenant on **Product** first.
2. Click **Add flow** at the top right (Admins and Members). It opens three tabs: **Add from scratch**, **Teach a flow by clicking** ([Teach a flow by clicking](/help/product-and-flows/teach-a-flow-by-clicking)) and **Create flows with Claude Code** ([Create flows with Claude Code](/help/product-and-flows/create-flows-with-claude-code)). The dialog remembers the tab you used last.
3. In **Add from scratch**, name the flow the way a prospect would ask for it, such as "Run monthly payroll". **What a prospect would ask** is optional (the name is used when it is empty); for example "How do I run payroll for my team?"
4. Optionally give a **Start page**, such as `/reports`. It must be on your demo tenant or an allowed host, and becomes the first step.
5. Click **Create draft and add steps**. The flow opens in the steps editor. To start from a Playwright codegen script or a Chrome Recorder export instead, click **Or import a recording file** (see [Import a flow recording](/help/product-and-flows/import-a-flow-recording)).
6. The flow starts as **Draft**. The agent only uses **Active** flows.

### Best for roles

Open a flow and fill in **Best for roles** under **Details** with the roles or keywords it suits, separated by commas, such as `CFO, finance` or `developer, API`. Up to 10. Click **Save details**.

The agent then orders the demo by the prospect's role. It learns the role from the demo link's pre-fill, from the answer to a role qualification question, or from what the prospect says, and shows the flows tagged for it first. A flow without tags is still offered, just after the tagged ones.

## Edit steps

Open a flow to see its steps in order. Each step is one row showing its number, its action, what it acts on (a button name or a page path), the start of its narration and any flags (**Needs fixing**, **Needs a review**, **AI draft**, **Failed in demos**, **Selector to promote**). A step imported with a screenshot shows a small picture of the screen on its row and a larger one inside. Click a row to open the full editor; several can be open at once, and **Expand all** or **Collapse all** opens or closes every step. Steps that need attention open by themselves. For each step you can change:

- **Action.** Go to page, click, type text, choose option, scroll, hover, wait or highlight.
- **Selector.** How the browser finds the element. Role, label, text and test ids are steadier than CSS.
- **Fallback selectors.** Up to five, tried in order if the main one finds nothing.
- **Value.** What to type or choose, or the path or https address to open.
- **Narration.** What the agent says while the step runs. Keep it to one sentence. The agent starts speaking as the step starts. Narration TalkDemo wrote for you (for steps sent from the Recorder or the API without any) shows an **AI draft** badge on the step's row. Read it, and change it if it isn't how you would say it: the badge goes as soon as you edit the text, and stays gone once you save.
- **Settle time.** How long to wait for the page before the next step.

### Promote a fallback selector

When the main selector of a step wasn't found in each of the last 3 successful replays and the same fallback worked every time, the step shows **Selector to promote** and a note naming that fallback. Click **Promote this selector** (Admins and Members): the fallback becomes the first selector tried and the old one takes its place as a fallback. The change is saved at once, recorded in the activity log, and starts the flow's health history afresh. Save or undo other edits to the steps first; the suggestion hides while you have unsaved changes.

You don't have to open each flow to find these. On the **Flows** list, a flow with suggestions shows a line such as **2 selectors to promote. Open the flow to review.** under its name. Archived flows don't show it.

Move steps with the arrows on their row, or focus a step's row and press Alt with the up or down arrow. Remove the ones you do not need, then click **Save steps**. Saving starts the flow's health history afresh.

When the steps are right, click **Mark active**. It is off while the flow has no steps or a step still shows a **Needs a review** note.

## Preview a flow

Check a flow before prospects see it, in two ways:

1. **Preview.** Press the eye icon on the flow's row in the **Flows** list, or **Preview** at the top of an open flow. A storyboard shows the flow as saved: step 3 of 10, the screenshot taken when the step was recorded (or "No screenshot for this step"), what the step does in plain words (for example "Click: Edit Profile"), what the agent says, and any review note. Use **Previous** and **Next**, the left and right arrow keys, **Play** (one step every 3 seconds) or the strip of steps to jump. Typed values that could be secrets are never shown. Viewers can preview too.
2. **Run in test console** (Admin, Member). Opens the **Test console** with the flow queued. Press **Start the demo** in the call: the agent says "Let me run …", runs the flow in the real browser on your demo tenant, with the same guardrails as a demo, narrates it, then asks what you'd like to see next. You see each step in the live activity beside the call. This works for drafts as well, so you can test a flow before you mark it active. Test calls are never billed or counted. **Test without it** on the Test console starts a normal test call.

Preview and Run in test console use the saved steps. Save your changes first to try them.

## Sign-in and secrets

Never put a real password in a flow. Sign-in is a separate set of login steps on **Product**, filled from the sealed demo login before the screen is shared. A flow value that contains `{{` is refused, and an imported recording has its sign-in steps and secret-looking values removed.

**Privacy:** record flows in your demo tenant with sample data only, so no real person's details end up in a flow.

## Frequently asked questions

### How many flows should I record?
Start with the 10 to 20 paths prospects ask about most.

### What if a prospect asks for something no flow covers?
The agent clicks through it live on the screen, one step at a time, within the same guardrails as a flow: only pages on your allowed hosts, nothing your blocked actions name, and no typing outside search boxes in read-only mode. It stops after a few steps or about 15 seconds and says so plainly when it can't find something, then offers a flow it can show. Add a [screen](/help/product-and-flows/screen-catalogue) or record a flow for the asks that come up often.

### What if a step fails during a demo?
The browser tries the fallback selectors, and when one keeps working the step suggests promoting it. If none works, the agent recovers verbally and shows another way. See [Flow health and broken flows](/help/product-and-flows/flow-health-and-broken-flows).
