Home / Docs / Reference Guides

Reference GuidesCopy link to this section

Reference Guides are short, site-authored notes for facts that may not appear in your public documentation: pricing, support channels, billing rules, commercial policies, availability, and similar product details.

A Ready Reference Guide becomes shared product knowledge for both the Demo Agent and Website Agent. It supplies facts for answers only. It does not create a demo walkthrough, tell an agent where to navigate, count as demo readiness, or appear in the Demo Agent's generated Guides list.

Create a guideCopy link to this section

Open Product Knowledge → Reference guides, then select Create reference guide. The action is available on every site to Owners and Admins.

Each guide has two fields:

  • Title — required, up to 120 characters.
  • Markdown content — required, up to 4,000 characters, in a plain Markdown editor.

Each site can hold up to 100 Reference Guides. If the editor reports that a guide is too long to index, shorten it.

Website Agent answers may share relevant guide content with public visitors. Do not put secrets, credentials, internal-only information, or customer-specific data in a Reference Guide. See Security & Privacy for the data-handling contract.

Ready, Indexing, and FailedCopy link to this section

  • Ready — the guide is indexed and both agents can use it.
  • Indexing… — a create or edit is being prepared. During an edit, agents keep using the previous Ready version until the replacement succeeds.
  • Failed — the create or edit did not go through and nothing changed. The editor keeps your draft so you can shorten it or try again.

A successful edit is available to the agents' next answer.

PermissionsCopy link to this section

Owners and Admins can create, view, edit, and delete Reference Guides. Members can view them but not change them.

How agents use guidesCopy link to this section

When a guide and crawled content disagree about a product fact such as pricing, support, limits, availability, or policy, the guide wins. A guide still has to be relevant to the question to be used; being operator-authored does not force an answer.

Keep one guide per topic and edit it in place.

Guide content is treated as facts, not instructions. Markdown in a guide cannot change how the agent behaves, create a call to action, or make it navigate. Reference Guide citations are named as a reference guide but are not linked to a source URL.

Edit or delete a guideCopy link to this section

Open a row to view it, or use its actions menu to edit or delete it. If another operator changed the guide since you loaded it, Floe preserves your draft and asks you to review the latest version instead of silently overwriting their change.

Deleting a guide removes it from both agents. Deletion is permanent, and research, ingestion, and guide regeneration never edit or remove Reference Guides.

When to use ingestion insteadCopy link to this section

Use Ingestion for source material that already lives in documentation, a help center, a changelog, or supported media. Use a Reference Guide for a small, authoritative gap you want to maintain directly in Floe. A Reference Guide is not a replacement for the screens, capabilities, and plans required to run a live demo.