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.

KnowledgeCopy link to this section

The Knowledge tab is where you review what Floe's research pipeline extracted from your content. It shows topics, features, and content coverage.

This is the "did Floe get it right?" checkpoint. If a topic shows low coverage or a feature needs more detail, you know where to improve your inputs before running demos.

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 (e.g., "Create a survey," "Invite team members") with details about where it happens and how involved it is.

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; generated context must be refreshed internally before a demo reflects the update. See Capabilities and Plans for how Floe uses that context.

Demo SessionsCopy link to this section

Demo Sessions is the record of saved sessions the demo pipeline ran for this site. It opens on Demos, which contains direct product demos and older sessions whose type predates the session label. Use Website Agent to review sessions that started in the website agent, or All to see both sources together. Each row is labelled Demo, Website Q&A, Website → Demo, Website Agent (when an older session has no recorded outcome), or Legacy so separate starts are not presented as pieces of one recording.

Because these records contain prospect identity and conversation content, the session list, questions, digest, individual 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 and Voice, Typed, or Form labels. An interrupted agent reply is marked rather than presented as fully played.
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

The transcript panel distinguishes a session that is still processing, a session that ended before either participant produced a transcript turn, and content removed under retention. Opening and closing the agent without engaging therefore remains an empty activity record rather than looking like a broken transcript.

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. Search, status, date, and recording filters do not change the four counters at the top of the page, so you can compare a filtered slice with the selected source. The Demos / Website Agent / All source selector does change those counters to match that source.

InsightsCopy link to this section

Insights starts with Floe's visitor outcome overview. Its top-line Visitors number counts distinct visitor identities in the selected window, then breaks that audience down by who opened the agent, asked a question, shared an email, and took a demo. Use the 7-, 30-, or 90-day picker to compare recent performance.

Select an outcome with supporting records to review the underlying activity. Below the overview, Questions groups the questions prospects asked and Trends shows demo volume and completion.

See Product Insights for the stage definitions and counting rules.

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 (when to ask for an email), opener suggestions, display mode, the live-demo hand-off, and the video avatar. When Video avatar is enabled, its card can upload, preview, replace, or remove the MP4/WebM idle loop used by the closed launcher; Floe hosts clips up to 10 MB, so you do not need a separate video host. 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. You can search by visitor name or email, filter by status or recent activity, and open a conversation to read its transcript, citations, tool actions, summary, topics, and outcome. When a visitor shared an email publicly, the list and detail show it as a source-bound contact claim with its status, separately from the visitor's identity. A complete email address performs an exact claim search; partial email fragments do not search encrypted claim data. These addresses and search results require conversation access. Migrated legacy addresses whose original source could not be proven are marked Quarantined legacy email and do not count as a shared-email funnel outcome. A retention-purged conversation keeps its metadata and shows an explicit removal notice in place of the old message content. Claim capture and these dashboard consumers are staged deployment capabilities and remain unavailable until Floe enables both for your deployment.

RecordingsCopy link to this section

Onboarding Agent → Recordings lists recordings of onboarding 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 and Website Agent transcripts contain visitor identity or message content, so they require conversation access. Organization owners and admins have that access by default; members can still view aggregate Insights.

A visitor may appear with a customer-provided user ID or only a browser identifier. An email shared through a public Website Agent or Demo Agent flow stays on that source conversation/session as a contact claim; Floe does not automatically merge it into a People record. A record you add by hand—or an anonymous record you identify manually—needs both a user ID and an email.

Deleting a People record erases its linked visitor, conversation, event, recording, and personal demo data. If its email is customer-provided, the same request also removes every retained source-bound claim for that exact address within the site and scrubs exact occurrences from otherwise separate surviving source records. It does not merge those browser histories before erasing them. A non-plaintext fence prevents delayed work from immediately restoring the address for the remainder of the site's applicable conversation-retention window. See Data deletion.

An anonymous browser ID provides continuity for that browser; it is not proof of a human identity. Treat records without a customer-provided user ID as visitor records rather than authenticated accounts.

The All, Identified, Engaged anonymous, and New segments help separate known contacts from visitors who have engaged without identifying themselves. For large sites, the page clearly indicates when counts or search cover only the visitor 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 Website Agent conversation-content retention from 7–365 days (90 by default). The latter window also deletes source-bound email claims from Website Agent and Demo Agent interactions; shortening it applies to existing claims on the next daily retention pass.

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 both change sites and settings, and invite, remove or re-role members. Members can view aggregate Insights and other non-sensitive site pages, but not People records or Website Agent transcripts, and cannot change or delete an existing site's configuration.

Owner and Admin views also show a visitor's source-bound shared-email claim and its current status on Website Agent conversation details and the matching Demo Agent session detail. Rejected, bounced, expired and superseded claims remain visible as evidence but are not rendered as contactable email links. Members do not receive this contact projection.

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.

The dashboard follows a consistent pattern:

Sites list is the home screen
Click a site to see its available sections, including Ingestion, Content, 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
The generated demo context is prepared internally
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.