Public documentation search

A grounded assistant for a public link — refuses anything not in the docs, so it cannot be talked into a claim.

Support · Someone asks · 4 steps · Reads your documents

AI Factory · Public documentation searchthe flow as it opens in the builder

QuestionQuestion

RetrieveRetrieve

AnswerAnswer

Answer shownAnswer shown

4 steps in the flowDrag the canvas, or any step, to move it around.

Why teams run it

A grounded assistant for a public link — refuses anything not in the docs, so it cannot be talked into a claim.

Retrieval respects each source’s own permissions, and the answer names the passage behind it.
Every run keeps its input, each step’s output, its time and model cost, and any decision.
In the builder, anything that would change a record or send a message is simulated; reads run for real.

What you supply: Public documentation as a knowledge source; A publication on the Deploy tab.

The same builder, tests and release review apply to a template as to anything built from scratch.

Open it as a working flow: Every step, source, branch and approval is already in place, and every one of them can be changed before it runs on your data.
Prove it before it ships: An evaluation set can gate the release, so a change that breaks an answer never reaches anyone. A question it cannot answer from the sources leaves the gate unproven, not passed.
Keep a person on the decisions: A run that needs a decision stops and says exactly what approving will do, and who it is waiting for.
Publish where people work: A form, an embedded widget, Microsoft Teams or a scheduled batch — with its own access and limits per deployment.

We open it in the builder, point it at a sample of your documents and systems, and run it with you.