Product Insights

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.

Insights

Open Site → Insights. The page reads top to bottom: the Funnel, then Where leads come from beside Pages that start conversations, then Leads, What people ask, and In demos. The 7-, 30-, or 90-day range at the top of the page applies to every section. Hover a funnel row or a column heading to see what it counts.

On a very busy site, a long range may be counted from the most recent activity only. A section says so when that happens, and a shorter range gives full counts.

Funnel

Six rows show how many distinct visitors reached Floe in the selected range, and how many went on to each outcome:

Each row shows its count, its share of Visitors as a bar and a percentage, and its change against the previous period.

Three things to know when reading it:

• Each row is counted on its own. A prospect who opens a demo link from an email lands in Took a demo without ever appearing in Opened the agent, so a row can be larger than the one above it. Each percentage is a share of Visitors, never of the row above.
• A visitor is counted once per row across the whole range, however many times they came back.
• Not measured is not zero. Shared email reads Not measured, with no bar, when Floe is not collecting it for your deployment; hover it for the reason. Booked a call stays at zero until provider booking verification is enabled and a provider is connected under Site → Integrations. A booking link alone keeps working but cannot produce evidence. See Integrations.

Change against the previous period

Each funnel row carries its change against the period of the same length immediately before it, and the top of the page names that period (vs previous 7 days). Insights opens on the last 7 days, so the change is week over week until you pick 30 or 90 days. The change is green when the count rose and red when it fell. Hover a change to see the earlier count it was compared with.

A change is only shown when there is an earlier count to compare with:

• A row that had none in the earlier period reads was 0, and a row that fell to none reads was followed by the earlier count, instead of a percentage.
• No change is shown when nothing was recorded in the earlier period, when the site is newer than that period, or when your retention settings no longer cover it.
• A row that reads Not measured has no change.

Where leads come from

One row per source, with the Visitors it sent, the Leads it produced, the leads who took a demo (Demos), and the leads who booked (Booked). A lead here is the same as on Leads: a visitor who booked, took a demo, shared an email or phone number, or asked about buying.

A source is the campaign a visitor arrived through (the utm_source and utm_campaign on the link they followed), otherwise the site that referred them, otherwise Direct. A demo started from a shared demo link is listed under that link, as Demo link and the link's name (or its campaign, or the day it was created, when it has no name). A link's row counts the demos started from it, so it can show more leads than visitors.

Each visitor is counted under one source for the whole range: the one their first visit in the range came from. A visitor who arrives from a campaign on Monday and from a search on Thursday is counted under the campaign, so the rows can be added up. The 20 sources with the most leads are listed.

Sources come from page views, so a visitor is not counted when visitor analytics collection is off or the visitor didn't consent. When some visitors or leads in the range have no source on record, the section says how many rather than counting them as Direct.

Pages that start conversations

One row per page, by path, with its Visits, the Chats that started on it, and how many of those conversations became Leads. A chat is a conversation in which the visitor wrote or spoke; opening the agent without saying anything is not one. Pages are ordered by conversations started, then by visits, and the top ten are listed. A visit ends after 30 minutes without a page view, so a visitor who returns later starts a new one; a page seen twice in one visit counts once.

Like sources, visits come from page views. A shared demo link opens on Floe's own page, not yours, so it is not listed; the page of a link you have since deleted can still appear. When some conversations in the range have no page on record, the section says how many.

Leads

Leads sums up the range and lists up to five visitors to call first: those who booked a meeting, then those who took a demo, shared an email or phone number, or asked about buying. Within each group the highest lead score comes first, then the newest; a score never moves a visitor into a stronger group. The line above the list counts each of those four across the whole range; when the list holds every lead of the range and each has a score, it counts Hot, Warm and Cold instead. It is the same evidence Leads uses.

A row shows the visitor's name and company with the strongest reason they are listed and, once the lead has been scored, its score. It never shows an address. A visitor with no name on record is described by what is known instead: their company, the demo link they came through, or the page they arrived on. Each row opens that visitor's conversation or demo, where their contact details are, and All leads opens the full list. The section requires conversation access; a Member sees a notice instead.

What people ask

The questions visitors asked the Demo Agent or the Website Agent most in the selected range, as the agent recorded them. Each shows how many conversations and demos asked it in that range. Identical questions are one row, and capitalisation, spacing, or a trailing question mark do not make two questions. The ten most asked are listed.

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.

To teach your agents the answer, select Add a fact on a question. It opens a new Reference Guide titled with the question; once you save it, both agents answer from it and the row reads Answered. If the same question is listed under Knowledge → Gaps, it is marked answered there too. Adding a fact needs an Owner or Admin, and the section requires conversation access.

Two things to know:

• The list is what the agent judged to be a question during the conversation, not a mechanical extraction of every sentence ending in a question mark.
• Answered means a fact you added covers the question. A question with no fact may still have been answered well by the agent in the conversation.

In demos

Two lists for the demos in the selected range, with up to ten entries each:

• Shown most: the features the Demo Agent showed, with how many demos showed each.
• Asked for, not shown: what prospects asked a demo to show that it did not, in their words, with how many demos asked. These also appear under Knowledge → Gaps, where you can add a fact to cover one.

The section requires conversation access.

Evidence behind a funnel row

Every funnel row opens the records behind it, over the same range it was counted in:

Owners and Admins hold both levels. A Member sees the funnel, Where leads come from, and Pages that start conversations, but gets a notice that conversation access is required in place of the three conversation-level lists and of Leads, What people ask, and In demos.

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 a demo shows the name, company and role they entered in the demo form.

Retention and the selectable range

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

Website Agent conversations

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, 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.

Session detail

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, 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 automatically

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, where the delivery log shows whether each one went through:

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 digest

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 dashboard shows the most recent week's digest, quiet weeks included; earlier weeks cannot be opened there. If you expected a digest and did not get one, check the dashboard's digest 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 retention

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.

What people ask and In demos are read from the sessions whose content Floe still holds, so an entry leaves them when retention removes that session's content or the person is deleted. Floe also keeps an all-time count of each question asked, as the question text and a number with nothing tying them to a person; that count is not deleted with an individual recording.

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.

FAQ

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. To see one visitor's sessions together, open their page from People. See Dashboard Overview. To filter by what a visitor did — booked, took a demo, shared an email, asked to buy — across both agents, use Leads.

Does Floe score my accounts? Floe scores leads, not accounts. After a conversation or a demo ends, a lead gets a lead score from 0 to 100 with a Hot, Warm or Cold tier, built from how well the visitor fits your ideal customer profile and from what they did. It shows on Leads, on the lead itself with the reasons behind it, on a person's page, in the AE, Slack and Teams recaps, and on the CRM lead card. The prospect's own recap never includes it. Floe does not compute account health scores or adoption percentages, and it does not alert you while a conversation is still under way. The score does not decide which visitors Leads calls worth a call: that is still whether they booked, took a demo, shared an email, or asked about buying.