Research

Research is where Floe turns raw content and product context into structured product knowledge. After ingestion collects your documentation, research analyzes it so the AI agent can answer accurately, in your product's own terms, during demos, self-serve onboarding, and support conversations.

How research fits in

1. Create a site for your product
2. Ingest content from your docs, knowledge base, and videos
3. Research analyzes your content and product context
4. The AI agent draws on the resulting product knowledge

Research runs automatically after your first successful ingestion, and again on its own when a later run of your sources finds changes. You can also run it yourself: select Re-run research on Knowledge → What Floe learned. The tab shows whether the run is queued or running, which step it is on and how far along it is, and lets you cancel it; if a run fails, it shows why and offers Retry.

What you see in the dashboard

After research completes, Knowledge → What Floe learned shows what Floe found, with when research last ran and a count for each section:

• Summary: what your product is, who it is for, and its value proposition, with counts of what research found
• Features: the features identified in your content, with the use cases they support
• Workflows: step-by-step tasks a user can complete in your product
• FAQs: questions and answers drawn from your content

This is the place to check whether Floe has an accurate picture of your product before running demos. The Facts tab is separate: it holds the short facts your team writes directly as Reference Guides, and research never changes it. See Reference Guides.

Correcting what research found

When research got a feature, workflow, or FAQ wrong, an Owner or Admin can correct it on Knowledge → What Floe learned:

• Edit replaces the item's text with yours: a feature's name and description, a workflow's name, description, and goal, or an FAQ's question and answer. A workflow's steps can't be edited. Agents answer from your text in new conversations.
• Hide takes the item out of the product knowledge your agents are given. It stays in the list, marked Hidden from agents, and Unhide brings it back.

Re-running research keeps both: an edited item keeps your text, and a hidden item stays hidden. If a later run finds the same idea worded differently, it appears as a new item, which you can edit or hide in the same way. When research runs again because your content changed, a feature or FAQ it no longer finds in your content can leave the list, and your agents stop using it; an item you edited or hid always stays.

Edit and Hide change the item research generated, not everything built from the same content:

• The overview guide your Demo and Website agents start from is rewritten the next time research runs, unless you have edited that guide yourself. Select Re-run research after you hide or edit a feature.
• Feature guides, capabilities, and plans are separate and are not rewritten. Edit a guide yourself under Demo Agent → Guides, or ask us to refresh the rest.
• The page the item was drawn from stays in Library, and agents can still answer from it. Delete the page there if they should not.

Members can see which items are hidden or edited, but can't change them.

Reviewing and improving research output

Research quality mirrors the quality of your inputs. If you see gaps:

Missing features: You likely need more content. Add documentation or help articles that cover the missing area and re-run ingestion.

Vague descriptions: If a feature description is generic, edit it, or check whether the underlying documentation is specific enough. Detailed docs produce detailed research.

A fact your docs don't state: For something like pricing or a support policy that is absent from your sources, add a Reference Guide instead. A guide needs no ingestion or research run: once it shows Ready, both agents use it.

When you add or change source documents, run the source again: when the run finds changes, research re-runs on the updated content. See When research needs updated input.

When research needs updated input

Run your sources again, or let Automatic refresh do it, when:

• You've added or updated content via ingestion
• The agent is giving inaccurate or outdated answers during demos

Research re-runs on its own when a run finds changes. Select Re-run research to rebuild it without a content change.

The research layer is the bridge between your raw content and the agent's contextual help: it is what makes the agent sound like it knows your product rather than reading from a script.

FAQ

Is research the same as ingestion? No. Ingestion reads and indexes your raw content. Research analyzes that content and available product context to build structured product understanding. Ingestion is input; research is analysis.

Can I review what research extracted? Yes. Review the Summary, Features, Workflows, and FAQs sections of Knowledge → What Floe learned to check whether Floe's picture of your product is accurate. Owners and Admins can edit or hide a feature, workflow, or FAQ there.

Does re-running research undo my edits? No. An item you edited keeps your text, and an item you hid stays hidden. See Correcting what research found.

How long does research take? It depends on how much content the site has. What Floe learned shows progress while it runs.