Dashboard OverviewCopy link to this section

The Floe dashboard is where you configure everything: your products, the AI agent's knowledge, demo settings, and session intelligence. Here's what each section does and when you'll use it.

SitesCopy link to this section

Sites are the top-level container. Each site represents one product or application. When you open the dashboard, you land on the Sites list.

Click into a site to access everything related to that product: content, knowledge, and demo sessions. If you manage multiple products, each one gets its own site. See Sites for details.

IngestionCopy link to this section

The Ingestion tab inside a site is where you add content sources. This is how Floe learns what your product does.

You add configs pointing to your docs, knowledge base, videos, and other content. Each config shows its processing status (pending, processing, completed, failed). Most teams start with their docs site and expand from there.

See Ingestion for supported content types and configuration.

ContentCopy link to this section

The Content tab shows what Floe has ingested and indexed. It's the library of everything the AI agent can reference during conversations.

Use this tab to verify that your content was processed correctly. You can see individual articles, their source URLs, and when they were last updated. If the agent says something inaccurate during a demo, this is where you check whether the source material is correct or needs updating.

Product KnowledgeCopy link to this section

The Product Knowledge tab has two kinds of knowledge. Generated tabs show what Floe's research extracted from your content: topics, features, workflows, FAQs, and insights. Reference guides holds short facts your team writes directly, such as pricing, support, or policy details.

Reference Guides are available whether or not research has run. A Ready guide grounds answers from both the Demo and Website agents, but it never becomes a walkthrough or navigation instruction. Owners and Admins can create, edit, and delete guides; Members can read them. See Reference Guides for limits and details.

Demo contextCopy link to this section

Floe prepares the capabilities and guided workflows the agents use as part of demo setup. Each capability describes a user action, such as "Create a survey" or "Invite team members".

Capabilities drive what the AI demo agent shows and what the onboarding automation agent helps users complete. After you change source content, re-run ingestion, then ask us to refresh the generated context; that refresh is not automatic. See Capabilities and Plans for how Floe uses that context.

Demo SessionsCopy link to this section

Demo Sessions is the record of saved sessions for this site. It opens on Demos, which contains direct product demos. Use Website Agent to review sessions that started in the website agent, or All to see both together. Each row is labelled by where it started — Demo, Website Q&A, or Website → Demo — so separate starts are not presented as pieces of one recording. Sessions recorded before Floe labelled their source show as Website Agent or Legacy.

Because these records contain prospect identity and conversation content, the session list, details, recordings, and transcripts require conversation access, which organization owners and admins have by default. Members can still view aggregate session statistics and trends.

You don't start a demo from here. Demos begin when a prospect opens a demo link — created under Demo Agent → Demo Links — or when a website-agent conversation hands off into a live demo. This section is the history of those sessions.

After a session ends, you can review:

Video replay when the product was shown, or audio replay for a voice conversation that never opened the product screen
Conversation transcript with timestamps, with each visitor turn marked Voice, Typed, or Form
The pages the agent visited during the demo
Buying signals the prospect expressed
Questions the prospect asked, and the objections they raised
Session duration and completion status

A session that is still processing, one that ended before anyone said anything, and content removed under retention are each labelled as such, so an empty transcript is not mistaken for a broken one.

This data feeds your sales team's follow-up. See Product Insights for what is captured and what reaches your inbox automatically.

Finding a sessionCopy link to this section

The list loads the most recent sessions first, a page at a time — Load more at the bottom fetches the next page, and the line above the list tells you how many you have loaded out of how many match.

To narrow it down:

Search matches the prospect's name, company, role, and the session summary. It searches every session on the site, not just the ones already loaded, so a prospect from months ago is one search away. It does not search by email address.
Status filters to completed, abandoned, active, or pending sessions.
Last 7 / 30 / 90 days limits the list to recent sessions.
Recorded shows only sessions that still have a recording you can play. Recordings are deleted on the retention schedule, so older sessions drop out of this filter while their summary and signals stay.

Filters combine. They do not change the four counters at the top of the page; the Demos / Website Agent / All source selector does.

InsightsCopy link to this section

Insights opens with the visitor outcome overview: how many distinct visitors reached Floe in the selected 7-, 30-, or 90-day window, and how many of them opened the agent, asked a question, shared an email, took a demo, and booked a call. Select any number to see the records behind it. Below that, Questions groups what prospects asked and Trends shows demo volume and completion.

See Product Insights for how each outcome is counted and who can open which records.

IntegrationsCopy link to this section

Site → Integrations brings scheduling, CRM, and post-demo delivery together: recap emails, Slack and Teams notifications, the HubSpot or Salesforce connection and its contact-delivery policy, and your booking setup — either a connected Cal.com or Calendly account or a custom HTTPS booking link, including Schedule Hero. Custom links can explicitly pass the prospect's email with an {email} query value. See Integrations.

Website AgentCopy link to this section

Website Agent → Configure sets up the top-of-funnel Ask Floe surface — the Q&A launcher and scroll nudges that run on your marketing site and hand off to a live demo.

Site Settings → Agents holds the on/off switch. Configure covers identity capture, opener suggestions, display mode, the live-demo hand-off, and the video avatar. Scroll nudges have their own page at Website Agent → Nudges, where you edit each page's copy or switch it off. See Website Agent Setup for the full walkthrough.

Website Agent → Conversations lists every stored website-agent thread. Search by visitor name or email, filter by status or recent activity, and open a conversation to read its transcript, citations, agent actions, summary, topics, and outcome. An email or phone the visitor shared is shown on the detail page with its status. Conversations and the matching Demo Agent → Sessions details require conversation access. A conversation whose content has expired under retention keeps its metadata and shows a removal notice in place of the messages.

RecordingsCopy link to this section

Onboarding Agent → Recordings lists recordings of onboarding and support sessions that ran inside your product. Open one to replay the session and read its transcript.

These are records of what the agent did with a real user, not authored content — you don't create them, and editing them isn't a thing. Whether they are captured at all is a property of your deployment; see Security & Privacy.

PeopleCopy link to this section

People is the record of the visitor identities your agents have talked to, across all three agents. Each row carries the available name, company, activity count and last-seen date, and you can add, edit and delete records directly.

People records contain visitor identity, so they require conversation access. A visitor may appear with a user ID your application provided or only with an anonymous browser identifier. A browser identifier is a continuity aid for that browser, not proof of a person; treat records without a customer-provided user ID as visitor records rather than authenticated accounts. An email a visitor shared with the Website Agent or Demo Agent stays attached to that conversation; Floe does not merge it into a People record on its own. A record you add by hand needs both a user ID and an email.

Deleting a People record erases its visitor, conversation, event, recording, and demo data. If the record's email came from your own system, the same request also erases that address across the site. See Data deletion.

The All, Identified, Engaged anonymous, and New segments separate known contacts from visitors who have engaged without identifying themselves. On large sites the page says when counts or search cover only the records loaded so far.

This is your view into the user onboarding funnel at the individual level.

Visitor data controlsCopy link to this section

Open Site → Settings → General → Visitor data collection to control the data behind the Website Agent and Insights:

Turn visitor analytics events and nudge telemetry on or off. Turning them off also pauses conversation summaries; the agents and live conversations keep working.
Turn Website Agent transcript recording on or off. When it is off, visitors can still chat, but no transcript appears under Conversations and no summary can be generated. Demo recordings are controlled separately.
Set raw-event retention from 30–730 days (365 by default) and conversation-content retention from 7–365 days (90 by default). The conversation window also covers email and phone details shared with either agent.

See Security & Privacy for what each switch changes and what remains after a retention sweep.

Organization and TeamCopy link to this section

Two entries at the bottom of the sidebar sit outside any single site:

Organization — your organization's name and settings.
Team — invite people to the dashboard by email. Invitees pick a password and land in your organization when they accept.

Roles are Owner, Admin and Member. Owner and Admin can change sites and settings, invite, remove or re-role members, manage Reference Guides, and read everything that carries a visitor's identity or words: People records, transcripts, session details, and the Insights records behind Asked a question, Shared email, and Took demo. Members can view every count and trend, read Reference Guides, and browse non-sensitive site pages, but cannot see those records or change a site's configuration.

One thing to be aware of when inviting people: everyone in the organization, Member included, can read a site's API keys under Settings → Developer Keys. Treat organization membership as trusted access.

API keys are per-site, not per-organization — see Sites.

Connected appsCopy link to this section

Organization settings → Connected apps lists the AI tools you have connected to this organization over Floe's MCP server — Claude Code, Claude Desktop, claude.ai, ChatGPT or Cursor — with the access each one holds and when it was last used.

You see and revoke your own connections. A connection is one member's authorization of one tool, so a colleague's connections are theirs to manage. Revoking one stops it working within a minute.

A connection's access can never exceed your own role, and it reaches only the organization you chose when you approved it.

The dashboard follows a consistent pattern:

Sites list is the home screen
Click a site to see its available sections, including Ingestion, Content, Product Knowledge, and agent-specific views
Click a tab to see that section's content
Click an item (such as a content source or demo session) to see its details

Most work happens inside a site. You pick the site you're working on, then move between tabs as needed. The sidebar stays visible so you can jump between sections without going back to the list.

Getting startedCopy link to this section

If you're new to the dashboard:

Start with the Quickstart to create your first site
Add content via Ingestion
Floe prepares the generated demo context
Launch your first demo session

FAQCopy link to this section

Can multiple team members use the dashboard? Yes. Invite them by email from Team in the sidebar. Everyone in the organization sees the same sites and data. Note that an invitation has to be accepted by someone who doesn't already have a Floe account — if they do, talk to us.

Is there a way to search across the dashboard? Each available section has its own search or filter. Content is searchable by keyword, and agent-specific views provide their own filters.

How do I know if my site is fully set up? A fully set up site has at least one ingestion config completed and generated demo context prepared before you launch a demo.