Skip to main content

System Tools List

This article lists the system (built-in) tools available to every AI agent. Unlike custom tools, system tools don’t require you to add a specific tool group. To use a system tool, reference it by name in the available_tools section of your workflow configuration.

For custom tools and how to add them, see Custom Tools


Tool Summary

This table lists all available system tools provided by the platform.

Tool NamePurposeStatus
SendChatMessageSends a stylized message to the customerCore tool
FinishSessionEnds and closes the current sessionCore tool
SearchToolSemantic search across tools and knowledge base (VDB)System tool (routing)
ProvideOptionButtonsShows interactive option buttons to the customerSystem tool (UI)
SuggestChatMessageSuggests a message to the human operatorCopilot mode
TriggerKBSearchUnified search across all connected Knowledge SourcesKnowledge Source
ReportUnansweredQuestionLogs questions the agent failed to answer for the Q&A libraryKnowledge Source
SearchInKnowledgeBase(deprecated) Searches the vector-based Knowledge BaseRAG tool
NoKBAnswer(deprecated) Handles cases where no info is found in the KBRAG tool

Communication Tools

SendChatMessage

  • Purpose: Sends a stylized message to the customer in the agent's speech style and language.
  • Parameters:
    • stylized_message — a string with the message to display to the customer.
  • Note: This is the basic tool for any text communication. Used in almost every state where the AI agent responds with text.

SuggestChatMessage

  • Purpose: Generates a suggested response for a human operator instead of sending it directly to the customer.
  • Status: Copilot mode.
  • Usage: Used in "Copilot" workflows where the AI assists a human agent by drafting replies that the human can approve or edit.

Session & State Management

FinishSession

  • Purpose: Ends and closes the current customer session. Can be used as a logical conclusion or during escalation to a human agent.
  • Parameters:
    • last_message — final message shown to the customer before ending the session.
  • Note: Recommended for any scenario involving session closure (logical conclusion or escalation). It explicitly notifies the system that the conversation is over.

UI & Interaction Tools

ProvideOptionButtons

  • Purpose: Displays interactive response options as buttons to the customer.
  • How it works: Takes an observation — a list of options returned by other tools — and shows them to the customer
  • Example usage: When the agent needs the customer to select a specific category or confirm an action (Yes/No), this tool ensures structured input.

⚠️ Note: ProvideOptionButtons only renders UI options. State transitions and business logic are handled by the agent and workflow.

Tool & Skill Discovery

SearchTool

  • Purpose: Performs semantic search across available tools and the vector database (Knowledge Base).
  • Status: System tool (routing).
  • How it works: SearchTool acts as a router. Instead of hardcoding specific tools for every scenario, the agent uses this tool to "look up" the best action or information source based on the customer's intent.
  • Why it matters: Enables dynamic agent behavior and efficient tool selection in complex agents with many capabilities.

Knowledge Base Tools

TriggerKBSearch

  • Purpose: Performs a single, unified search across all connected Knowledge Sources (FAQs, websites, documents).
  • Usage notes:
    • This is the primary standard tool for all modern RAG (Retrieval-Augmented Generation) workflows.
    • Migration Note: It completely replaces the legacy tools: SingleSearchFAQ, SearchFAQ, SearchInKnowledgeBase, and ProfessionalAnswer. If you are migrating an agent, add TriggerKBSearch to your main agent state and delete old dedicated KB states along with their internal tools (such as FilterFAQ, AnswerFAQ, NoKBAnswer, etc.).
    • Note: The underlying system tools (SearchKnowledgeBase, SelectRelevantChunks, NoRelevantContext) are activated automatically in the background—you do not need to add them manually to your workflow configuration.

ReportUnansweredQuestion

  • Purpose: Logs on-topic questions from customers that the agent was unable to answer using the connected Knowledge Sources.
  • Usage notes:
    • Add this tool to your main agent state to track content gaps and continuously improve your bot.
    • When triggered, the missed question is automatically stored under the Unanswered tab in the Knowledge Sources > FAQ section of the platform dashboard.
    • Human administrators can review these questions and turn them into new approved Q&A pairs in one click.

NoKBAnswer (deprecated)

  • Purpose: Informs the flow that no relevant information was found in the Knowledge Base.
  • Usage notes:
    • Deprecated: This was an internal tool for legacy KB setups. If you are migrating to Knowledge Sources, this tool is no longer required and should be deleted along with your legacy KB states.

SearchInKnowledgeBase (deprecated)

  • Purpose: Searches the vector-based Knowledge Base for relevant information.
  • Usage notes:
    • Deprecated: Replace this tool with TriggerKBSearch in your active workflows.

Was this article helpful?