Docs

Use with agents

Enable knowledge notebooks on agents and test that answers come from the right source material.

After you create a notebook, enable it on the agent that should search it. Agents do not automatically use every notebook in the workspace.

Enable a notebook on an agent

  1. Open the agent

    Go to Agents, then open the agent.

  2. Open Configure

    Click Configure.

  3. Open Knowledge

    Select Knowledge on the configuration map.

  4. Find the notebook

    Use Search notebooks... if the list is long.

  5. Enable the notebook

    Turn on the notebook switch. The footer shows how many notebooks are enabled.

    Search notebooks, enable the right one, and check the enabled notebook count.

  6. Done

    Click Done.

If there are no notebooks, click Go to Knowledge and create one first.

Tell the agent when to use knowledge

Open Create and configure, then add instructions that explain when the notebook should be used.

Example:

text
Use the Support refund FAQ notebook for customer refund questions.
When you answer from the notebook, mention the policy section if it is available.
If the notebook does not cover the case, say that the policy does not answer it and ask a manager to review.

Instructions prevent two common problems:

ProblemHow instructions help
Agent ignores the notebookTell it which topics require notebook lookup
Agent overuses the notebookTell it when the notebook is relevant and when it is not

Test retrieval

Return to Build and try:

TestWhat good looks like
Direct questionThe agent answers from the notebook
Missing answerThe agent says the notebook does not cover it instead of inventing
Similar but unrelated questionThe agent does not force a bad match

If the agent misses obvious information:

  1. Confirm the notebook is enabled on the agent.
  2. Check that the document finished processing.
  3. Improve headings or split the document into clearer sections.
  4. Add more specific instructions.

Keep notebooks current

Review notebooks when policies or processes change. Old documents can make agents confidently wrong. If you replace a policy, remove or clearly archive the old version.

Related