Product InsightsCopy link to this section

Every demo the agent runs is summarized, and — when demo recording is enabled for your deployment — recorded and transcribed too. This page covers what Floe captures, where to find it, and what reaches your team automatically.

Insights combine activity from the demo agent and website agent. Onboarding and support sessions have their own recordings and do not feed the views described below.

InsightsCopy link to this section

Open Site → Insights. The outcome overview appears above the Questions and Trends tabs.

Unique visitor outcomesCopy link to this section

The overview answers the top-line question first: how many distinct visitors reached Floe during the selected 7-, 30-, or 90-day window? It then shows how many reached each later outcome:

Three things to know when reading the card:

• Each outcome is counted on its own, so the six numbers are not a funnel. A prospect who opens a demo link from an email lands in Took demo without ever appearing in Opened agent. Every percentage on the card is a share of Unique visitors, never of the previous row. The ordered view is below.
• A visitor is counted once per outcome across the whole window. The small daily bars under each number show activity per day, so a returning visitor can appear on several bars while counting once in the headline. A dashed bar is today, still counting.
• Not measured is not zero. An outcome Floe is not collecting for your deployment reads Not measured, with a grey placeholder instead of a sparkline. Shared email needs contact capture enabled; Booked call needs provider booking verification enabled and a provider connected under Site → Integrations. A booking link alone keeps working but cannot produce evidence. See Integrations.

Evidence behind an outcomeCopy link to this section

Every outcome number opens the records behind it, over the same window it was counted in:

Owners and Admins hold both levels. A Member sees every count but gets a "requires conversation access" panel in place of the three conversation-level lists.

No row carries an email address or a browser identifier, and the Shared email list never shows the address — open the linked conversation or demo session, or use Website Agent → Conversations, to reach it. Two lists show what the visitor typed: Asked a question shows a short preview of their own words, and Took demo shows the name, company and role they entered in the demo form.

Ordered journeyCopy link to this section

Below the outcomes, Ordered journey counts only visitors whose stages happened in order within the window. Someone who walked straight into a demo appears in the Took demo total above but drops out of this cohort at their first missing step. This is the only place a % of previous is shown, because it is the only place the stages are ordered. Do not add these counts to the outcome totals.

Shared email — claim statusCopy link to this section

This card breaks Shared email down by the status of each shared address. It counts addresses rather than people, so it can total more than the Shared email tile when a visitor corrected their address.

Retention and the selectable windowCopy link to this section

Insights can only show a window your retention settings cover. A site that keeps events or conversation content for 30 days cannot select a complete 90-day window; the dashboard disables it rather than presenting partial data as complete.

Website Agent conversationsCopy link to this section

Open Website Agent → Conversations to review Website Agent activity. Search or filter the list, then open a row to see the stored transcript, source links, agent actions, and — after the conversation closes — its summary, topics, and outcome. Content that has expired under the site's retention policy is marked as removed.

Enter a complete email address to find the conversations where it was shared; partial addresses do not match. Addresses and search results require conversation access.

QuestionsCopy link to this section

Every question a prospect asked during a demo, as the agent recorded it. Identical questions are grouped into a single row with a count and the date it was last asked, so the list surfaces what comes up repeatedly rather than what came up once.

This is the fastest read on where your positioning has a hole. If eleven prospects asked whether you support SSO, that belongs on your pricing page, not in a demo.

Two things to know:

• Grouping is an exact text match. "Do you support SSO?" and "do you support sso" are counted as two separate questions.
• The list is what the agent judged to be a question during the call, not a mechanical extraction of every sentence ending in a question mark.

TrendsCopy link to this section

Two charts over the last 30 days:

• Session volume — demos started per day
• Completion rate — the share of that day's sessions that reached the end. Sessions that were opened but never joined count against it.

Every day in the window gets a bar, including days with no sessions.

Session detailCopy link to this section

Open any session from Demo Sessions to see:

• Summary — a written recap of the conversation, generated after the call
• Buying signals — moments the agent judged to be significant, as a list of written observations
• Prospect profile — what the agent learned: pain points, what they said they were interested in, engagement signals, and objections
• Contact details — the email and, when available, the phone number the prospect shared. A phone is labelled Prospect-confirmed when the prospect checked the transcription during the call, or Stated when it came from a form or demo link. Neither label verifies ownership. Requires conversation access.
• Features shown — the parts of your product the agent actually demonstrated
• Conversation — the transcript with elapsed timestamps, when recording is available
• Pages — the URLs the agent visited during the demo

AE, Slack, and Teams recaps carry two extra lists the dashboard does not show: the prospect's tech stack and any capability gaps they mentioned. A connected CRM receives a lead card with those fields plus qualification, intent, score, and next-step context — see Integrations for when a contact is written.

The prospect profile is the part your AEs will use. It is what the prospect said, captured as they said it, so a follow-up call can pick up where the demo left off instead of re-running discovery.

What reaches your team automaticallyCopy link to this section

After a demo completes — or an eligible Website Agent conversation ends — Floe can send the recap to four places. Each is a separate switch under Site → Integrations:

The prospect gets a deliberately different recap from the one your team gets — theirs is a summary of what they saw, with none of the qualification language.

Weekly digestCopy link to this section

Every Monday, Floe emails a digest of the previous week to the owners of your organization: session counts, average duration, the top questions, and how many sessions were abandoned. It links to a fuller version in the dashboard, which additionally names the abandoned sessions.

A quiet week sends no email. If nobody ran a demo, there is nothing to report, so we skip the send rather than mail you a page of zeros. The week is still recorded either way, so you can always open that week in the dashboard. If you expected a digest and did not get one, check the dashboard for that week first — and talk to us if the sessions are there but the email never arrived.

The digest is sent automatically once your site is live. There is currently no setting to change its recipients, its schedule, or to turn it off — if you need that, talk to us.

Recordings and retentionCopy link to this section

Demo recordings and transcripts are kept for 90 days by default, then deleted along with the prospect details attached to that session. Website Agent conversation content, contact details, and raw visitor events each have their own site-level retention window. See Security & Privacy for the controls and allowed ranges.

The aggregated question list under Insights is not deleted with an individual recording — it holds the question text without tying it to a person.

Website Agent transcript recording is controlled per site under Site → Settings → General → Visitor data collection. Turning it off keeps live chat available, but message content is not retained and no summary can be generated; the Conversations page still shows that a conversation happened, and Asked a question still counts it. Direct Demo Agent recordings use a separate deployment-level control; talk to us if you need it changed.

FAQCopy link to this section

Can I export this data? Bulk export is dashboard-only today — there is no export endpoint, and no CSV or scheduled delivery. For programmatic access, connect your own AI tool over Floe's MCP server: a read-only connection reaches demo sessions, prospect questions and funnel metrics with your own permissions. Recordings are not reachable that way.

Do onboarding and support sessions appear in Insights? No. Onboarding and support sessions produce their own recordings and transcripts under Onboarding Agent → Recordings, but they do not contribute to Insights. Support sessions that use live account data over MCP are never recorded at all.

Can I filter sessions? Yes. Demo Sessions has a free-text search over prospect name, company, role and summary, plus filters for status, a last 7 / 30 / 90 day window, and Recorded for sessions that still have a playable recording. They search every session on the site, not just the page you have loaded. There is no filter by funnel outcome or by person, and search does not match email addresses. See Dashboard Overview.

Does Floe score my accounts? No. Floe does not compute account health scores or adoption percentages, and it does not fire alerts when a prospect looks promising. A session's recap can carry a lead score or tier, but that is a read of one conversation, not an account score. What Floe gives you is the record of what happened in each demo — the summary, questions, objections, and, when recording is enabled, the transcript.