Home / Docs / Website Agent Setup

Website Agent Setup

The website agent shares the demo agent's knowledge, so setup builds on the same foundation: a site, ingested content, and exploration. Once those are in place, you enable the website agent and shape how it behaves from your site settings.

Prerequisites

The website agent answers from the same knowledge as the demo agent, so it needs the same groundwork:

  1. Site created — a site pointed at your product. See Sites.
  2. Content ingested — your docs and knowledge base, so answers are accurate. See Ingestion.
  3. Exploration and capabilities — needed for the live-demo hand-off to drive your product. See the Quickstart.

If you only want top-of-funnel Q&A (no demo hand-off), content is the essential piece — that's what answers are grounded in.

Enabling the website agent

The website agent is off by default. Turn it on in the Website Agent section of your site settings. Once enabled, the configuration below becomes available.

Configuration

All of the following live in the Website Agent section of your site's settings in the dashboard.

Identity capture

By default the agent engages anonymously — a visitor can ask questions with no email. If you want to collect an email (and optionally name and company), turn on Identity capture and choose when to ask:

  • Never (anonymous only) — never prompt.
  • When the chat opens — ask up front.
  • After N questions — let the visitor get value first, then ask (you set N).
  • When they want a demo — only ask at the point of demo intent.

Capture is inline and never blocks the first answer. Once a visitor shares an email, their earlier anonymous activity is linked to it.

Scroll nudges

Nudges are the short, contextual prompts the agent surfaces as a visitor scrolls. Floe generates a starting set from your content, prioritizing buying-intent pages, but you own every one. Each nudge has:

  • Page (e.g. / or /pricing) — the nudge only fires on this page.
  • Topic — a short label for what it's about.
  • Bubble copy shown to the visitor — the one line the visitor sees.

Toggle an individual nudge with Show this nudge, or use Enable all nudges on this page / Disable all nudges on this page to control a whole page at once.

Opener suggestions

Opener chips are the suggested questions shown when the chat first opens. Leave them empty to use sensible defaults derived from your product content, or add your own to steer visitors toward the questions you most want to answer. (Follow-up suggestions after each reply are generated automatically from the conversation and don't need configuring.)

ICP personas

Give the agent your ideal-customer profile so it can tailor answers and qualify visitors. Add personas with a Persona name (e.g. "VP of Engineering") and their Pain points. These feed the same qualification the demo agent uses.

Offer a live demo

The live-demo hand-off is on by default: when a visitor asks to see the product, the agent transitions the session into a live demo. Turn Offer a live demo off to keep the website agent Q&A-only, or set the label on its call-to-action.

Video avatar

Optionally front the chat with a talking-head Video avatar. Off by default.

Embedding on your site

Add Floe to your marketing site with the Browser SDK and turn on website-agent mode:

<!-- 1. Load the SDK (allow https://cdn.floe.so in your script-src) -->
<script src="https://cdn.floe.so/floe-sdk.iife.js" defer></script>
<!-- 2. Initialize from your own script — no inline JS, so it works under a strict CSP -->
<script src="/floe-init.js" defer></script>

// floe-init.js — served from your own origin
Floe({
  clientKey: "YOUR_CLIENT_KEY",
  websiteAgent: true,
  demoSiteId: "YOUR_SITE_ID",
});

Both scripts are external and deferred, so they run in order after the page parses — floe-init.js calls Floe() only once the SDK has loaded, and nothing is inlined, so this works under a strict Content-Security-Policy. websiteAgent: true renders the Ask Floe launcher and its nudges; demoSiteId is the site the live-demo hand-off starts, so include it to keep the default hand-off working. demoMode and websiteAgent are mutually exclusive — a single embed runs one or the other. See the Browser SDK reference for all options.

Verifying your setup

  1. Load a page where you've embedded Floe. The Ask Floe launcher should appear.
  2. Open it and ask a question you know your content covers — confirm the answer is accurate.
  3. Ask about something you haven't documented — confirm the agent declines honestly instead of guessing.
  4. Scroll a page with a nudge configured and confirm the prompt appears.
  5. Ask to see a live demo and confirm the session hands off into the driven product.

If answers are thin or wrong, check the Content tab — the fix is almost always more or better ingested content, then a re-ingest.

FAQ

Do I need a separate integration for the website agent and the demo agent? No. It's one SDK embed. websiteAgent: true runs the top-of-funnel Q&A that hands off into the demo; demoMode: true runs the demo directly.

Where do the nudges come from? Floe generates a starting set from your ingested content, weighted toward buying-intent pages. You then edit, add, or disable them per page in the dashboard.

Can I run the website agent without the live-demo hand-off? Yes. Turn off Offer a live demo and it stays a grounded Q&A surface.

How do I update what the agent knows? Update your content and re-run ingestion. The website agent and demo agent both answer from that refreshed knowledge.