Dashboard Overview

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.

Sites

Sites are the top-level container. Each site represents one product or application. If you manage multiple products, each one gets its own site. See Sites for details.

The site switcher at the top of the sidebar, under your organization's name, moves between your sites and, for Owners and Admins, offers Add new site. Creating a site takes you straight to its Home, which says what to do next. A new site starts with the Demo Agent and the Website Agent turned on.

Home

Once the site is set up and its Website or Demo Agent is on, Home shows the last 7 days: how many people booked a call, took a demo, shared an email and asked a question, each against the 7 days before when there is a week to compare with. Below them are the leads to follow up first, the sources that brought the most leads, and the questions that still have no answer; where you can add a fact, Add a fact sits beside the question. Insights has the same figures over longer ranges. A site with only the Onboarding Agent shows its recent sessions instead.

Settings → General holds the site's name and description; you can change either at any time.

Turning an agent on or off

The Demo Agent and the Website Agent each have an on/off switch on their Setup page, the first item in that agent's section of the sidebar. Turning one off takes it off your site at the next page load and keeps its configuration; while it is off, its pages show a button to turn it back on.

The Onboarding Agent is enabled by Floe as part of your plan, so its Setup page shows its state rather than a switch. If it isn't in your plan, its pages say so and offer Contact sales instead of a button to turn it on.

Leads

Leads, directly under Home in the sidebar, lists everyone who talked to your Website or Demo Agent, newest first, with each of their conversations and demos under them. Conversations and demos from the same browser, or that shared the same email address, are one person; shared and confirmed addresses both count. A conversation that went on into a live demo is one visit.

Each person shows their name (or Unnamed visitor), their email and company, their strongest signal with its reasons, and their lead score when available. Under them, each visit shows whether it was a Demo or a Chat, a one-line summary, when it happened, how long it lasted, and whether a recording is available; a visit still in progress is marked live. The newest three visits show first and the rest open on request. Select a person to open their newest visit, or select a visit to open it.

A lead is worth a call when their request is within what your product does and they did at least one of these, shown strongest first:

Booked a meeting through your connected calendar. A cancelled booking doesn't count.
Took a demo of your product.
Shared email or a phone number with the agent, marked confirmed when they confirmed it.
Asked to buy: raised buying questions or qualifying details, such as pricing, budget, a trial, or the problem they need solved. It is the same test Floe uses to decide whether a Website Agent conversation is sent to your team as a lead.

Everyone else appears under Everyone.

Because these records carry visitors' identities and words, the list, each conversation and demo, their recordings and their transcripts require conversation access, which owners and admins have. Members see a notice instead.

You don't start a demo from here. Demos begin when a prospect opens a demo link — created under Demo Agent → Demo Links, where each link has a name and shows the sessions and demos that started from it — or when a website-agent conversation hands off into a live demo.

Finding a conversation

The page opens on Worth a call for the last 30 days. The list loads a page at a time — Load more at the bottom fetches the next page, and the line above the list tells you how many people you have loaded out of how many match.

Worth a call, Live now (people talking to an agent right now) and Everyone, each with its count.
Search by name, company, what a conversation or demo was about, or a complete email address; partial addresses do not match. A search match shows the whole person. Search covers the chosen view and window, not just the people already loaded: to search everyone, choose Everyone, and All time under Filters.
Filters holds the rest: the agent (Website or Demo), the last 7, 30 or 90 days or All time, one signal (Booked, Took a demo, Shared email or Asked to buy), Recorded only for people with a recording you can still play, and the order. Newest puts the most recent activity first; By score puts the highest score first, and people without a score last. The button lists the filters that are on.

Filters combine, and the address keeps them, so a link opens the same list.

Reviewing a conversation

A visit opens beside the list with a short summary at the top, with the suggested next step when there is one (never for a visitor who left no email or phone). Under it, Details, closed until you open it, has the email and phone they shared, with their status (a phone the visitor gave the agent without confirming its country says so), the buying signals they expressed, the questions they asked, their pain points, interests and objections, and the topics covered. Then comes the recording: video when the product was shown, or audio for a voice conversation that never opened the product screen. When a conversation has more than one recording, the sessions are listed under the player, newest first, and you choose which one to play; a chat recorded by voice is marked Voice chat. Where available, the header shows the visitor's approximate location, and Details shows the page they arrived on. That page comes from page views, so it is left blank when visitor analytics collection is off, the visitor didn't consent, or the visit is older than your event retention.

Below that, these sections are closed until you open them, and a section with nothing in it is left out:

Transcript — the conversation, message by message. A demo opened on its own shows each turn's time, with each visitor turn marked Voice, Typed, or Form
Past conversations — this person's other conversations and demos, newest 50 first, with the total count. Each shows whether it was a chat or a demo, its own signal and its time, and opens its own record
What they did — the pages they visited, what the demo showed, and the pages the agent opened during it
Why this score — the visitor's lead score and why they are worth a call

A conversation whose content has expired under retention keeps its metadata and shows a removal notice in place of the messages.

This data feeds your sales team's follow-up. See Product Insights for what is captured and what reaches your inbox automatically. Links to a conversation or demo in recap emails and CRM notes open it here.

Owners and Admins can choose Delete this lead at the end of a conversation's Details and confirm the counts of conversations, demos and separately saved chats to permanently erase the whole lead. The demos’ personal content is removed; only records with nothing identifying remain, for counts. A demo or chat that belongs to no conversation also offers Delete this demo or Delete this chat, which removes only that one and its summary from your dashboard and leaves the rest of the person's record. It does not erase that demo's or chat's stored recording and transcript; to erase those, choose Delete this lead instead. For an email erasure request and how Floe prevents recapture, see Data deletion.

What they did is the lead's timeline, in the order it happened: where the visit came from (the referring site and the campaign), the pages they viewed, each with its title, how long they stayed, how much of the page they saw, the headings they stopped on and the links, buttons and forms they used, then the nudge they clicked, when they opened the agent and on which page, their first messages in their own words, and when they shared an email, took a live demo, clicked one of your custom links and booked a meeting. The visit the conversation began in is open; a visit is a run of activity with no break of 30 minutes or more. Earlier visits from the previous 30 days are collapsed above it, and what they did in the day after is shown below it. A long visit shows its first page and its most recent ones, and says so. What Floe reads from a page, and what it never reads, is listed under Security: What visitor analytics reads from the page. Where a visit came from, its pages, nudges, custom-link clicks, and the page the agent was opened on come from visitor analytics, so they are missing when collection is off, the visitor didn't consent, or the visit is older than your event retention. Messages need Website Agent transcript recording to be on. The other steps always appear.

Requests outside what your product does are marked Not a fit, with the reason, in Leads and team recaps. Leads lists them under Everyone, not Worth a call, and a scored one shows Cold with a score of zero; team recaps say Not a fit instead of a score or buying intent. The lead's most recent conversation or demo in which the visitor said what they were after decides whether it is Not a fit. A product question the agent cannot answer still goes to your team.

Lead score

After a conversation or a demo ends, Floe scores the lead from 0 to 100 and labels it Hot, Warm or Cold. The score has two parts:

Fit: how well what the visitor said matches your ideal customer profile. Floe checks three things: their kind of company, their role, and the problem they described.
Engagement: what they did. A booked meeting, a live demo and how far they took it, contact details they shared or confirmed, how much they said, buying questions, and, where visitor analytics is on, the pages they viewed, the time they spent, a visit to a pricing page, and return visits.

Open a lead and Why this score lists each fit check with what the visitor said behind it, where that is on record, and the engagement reasons, strongest first. The score is brought up to date when a meeting is booked or a contact detail arrives after the conversation.

When a visitor said too little to judge fit, or your profile is empty, the lead has no fit score: it is scored on engagement alone and is never Hot. A lead with nothing on record has no score. Website Agent conversations, including one that went on into a live demo, are not scored while Collect visitor analytics events is off. Leads that ended before scoring was available are unscored; Floe can score your last 30 days of leads on request.

The score also appears on the person's page, in your team's AE, Slack and Teams recaps, and on the CRM lead card. Recaps and CRM notes for leads marked Not a fit show that label instead of a score.

What the score never does:

It does not decide who is worth a call. That depends on what the visitor did and excludes leads marked Not a fit. A high score does not move a lead into a stronger signal.
It does not change the conversation. It is worked out afterwards, so the agent never mentions it and never treats a visitor differently because of it.
It never reaches the visitor. Their own recap email does not include it.

There is nothing to tune. To change what fit is judged against, edit your ideal customer profile. What is sent for scoring, and how long what the visitor said is kept, is covered in Security & Privacy.

Knowledge

Knowledge is everything your agents answer from, in one place. It is shared by all your agents and has five tabs.

Sources

Sources is where you add the places Floe reads: your docs, help center, changelog, videos, and PDFs you upload. This is how Floe learns what your product does.

Each source shows its status (Ready, Queued, Crawling, Failed, or Not crawled yet), how many pages Floe has from it, and when it was last crawled. When a source fails, the reason is shown under it. You can Re-run one source on its own, Edit its address, or Run all sources at once. A run in progress can be cancelled. Editing a source doesn't crawl it; re-run it to read it from the new address. Removing a source keeps the pages already read from it until you delete them in Library.

A run doesn't take your agents offline, and neither does one that fails: they keep answering from what Floe already has. The site's Home keeps showing its week, or its sessions, in the meantime, with a note that a refresh is running or didn't finish.

Automatic refresh runs all sources on a schedule you choose (Daily, Weekly, or Monthly) for a site with a documentation, knowledge base, changelog, or custom URL source. It is off until you turn it on. After a run, Sources shows how many pages were updated, new, back, or gone. See Keeping content up to date.

See Ingestion for supported content types and configuration.

Library

Library lists every page and document Floe has read, with the source it came from, its type, and its status. Search it, or filter by type. Use it to check that your content was read correctly: if the agent says something inaccurate, this is where you check whether the source material is right.

An item marked Flagged contains text that reads like instructions to an AI assistant. Filter by Flagged to review these, and delete any page you don't recognise.

An item marked Gone is a page Floe could no longer reach: your agents don't answer from it, and a later run that reaches the page again brings it back.

What Floe learned

What Floe learned shows what Floe's research found in your content: a summary, features, workflows, and FAQs, with a count for each, and when research last ran. Re-run research refreshes it and shows whether the run is queued or running, and how far along it is.

Owners and Admins can correct what research found: Edit replaces a feature's, workflow's, or FAQ's text with yours, and Hide takes an item out of the product knowledge your agents are given while keeping it in the list, marked Hidden from agents, with Unhide to bring it back. Each list says how many of its items are hidden. Members see what is hidden or edited but cannot change it. See Correcting what research found.

Facts

Facts holds Reference Guides: short facts your team writes directly, such as pricing, support, or policy details. They 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.

Gaps

Gaps lists, from the last 90 days, questions your agents couldn't answer and things visitors asked a demo to show that it didn't. Each question is checked against your knowledge and rewritten as a clear question; expand it to see the visitor's original wording and anything your knowledge already says. Questions that ask the same thing are grouped, most asked first. A new question shows its original wording until it has been checked. A demo's gaps come from its recorded conversation, so they appear after the demo ends and only when conversation recording is on.

Open holds questions that still need an answer, including ones your knowledge only partly answers. Already answered holds questions your knowledge answers, and Dismissed holds greetings and other noise. If the knowledge behind an answer changes or is removed, its questions return to Open until they are checked again. On a request a demo couldn't show, Demo guides opens the Demo Agent's guides.

Add a fact opens a new Reference Guide with the question as its title. Write the answer and save it: both agents can answer from it, and every question in that group moves to Answered. Hover over Answered to see which guide answers it. If you delete that guide, those questions are reconsidered.

Gaps quote what visitors said, so only roles that can read visitor conversations (Owners and Admins) see them. Members see a notice instead.

Links to the old Ingestion and Content pages open the matching tab.

Demo context

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, run your sources again on Knowledge → Sources or let Automatic refresh do it; when a run finds changes, Floe re-runs research. Capabilities and guided workflows are not rebuilt by a run: ask us to refresh them. See Capabilities and Plans for how Floe uses that context.

Media

Media is where you upload a slide deck and short videos for your Website Agent and Demo Agent to show visitors during a conversation. Clips of what a live demo can't show, such as your mobile app, work well.

Upload deck (PDF): up to 50 MB and 60 pages. Each page becomes a slide. Export PowerPoint or Keynote decks to PDF first.
Upload video (MP4): an H.264 MP4 up to 500 MB and 15 minutes. A short video becomes one clip; a longer one is split into chapters.

Each slide and clip has a one-line description of what it shows, and the agents choose what to show from it. Edit a description so it says what a visitor sees, and hide any slide or clip you don't want shown. The agents choose from up to 40 slides and clips that aren't hidden, earliest uploads first, so hiding items makes room for others. Deleting an upload removes it and everything made from it; recordings already made keep what was shown in them.

Demo Agent

Demo Agent → Setup says whether your demo is ready to share, and what to fix if it isn't: at least one live guide and a passing Product sign-in check, or, with Live product turned off, a product overview and a video or slide, of a kind you have turned on, to show. With Live product on and no demo tour live, it shows Owners and Admins the commands to build one with an AI coding tool. It also shows the embed snippet with your client key and site ID filled in. Configure → Show your product chooses what your demo shows: your live product, your videos, your slides, or any mix (see Choose what your demo shows). Guides marks which guides are Live; only live guides are offered to prospects as tours. See Demo Agent Setup.

Insights

Insights opens with the funnel: how many distinct visitors reached Floe in the selected 7-, 30-, or 90-day range, and how many of them deliberately opened the agent or clicked a nudge, asked a question, shared an email, took a demo, and booked a call. Each row shows its change against the previous period of the same length, and selecting a row opens the records behind it. Below the funnel, Where leads come from lists each source with its visitors and qualifying leads, counting each person once per source and column (a demo without visitor analytics or consent counts once per demo), and Pages how often the agent was opened, chatted with, and given a contact on each page. Leads lists the visitors with the strongest evidence in that range. What people ask groups what prospects asked in that range and lets an Owner or Admin add a fact when a question is also an open knowledge gap; In demos lists what demos showed most and what prospects asked to see that was not shown.

Conversations by country shows engaged conversations for each known country in the selected range. Conversations without a location are excluded, and a conversation that continues into a demo counts once.

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

Integrations

Site → Integrations brings CRM, scheduling, and recap delivery for both agents together, in the order you set them up: the HubSpot, Salesforce or Leadrat connection and your booking setup (a connected Cal.com or Calendly account, or a custom HTTPS booking link, including Schedule Hero), then recap emails and Slack and Teams notifications, then the CRM contact-delivery policy, then Factors. Each card with fields saves on its own. Custom booking links can explicitly pass the prospect's email with an {email} query value. Without a booking link, the Custom links card holds up to three links, such as Chat on WhatsApp, that the agents show in place of the booking button, with how often each was clicked.

The Delivery log at the foot of the page lists what Floe sent for each lead, where, and whether it went through, with filters for channel and outcome. Owners and Admins can read it. See Integrations.

Website Agent

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.

Email ownership, on either agent's Configure page, lets you turn on Verify emails that may not belong to the visitor and enter Competitor domains. These settings apply to both agents. See Ask for their details.

Website Agent → Setup holds the on/off switch, the embed snippet with your client key filled in, and Try it, which runs the agent over one of your pages before you install anything (see Try it before you install). Configure covers the presenter (video avatar, personality, and voice), your ideal customer profile, opener suggestions, identity capture, the live-demo hand-off, and display mode. Website Agent → Nudges manages saved nudges and suggested questions, page by page with search and filters: edit wording, remove a question, turn off a page, or, on its Settings tab, control whether a new conversation opens with a question about the current page. If the saved list changes while you edit, your unsaved work stays available until you choose to load the latest list. It also shows nudge engagement and Conversation outcomes, with conversation opens and, when Learn from conversations is enabled, useful conversations. See Website Agent Setup for the full walkthrough.

Recordings

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. Recordings carry your users' words and identity, so they require conversation access, which owners and admins have.

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.

People

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, the agents they used and last-seen date, and you can add, edit and delete records directly. Select a name to open that person beside the list, in a panel you can widen or open as a full page.

Changing a person's email or external ID here records that identity as provided by your team.

A person's page

A person's page shows what that visitor did, as plain counts taken from their records:

Sessions on record: how many of their sessions Floe holds, split by agent. A website conversation, a demo opened on its own, and an in-product session each count once; a website conversation that went on into a live demo is one session. The count in the People list is every agent session that began for them, so it can be higher.
Average session: the average length of those sessions, shown once at least one has a recorded length. It covers only those sessions and says how many that was.
Last seen and Agents used.
Latest lead score: the lead score and tier of their most recent scored conversation or demo. It appears once one has been scored.
Timeline: their conversations, demo sessions, in-product sessions and bookings, newest first; the newest five until you choose Show all. Each row opens the conversation, session or booking it describes.
What they did: the features their demos showed, what their website conversations were about, and the pages they viewed. A list only appears when something was recorded.
Details: the fields on their record, including anything your application sent with them. A field with no value is left out.
Notes from their conversations: short facts Floe noted from their earlier website conversations. These expire with your conversation retention.

Apart from the latest lead score, the figures are counts of the records Floe holds. Floe doesn't compute a health score or a ranking for a person. Retention removes a conversation's or session's content on your schedule, along with page views and notes; the session counts and the timeline rows stay until the person is deleted. The page says so when it shows only the most recent activity.

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 controls

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 Tailor the agent to what a visitor has read on or off. It is on by default: the Website Agent and the Demo Agent use the pages a visitor viewed to choose what to offer, and are instructed never to mention them. It is unavailable while visitor analytics is off.
Turn Website Agent transcript recording on or off. When it is off, visitors can still chat, but no transcript appears under Leads 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 Team

If you belong to more than one organization, switch between them from the top of the sidebar, just above the site switcher. Organization, at the bottom of the sidebar, opens your organization's pages:

General — your organization's name and description.
Team — everyone in the organization with their role, and the invitations you have sent. Invite people to the dashboard by email; invitees pick a password and land in your organization when they accept.
Connected apps — see below.
Usage — the credits your Demo and Website agents used, with the minutes and number of conversations behind them, by day (in UTC) and by site, for this month, last month or the last 90 days. A minute with the video avatar uses more credits than one without; the tab shows the rate.

Roles are Owner, Admin and Member. Owner and Admin can add sites, change sites and settings (including integrations), change what the agents know (add or remove sources, upload documents, delete content, run research, edit or hide what research found, and manage Reference Guides), invite, remove or re-role members, and read everything that carries a visitor's identity or words: Leads, People records, transcripts, session details, and the Insights records behind Asked a question, Shared email, and Took a demo. Members can view the counts that name no one (the Insights funnel, sources and pages, session statistics, and the credits on Usage), read a site's sources, content, product knowledge and Reference Guides, and browse non-sensitive site pages, but cannot add a site, see those records, change a site's configuration, or change what its agents know.

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.

Verifying your email

Sign up with your work email. A personal address, such as Gmail or Outlook, a disposable or placeholder address, or one Floe finds can't receive email can't create a Floe account. Someone you invite from Team joins with the address you invited.

Until your email address is verified, a banner at the top of every dashboard page asks you to verify it; you can keep working in the meantime. New accounts are emailed a verification link when they sign up. If you don't have one, or it has expired, use Send verification email in the banner (check your spam folder first). Open the link, then press Verify my email on the page it takes you to. Each link works once and expires after 24 hours; a new email replaces the previous link, and you can send one about once a minute.

People who join through a Team invitation don't need a separate verification email: accepting the invitation that was emailed to them confirms their address. Completing a password reset also confirms it.

Resetting your password signs you out of the dashboard on your other devices. A device that is already signed in can keep its current session for up to a day. A reset does not disconnect AI tools you connected to Floe; revoke those under Connected apps below.

Connected apps

Organization → 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:

Pick a site from the switcher at the top of the sidebar; it opens on the site's Home, with Leads under it
Pick an agent from the agent switcher below it; that agent's section lists its pages, starting with Setup
Site-wide sections such as Knowledge and People sit below the agent's section, the same whichever agent is picked
Click an item (such as a content source or conversation) to see its details

Most work happens inside a site. The sidebar stays visible so you can jump between sections without going back to a list.

Getting started

If you're new to the dashboard:

Start with the Quickstart to create your first site
Add content sources under Knowledge → Sources (see Ingestion)
Floe prepares the generated demo context
Launch your first demo session

FAQ

Can multiple team members use the dashboard? Yes. Invite them by email from Organization → Team. 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.

I didn't get the verification email. What do I do? See Verifying your email.

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? Demo Agent → Setup says Ready to share once at least one guide is live and its Product sign-in check passes. With Live product turned off in Demo Agent → Configure, it needs a product overview and a video or slide, of a kind you have turned on, to show instead. Guides start as drafts; ask us to make the ones you want offered live, or build your demo tour with your AI coding tool. Before any of that, a site needs at least one completed content source.