ruLog in to Senler

Agent Knowledge Base

In the side menu, open Agents, then select the required agent in the list. This opens the agent settings form.

  1. In the agent form, open the Tools tab.
  2. In the Knowledge Base block, select Configure.
  3. Select Add from knowledge base.
  4. Select a folder, file, or table.
  5. Select Done to return to the list of selected sources.
How to link sources. 3. Add from knowledge base
3 / 3
3. Add from knowledge base

If a folder is selected, the agent will see all current and future items within that folder.

Create and edit the materials themselves on the knowledge base page. In the agent form, select sources and configure read or edit access in Knowledge Base Permissions.

For a selected source, you can open its parent folder or remove it from the agent. Changes take effect after clicking Save.

Sources linked from the instructions

A material can be connected directly from the agent instructions. Select the @ button or type / or @, choose Knowledge base in the unified catalog, and then select the required resource. You can open folders and create a suitable text file from the same section.

The selected material appears in the instructions as a link and is automatically added to the sources. It is marked Used in the instruction in the source list. Removing that source opens a separate warning that its instruction link will be removed as well.

Clicking the link opens the material. Here you can check its content and the agent's permissions. If the resource was deleted, disabled, or is inaccessible, the link shows that state; select an available material or fix access before publishing.

See Knowledge base materials in instructions for the complete sequence.

Describe The Table Write Rule To The Agent

Table permissions do not determine whether the agent should keep one row per lead or append every request separately. This is a business rule and must be stated explicitly in the instructions.

If one current row is required, name the exact key, such as lead_id, and require the agent to update or create a record only by that key. The agent must not guess a physical row number or carry one over from another search result. If several rows match, it must stop without writing and report the duplicates.

If each request or event must be retained separately, explicitly allow a new row on every call. Test both scenarios with safe test data.

Diagnostics

If the agent does not use the knowledge base:

  1. Make sure that the file, folder or table is selected in the "Knowledge Base" block.
  2. Check that the resource is active.
  3. If you need a file inside a folder, make sure the correct folder or file is selected.
  4. If the source is selected but the agent cannot read or edit it, check Knowledge Base Permissions.