# Recorded demo flows: show the important paths the same way every time

> Recorded demo flows are the paths through your product that your team records once, such as creating an invoice or building a report. TalkDemo stores each step with a screenshot and narration notes, and the agent replays the right flow when a prospect asks, narrating as it clicks. Flows make live demos dependable. You can import a recording, have Claude Code draft flows, or edit them in the dashboard.

Source: https://talkdemo.com/features/recorded-flows · Updated 2026-11-19

## Key takeaways

- A solutions engineer records 10 to 20 core flows once during setup.
- Each step keeps its selector, a screenshot and narration notes.
- Replay is deterministic, with fallback selectors when the page shifts slightly.
- Import a Playwright or Chrome DevTools recording, or let Claude Code draft flows; or click through it with the TalkDemo Recorder for Chrome.

## Why recorded demo flows beat improvising

An AI that clicks around a product it has never seen is slow and sometimes wrong. A path someone recorded is fast and predictable. TalkDemo uses both, in that order: flows for the parts of the demo that matter most, and live clicks only for questions no flow covers.

Flows also keep the story yours. The narration notes on each step carry the point your best AE makes on that screen.

## Recording a flow

1. Name the flow after the buyer's goal, for example "send a payment reminder".
2. Record the path once: import a Playwright or Chrome DevTools recording, let Claude Code draft it, or click through it with the TalkDemo Recorder for Chrome. Each step saves the element and the page address.
3. Add a sentence of narration per step and the questions buyers usually ask there.
4. Replay it in the test console and fix any step that lands in the wrong place.

## Keeping flows healthy after releases

Product teams ship, and recorded steps can break. Every replay in a real demo is counted: when a flow fails at the same step three replays in a row, it is marked broken and your admins get an alert. Automatic re-scans when you deploy, self-healing steps and flows proposed from a crawl of your product are on the roadmap.

## Frequently asked questions

### How many flows do we need?

Most products are covered by 10 to 20 flows: one per buyer goal you show in a first demo. Start with the five that appear in every sales call.

### Who records the flows?

Solutions engineers or product marketers, in the dashboard, and in pilots we help. Every new flow arrives as a draft that a person reviews before prospects see it.

### Do flows work in slide mode?

No. Slide mode uses your deck or screenshots as steps. Recorded flows belong to live product mode on Growth and above.

## Related pages

- [Live product mode](https://talkdemo.com/features/live-product-mode)
- [Guardrails and demo tenants](https://talkdemo.com/features/guardrails-and-demo-tenants)
- [What is demo automation?](https://talkdemo.com/glossary/demo-automation)
- [All use cases](https://talkdemo.com/use-cases)
