Answers from your content

Visitors get answers from two operator-owned places:

1. Published Agent Instructions — tone, boundaries, and what to do next.
2. Data Sources — pages and files you ingested and marked for Visitors.

A source or page set to Team only or Restricted is never used in a visitor answer, and it does not appear in the public llms.txt files for your site. See Data Sources to review or change that setting.

If a reply is thin or wrong, fix those two — publish clearer instructions, or ingest the missing page. Do not look for a platform “knowledge graph” setting.

When the project does not cover the question

The reply should acknowledge what was asked, share the closest detail that is in your Data Sources or in published Agent Instructions, and offer a next step you already configured, such as a form, booking, or call to action.

If the reply would otherwise show nothing, visitors see the fallback copy on Agent Instructions → Messages. You can change that copy. It should not supply a fact the project does not contain.

A saved Funnel still shows the sections you published. Those steps use that saved content.

Answers use this project’s Sources, published instructions, and saved sections. They do not use another project’s content, and they do not search the public web to fill a gap. That keeps answers closer to your material. It does not guarantee that every sentence stays inside it. A reply can still phrase a claim more strongly than your sources support. When that happens, ingest the missing page or publish a clearer boundary.

When a fact changes

Update the source that holds it: reload the website source, re-ingest that page, or replace the TXT or CSV file. See Data Sources. After that source is done, later answers can use the updated material. Publish Agent Instructions again when tone, boundaries, or the next step should change. A fact that already lives in Sources does not need a new instruction publish by itself. You remain responsible for keeping the source current.

What you do not configure

You do not tune how answers pick passages. Those are platform mechanics. Your job is accurate Sources and clear instructions.

Funnels and sections

A Funnel decides which content sections the live surface can show. In Agent Instructions, point the agent at a saved section with @page_section:<tag> or at a library shape with @ui-block:<id>. Type @ and pick the published object so the spelling matches. The UI blocks page lists each library item and its purpose. Visitors still hear product names you actually use — they should never see the raw tag.

© 2026 Cintesa. Guide text and screenshots are Cintesa product materials for personal and operator use. Do not scrape or republish them commercially without permission. Terms of Service · Privacy Policy.