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 Questions or Trends 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 visitor identities reached Floe during the selected 7-, 30-, or 90-day window? It then shows how many reached each later outcome:

The Shared email outcome and claim-backed conversation search require Floe to enable both staged email-claim capture and consumer access for your deployment. They are unavailable by default until that rollout is activated.

Unique visitors is the top-line reach number, not a page-view count. Within a window, the same visitor is counted once in each outcome shown. A visitor can appear in more than one outcome, including when they enter Floe directly through a demo rather than through the Website Agent. Each outcome requires its own activity: taking a demo does not imply that the visitor opened the Website Agent, asked a question, or shared an email first.

The headline numbers are deduplicated across the whole selected window. The small bars under each number show daily activity instead; a returning visitor can appear on several daily bars while still counting once in the headline.

Outcome rows are currently informational. Use Website Agent → Conversations to review available activity records. Records that contain visitor identity or transcript content require conversation access; aggregate Insights remain available to members without it.

The available window is limited by the shortest retention setting used by its outcome evidence: raw events or conversation content and shared-email claims. For example, a site keeping either source for 30 days cannot select a complete 90-day outcome window; the dashboard disables that window instead of presenting partial data as complete.

Website Agent conversationsCopy link to this section

Open Website Agent → Conversations to review available Website Agent activity. This is a broader conversation list, not a one-to-one list of the distinct visitors counted in an outcome. A row with a source-bound contact claim shows the shared address and its current claim status separately from visitor identity. Enter a complete email address to search these encrypted claims by exact match; partial email fragments do not search claim data. Search results and raw claim addresses require conversation access.

Search or filter the list, then open a row to see the stored transcript, source links, and agent actions when they exist.

After a conversation closes, its detail can also show the generated summary, topics, and outcome. Content that expires under the site's retention policy is clearly marked as removed.

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
• 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 CRM lead card can carry those fields plus qualification, intent, score/tier, source, and next-step context, but only a confirmed contact claim can authorize the CRM write.

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.

A connected CRM receives the source-aware lead card only after the exact email claim is confirmed. Claim capture/consumption and CRM connections are staged deployment capabilities rather than self-serve today; see Integrations.

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 has its own site-level retention window, and raw visitor events have a separate window. Source-bound shared-email claims from either agent use that site's conversation-retention window and are deleted in full when it expires. See Security & Privacy for the current 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 new message content is not retained and transcript-derived summaries cannot be generated. The Conversations page can still show an activity record without a transcript. The same Website Agent policy governs stored chat turns when a conversation hands off to a live demo; direct Demo Agent recordings use a separate deployment-level control. Talk to us if you need that control changed.

The Asked a question outcome can still count that an interaction happened while transcript recording is off; Floe does not retain the words the visitor typed or spoke for that outcome.

FAQCopy link to this section

Can I export this data? Not yet. Insights, session detail, and recordings are dashboard-only today. There is no export endpoint.

Do onboarding and support sessions appear in Insights? No. Onboarding sessions produce their own recordings and transcripts, which you can replay, but they do not contribute to the Questions or Trends views. Support sessions do too — unless the site connects live account data over MCP, in which case those sessions are deliberately never recorded, so nothing from them persists.

Can I filter sessions? There is a free-text search over the session list. There is no filtering by outcome, date range, or user.

Does Floe score my accounts? No. Floe does not compute account health scores, ICP fit, or adoption percentages, and it does not fire alerts when a prospect looks promising. What it gives you is the available record of what happened in each demo — the summary, questions, objections, and, when recording is enabled, the transcript.