Demo Agent CustomizationCopy link to this section

The demo agent adapts to your product, your buyers, and your go-to-market motion. Out of the box it runs a solid demo; customization is what makes it feel like your SE rather than a generic AI.

Everything on this page lives under Demo Agent → Configure in the dashboard, plus two shared settings under the site's Settings. Each card saves on its own, and changes apply to new demo sessions immediately.

Persona & toneCopy link to this section

The persona controls how the agent comes across: its identity, its tone, how long its answers run, and how briskly it moves.

• Preset — Warm Guide is the default: patient, informative, generous with signposting. Witty Peer is informal with tasteful humour. Crisp Expert is professional and concise with minimal filler. Or write a custom tone of up to 500 characters — "always explain features in terms of time saved", "keep explanations short and pause for questions".
• Identity — an optional description of who the agent is, up to 120 characters.
• Answer length — defaults to Medium.
• Pace — defaults to Brisk. Slower paces are for surgical emphasis, not the baseline.

The voice the session actually uses is chosen on the Languages & voices card, not here. See Languages & Voices.

Discovery & openingCopy link to this section

Discovery is what the agent asks early in the session to understand the prospect's needs, similar to a discovery call. Good discovery makes the rest of the demo feel personalized: if the prospect says they're struggling with user activation, the agent leans on features related to activation and time to value; if they mention a large team, it highlights admin controls and permissions.

• Framework — None (the default), BANT, MEDDIC, MEDDPICC, Challenger, SPIN, Sandler, Gap Selling, or a custom framework of up to 2,000 characters.
• Qualification questions — up to eight, 240 characters each. The agent weaves them across the demo and asks at most one before showing the product, so discovery never feels like an interrogation.

Discovery answers also feed the session's prospect profile and the recap your AE receives.

Ask for their detailsCopy link to this section

Identity capture decides which details the agent asks for and when. Select at least one of name, phone, email, company, and role, and use each field's Required checkbox to decide whether the prospect can decline it. When phone is selected, choose a Phone region so a number given without a country code can be interpreted.

Before the demo starts is the default. The prospect fills in a short form before the session begins. It always asks for email and name, adds phone if you selected it, and required fields must be completed to start.

The other timings — After the intro, After the first feature, and When a full walkthrough is requested — collect details in conversation instead:

• The agent asks for one detail at a time and skips anything already known — from a demo link, the start form, the SDK's userInfo, or an answer earlier in the same session.
• A spoken phone number or email appears in the message box for the prospect to check or correct before it is kept.
• Each detail is asked for once during the demo. A declined detail is not asked for again until the demo wraps up, when the agent may ask one more time for one declined detail; a second decline is final. Declining a Required detail does not stop the conversation; in the website agent, an unanswered required detail holds the hand-off into a live demo.
• Each detail can also have its own moment. Leave a field on Same as above to follow the card's timing, or give it one of the conversational moments — including At the end, which asks as the demo wraps up. So you can take a name after the intro and leave the email until the prospect has seen the product.

A phone number the prospect confirmed in conversation is labelled Prospect-confirmed in the dashboard and recaps; one supplied by the form or a demo link is Stated. Neither label verifies ownership. Which contacts are written to your CRM is set by the CRM delivery policy.

Choosing Never turns off the card's default moment, not the card. A detail you gave a moment of its own is still asked at that moment; to stop the agent asking for anything, turn the whole card off. When your site uses pending consent, conversational asks wait for a grant; see Consent gating.

Opener chipsCopy link to this section

Opener chips are the one-tap starting points shown when the demo connects. Add, reorder, or remove up to six (100 characters each), or leave the list blank and Floe derives suggestions from your guides.

Languages & voicesCopy link to this section

Pick which languages this agent speaks and the voice for each. English only unless you enable Hindi. See Languages & Voices.

Shared site settingsCopy link to this section

Two things that shape every demo live in the site's Settings rather than on the Configure page:

• Logo, accent colour, and the booking CTA are shared across all agents and appear in the demo surface and the recap emails.
• Pronunciation fixes how the agent says product names and acronyms. It applies to English sessions. See Pronunciation.

Per-prospect contextCopy link to this section

When you create a demo link, you can add the prospect's name, work email, phone, company, and role, override the booking link, and set an expiry. The agent skips details the link already supplies and uses that context to personalize its opener and frame the demo around the prospect's company and role; without it, it starts broadly and adapts to what the prospect asks. See Creating and publishing a demo link.

Editing what the agent says about a featureCopy link to this section

The guide is the script the agent follows for a single feature or walkthrough. Open Demo Agent → Guides and expand a guide to read it. Edit opens the content editor; Save publishes the change, and Cancel discards your draft. Hand-edited guides are preserved when Floe regenerates guides.

You can also read and rewrite guides from your own AI tool over Floe's MCP server:

Read the guide for the "reporting" topic, then rewrite what it says
about the weekly summary so it leads with the number rather than the
filters.

See Writing a guide for the rules a guide must follow.

What's nextCopy link to this section

• Demo agent setup if you haven't configured the basics yet
• Demo agent overview for session intelligence and post-demo data

FAQCopy link to this section

Can I have different configurations for different buyer personas? Not as separate saved profiles yet. The agent adapts to the prospect context you attach to each demo link and to the discovery answers it collects during the session.

Can I stop the agent from discussing pricing or competitors? Put the boundaries in the custom tone ("do not quote prices; offer to connect them with the team") and give the agent the facts it should use instead via a Reference Guide. The agent answers from your content and declines honestly when it doesn't know rather than guessing.

What if the prospect asks a discovery question back? The agent handles reverse questions naturally. If the prospect asks "What do most companies your size use this for?", it answers from your content before continuing.

Can I see how customizations affect demo quality? When the session's consent and recording settings permit transcript capture, Floe stores a transcript alongside the engagement signals. Compare sessions with different configurations to see which produces better conversations and more buying signals.