Demo AgentCopy link to this section

The demo agent is your AI demo agent. A prospect clicks a link, joins a video call, and watches an AI navigate your real product in a live browser while having a natural voice AI conversation.

How it worksCopy link to this section

1. Prospect clicks a demo link and lands on a branded page
2. The AI agent launches a real browser with your product loaded
3. Video call starts with the prospect seeing the live product via screen share
4. Voice conversation begins: the agent greets the prospect and asks about their role and pain points
5. The agent navigates your product based on the prospect's interests, using what it learned from your content and screens
6. Post-session intelligence captures what was asked, what resonated, and buying signals

The entire demo runs without human involvement. No sales engineer needed. Available 24/7, in every time zone, in English or Hindi.

A demo can also begin as a question. The website agent answers a visitor's questions on your marketing site first, and when they ask to see the product it hands off in place — the same session becomes the demo described here, with no navigation away or second form.

When a prospect starts a demo from the same embedded Floe experience after an earlier Website Agent conversation, the demo may use retained context from that browser to avoid repeating discovery, subject to visitor-data and consent settings. The demo remains attached to that exact browser source. An email the prospect supplies is a contact claim for this interaction, not a person merge, and it does not pull conversation or demo context from another browser. When consent produces no browser token, the claim stays attached to that demo session without creating a browser identity just for continuity.

Real browser, not slidesCopy link to this section

The agent controls a real browser running your actual product. It clicks buttons, fills forms, navigates menus. Every action is real. The prospect sees their use case being configured in real time, not a pre-recorded walkthrough.

This means the agent handles live questions. "Show me the reporting dashboard" causes the agent to actually navigate there. "What happens if I invite 50 users?" triggers a real explanation with the actual UI visible.

Voice conversationCopy link to this section

The AI uses natural voice conversation, not text chat. It talks like a human SE: warm, knowledgeable, adaptive.

The prospect talks back naturally. They interrupt, ask tangent questions, express confusion. The agent handles all of it in real time. No scripts. No pre-recorded responses.

During an autonomous guided browser sequence, each guide beat either advances the product or ends with one short, relevant question. Direct answers to a prospect's question can stop after the answer. Broad requests such as integrations or reporting can begin with one narrowing question; when the prospect names a specific provider or report and a guide exists for it, the agent follows that specific guide instead of wandering through the broader menu. On-screen highlights and answer choices stay with the spoken guide beat they support. Chained responses within one guide do not repeat an already-spoken question, while a different guide keeps its own intentional closing question.

Knowledge from your contentCopy link to this section

The agent's product knowledge comes from your content. After you've added content via ingestion and created a site, Floe learns your product inside and out: what features exist, how they work, what screens to navigate to, and what matters to different types of users.

When a prospect asks about a feature, the agent draws on this knowledge and navigates to the right screen while explaining it in context.

Session intelligenceCopy link to this section

Every demo session captures:

• Transcript: full conversation with timestamps
• Features shown: which parts of your product the agent actually demonstrated
• Pages visited: where the agent navigated during the demo
• Buying signals: moments the agent judged significant, written as observations
• Questions and objections: what the prospect asked, and what gave them pause
• Session duration and completion

This data feeds directly to your CS and sales teams, and can be delivered to your inbox, Slack, or CRM automatically. See Product Insights and Integrations.

When source-bound email capture is enabled for your deployment, the prospect recap can include Schedule a follow-up and Not you? actions. Scheduling from the same consented browser source can confirm only that claim; scheduling from another device still opens the booking destination without merging visitor history or confirming the address. Floe never appends the prospect's contact details to the booking URL. See Prospect recap email.

Getting startedCopy link to this section

1. Create a site for your product
2. Add content so Floe can learn your product
3. Wait for the site to reach Ready in the dashboard — that's when the agent has enough context to demo
4. Create a demo link under Demo Agent → Demo Links and send it to a prospect

For the full setup flow, see the Quickstart.

FAQCopy link to this section

How long is a typical demo? Around 15 minutes is typical, and the agent adapts to the prospect's pace rather than working to a clock. A session ends on its own after a few minutes of silence from both sides, and there is an upper bound on any single session, so a very long demo can be cut short.

Can I customize the agent's personality? Yes — you pick a persona preset, or write your own tone, and choose the voice. See Demo Agent Customization.

What if the prospect wants to talk to a human? The agent offers your booking link so they can put time in with your team, and the recap that follows gives whoever takes that call the full context. It cannot transfer a prospect to a live person mid-session.

Does the demo agent need access to a real account? The agent runs against a configured instance of your product. You control what data is visible during demos.