Website Agent

The website agent is Floe at the top of the funnel. Before a visitor is ready for a full demo, a launcher pill — Ask Floe — sits on your marketing site and answers their questions, grounded in your product. When they ask to see something live, the same agent hands off in place to a live demo. No new tab, no form, no wait.

It runs on the same session as the demo agent. A visitor can start by typing a question and finish by watching the agent drive your real product — one continuous conversation.

Answer questions before the demo

Not every visitor is ready to sit through a demo. Most have a question first: "Does this integrate with Salesforce?", "How is this different from Storylane?", "What does setup involve?"

The website agent answers those questions right on the page. A visitor clicks the Ask Floe launcher, a chat opens, and they get an answer drawn from your documentation and product content — the same knowledge that powers the demo agent. It's the top-of-funnel conversation that used to require a rep or a form.

Grounded answers, honest about gaps

Answers are grounded in your ingested content. When the agent is confident, it answers. When it isn't — when a visitor asks about something you haven't documented — it says so and offers to connect them, rather than inventing an answer. A confidence gate sits between the question and the reply for exactly this reason: a wrong answer on your marketing site is worse than an honest "I don't have that detail."

This is the same grounding discipline as the demo agent. The agent only speaks to what it learned from your content and product.

Contextual nudges as they scroll

As a visitor moves through a page, the website agent can surface a short, contextual nudge tied to the section they're reading — a one-line prompt like "Curious how scoring works? Ask me." Nudges are page-scoped: each one belongs to a specific page and section, so the prompt matches what's actually on screen, and follows the visitor as they navigate your site.

Nudge copy is generated from your content and prioritizes your buying-intent pages (pricing, product, comparisons). You control every nudge from the dashboard — edit the copy, or switch a page's nudge off entirely. See Website Agent Setup.

Type or talk

The chat opens muted — the visitor can simply type their questions, no microphone required. If they'd rather talk, they can unmute and have a voice conversation instead. Either way it's the same agent and the same session; the visitor chooses the modality that fits where they are.

Answers render as formatted text — lists, links, and emphasis — so a multi-part answer stays readable in the chat.

Hand off to a live demo, in place

This is what separates the website agent from a support chatbot. When a visitor asks to see something — "Can you show me?" — the agent doesn't dead-end at text. It transitions the same session into a live demo: it opens your real product in a driven browser and the chat widens into a demo, with the live product on one side and the conversation on the other.

There's no navigation away, no second form, no scheduling. The question becomes a demo in one continuous flow. From there it's the full demo agent: voice-led, driving your real UI, qualifying against your ICP.

You can turn the demo hand-off off, or set the label on its call-to-action, from the dashboard.

Know your visitors

Every visitor is attributed from their first question with an anonymous ID — no email required to start. If you choose to, the agent can ask for an email (and optionally name and company) inline, at a moment you configure: when the chat opens, after a couple of questions, or only when the visitor shows demo intent. Capture never blocks the first answer, and once a visitor shares an email their earlier anonymous activity is linked to them. See Security & Privacy for how this data is handled.

Which nudges get shown and clicked is tracked so you can see what's drawing interest across your site.

How it's different from a chatbot

A support chatbot answers text from a static knowledge base and stops there. The website agent:

Is grounded and honest — it answers from your product content and declines when it doesn't know, instead of guessing.
Is proactive — it surfaces contextual nudges tied to the page a visitor is on, rather than waiting to be opened.
Ends in a demo, not a transcript — when the visitor is ready, the same agent drives your real product live. The chat is the on-ramp to the demo, not a replacement for it.

Getting started

The website agent shares its knowledge with the demo agent, so setup builds on the same foundation:

Create a site for your product
Add content so Floe can answer accurately
Enable and configure the website agent — see Website Agent Setup
Embed Floe on your marketing site with the Browser SDK

FAQ

Can it answer questions before starting a demo? Yes — that's its main job. The Ask Floe launcher answers questions right on your marketing site, grounded in your product content, before a visitor commits to a full demo.

Does it show contextual nudges as I scroll? Yes. Nudges are page-scoped and section-aware: as a visitor reads, the agent can surface a short prompt tied to what's on screen. You control the copy and can turn any page's nudge off.

Can it hand off to a live demo in place? Yes. When a visitor asks to see the product, the same session transitions into a live demo — the agent opens your real product in a driven browser and the chat widens into a demo. No new tab, no form.

Is the website agent the same as the demo agent? They're two phases of one agent on one session. The website agent handles the top-of-funnel Q&A; when the visitor is ready it becomes the demo agent and drives your product. Same knowledge, same conversation.

Do visitors have to talk? No. The chat opens muted, so a visitor can type. Voice is there if they want it — they can unmute at any time.

Does the chat remember a visitor across visits? A returning visitor is recognized by their anonymous ID, and once they've shared an email they're linked to it. The chat transcript itself starts fresh each session.