Main concepts
At the heart of Syntphony CAI's intelligent solution are some fundamental concepts that revolutionize how AI Agents are built and deployed. Together, these elements create a flexible, powerful framework for developing adaptive solutions, acting as autonomous agents that can manage customer queries, solve common problems and guide users without human intervention. Let’s explore the elements that make up our solution..
A Project is the top-level container that defines and encapsulates a complete conversational AI solution. It establishes both the structural boundary of the system and the rules that govern how it operates.
Within a Project, all core components are configured and executed, including the Supervisor, specialized Agents, Workflows, Actions, Knowledge, and integration settings.
Each component has a clearly defined role:
The Supervisor orchestrates interactions by evaluating user input, applying governance rules, and determining how each request should be handled;
Agents execute specific tasks within a defined scope once selected;
Workflows, Actions, and Knowledge provide the operational capabilities required to fulfill requests, from structured processes to external integrations and information retrieval.
These components do not operate independently. The Project defines how they interact end-to-end: how requests are interpreted, how routing decisions are made, and how execution is delegated across the system.
As a result, the Project functions as both the structural boundary and the behavioral definition layer of the system.
This structure enables organizations to design conversational systems that are modular, governed, and scalable, supporting use cases ranging from customer support to complex operational workflows.
Within the Syntphony CAI ecosystem, the Supervisor is the orchestration and decision layer of a Project. It governs how every interaction is evaluated, classified, and routed according to a defined governance model.
Rather than relying on autonomous reasoning, the Supervisor operates as a deterministic decision engine. It evaluates each request against predefined eligibility criteria and applies a formal decision hierarchy to determine the correct handling path.
The Supervisor coordinates multiple Agents and Workflows through this centralized control layer. While Agents encapsulate domain-specific capabilities, the Supervisor is responsible for interpreting user input and activating the Specialist Agent that will resolve the request.
Coordination across multiple Agents
In complex scenarios, such as technical support, multiple Agents may be available (e.g., diagnostics, troubleshooting, billing).
The Supervisor coordinates these components by routing each request to the appropriate Agent or Workflow based on governance rules and eligibility criteria. It ensures that the right capability is activated at the right time, without ambiguity or overlap.
Structured orchestration
The Supervisor operates through a governed and deterministic process. For every interaction, it:
Verifies eligibility across available Agents or Workflows based on the selected governance model;
Classifies the request as conversational (chit-chat) or task-oriented;
Selects the appropriate handling path based on predefined decision logic;
Applies a controlled fallback when no valid path exists.
This ensures that decisions are not inferred or improvised, but consistently enforced according to the Project’s defined rules and capabilities.
Rules and Guardrails
They define the boundaries of system behavior and ensure that all interactions remain aligned with governance policies and domain constraints.
Rules define what the system is allowed or not allowed to do;
Guardrails enforce those boundaries at runtime, ensuring that decisions and outputs remain compliant.
Together, they establish a controlled environment where behavior is explicitly defined rather than implicitly learned.
Personas define how Agents communicate, transforming them from generic interfaces into structured communication partners aligned with specific contexts and expectations.
They provide a configurable communication layer that determines how responses are expressed, including tone, style, and contextual framing.
By defining personality traits, communication styles, and domain-specific context, Personas allow Agents to adapt their approach to different user profiles, industries, or interaction scenarios. This behavior is explicitly configured as part of the system design, ensuring consistency and control.
As a result, interactions remain clear, relevant, and aligned with business expectations, while enabling more natural and context-appropriate communication.
In Syntphony CAI, Agents are specialized execution units responsible for handling requests within a defined domain.
Each Agent operates through a structured set of skills that define how it retrieves information, performs tasks, and interacts with external systems. Agents do not make decisions or control routing. They are invoked by the Supervisor once a valid handling path is determined.
As part of the execution layer, an Agent’s role is to perform tasks within its scope—not to orchestrate or classify interactions. This separation ensures that execution remains modular, predictable, and fully aligned with the system’s governance model.
Agent skills
Agents rely on a set of skills that enable them to process inputs, generate responses, and perform operations.
In the platform, Skills are composed by:
Actions and Tools;
KAI Collections (Knowledge)
Together, they define the Agent’s operational and reasoning capabilities.
Actions
Actions are structured execution units within Agent Skills.
They define what the Agent must accomplish as part of a goal-driven workflow and how the required information is collected to achieve that goal.
Tools
Tools are integrations that allow Agents to interact with external systems and services.
They enable real-world operations such as retrieving data, updating records, triggering processes, and executing workflows—extending Agent skills beyond response generation.
KAI Collection (Knowledge)
Knowledge enables Agents to retrieve and use information from structured content sources.
Through Retrieval-Augmented Generation (RAG), Agents access relevant data at runtime and ground their responses in external knowledge, improving accuracy, consistency, and contextual relevance.
Rules and Guardrails
Within Agents, Rules and Guardrails define how tasks are executed and ensure that execution remains safe and controlled.
Rules specify how the Agent performs its Actions, including execution steps, constraints, and operational protocols;
Guardrails enforce safety, policy, and domain boundaries during execution, preventing unsafe or non-compliant outputs.
Actions define the specific tasks an Agent performs to fulfill a request. They represent the core unit of execution within an Agent.
An Action is a structured execution contract that defines:
Which task should be performed;
What data is required;
How the task should be executed.
Each Action is configured through a set of components:
Name: identifies the purpose of the Action. For instance: ticket resolution, appointment scheduling;
Instructions: define when the Action should be executed and how it should handle its inputs and behavior;
Properties: specify the required data for execution, including what information must be collected and which inputs are mandatory. Each property represents a structured input used during task execution.
Once all required properties are provided, the Action is executed to perform a defined operation, such as generating content, processing information, or triggering workflows.
By structuring both inputs and execution logic, Actions enable Agents to translate conversational input into controlled, task-oriented outcomes.
Last updated
Was this helpful?