What is an Agent?
In Zaia Endless, an Agent is more than a chatbot. It is a configurable AI entity capable of reasoning, using tools, interacting with data, and collaborating with humans — all inside a single platform.
Agents are designed to start simple (just a Role and a Prompt) and evolve progressively with Memory, Knowledge, Tools, Workflows, and external integrations.
Core Identity
Every Agent starts with two essential elements:
Role
A short description that defines the Agent’s purpose.
Example: “Assistant specialized in customer onboarding.”
Prompt
A detailed instruction set (up to 5000 characters) that defines:
Behavior and tone
Objectives and boundaries
How the Agent should respond in different situations
💡 Tip: Whenever possible, keep essential knowledge directly in the Prompt to avoid unnecessary complexity.
Settings That Shape Behavior
Agents are dynamic and configurable. These settings define how an Agent thinks and responds:
Temperature
Controls creativity:
0%→ Fully methodical (finance, legal, compliance).100%→ Highly creative (brainstorming, marketing).
Effort
Defines how many reasoning steps the Agent can take. Range: 10–100.
Low (10–20): FAQs and simple flows
High (80–100): Complex logic, tool orchestration, workflows
Planning
When enabled, the Agent creates a structured execution plan before acting, considering available Tools and resources.
Recommended for Agents that operate in multi-step or decision-heavy environments.
Reasoning
Controls the depth of reasoning applied when generating responses.
Available modes:
Low — Faster responses for simple interactions
Medium — Balanced reasoning for most business use cases
High — Deeper analysis and structured thinking for complex problems
⚠️ Higher reasoning levels may increase response time and credit usage.
Extending Agent Capabilities
Agents can be extended using native Endless resources:
Memory
Works like persistent variables. You decide what information should be stored and reused later.
Examples: name, email, budget, deadline.
Knowledge Bases
Structured repositories for large or frequently updated content such as:
FAQs
Product manuals
Internal policies
Agents access them via Knowledge Search Tools.
Tables
Native Endless databases used for structured data like:
Leads
Customers
Orders
Tickets
Tables can be queried and modified through dedicated Tools.
Workflows
Predefined multi-step processes that automate business logic.
Example: “Validate input → call external API → update table → respond to user.”
MCPs (Managed Connector Providers)
Native integrations with external platforms. Once connected, MCPs unlock new Tools for the Agent.
Examples: Google Calendar, Notion, Airtable, Supabase.
Acting Through Tools
Agents are passive by design — they only act when triggered by user interaction or internal logic.
Tools allow Agents to perform actions such as:
Execute code (Code Execution)
Store and retrieve memory (Contextual Memory)
Send follow-up messages after inactivity (Follow Up)
Search Knowledge Bases (Knowledge Search)
Read and extract data from PDFs (PDF Reader)
Insert, update, or search table rows (Table Row Insertion / Update / Search)
Perform semantic or similarity searches on tables
Execute workflows (Workflow Executor)
Send messages programmatically (Message Sending)
Create tickets for human assistance (Ticket Creation)
Make external API calls (HTTP Request)
Perform web searches (Web Search)
💡 Best practice: Only enable Tools your Agent is expected to use. Fewer tools lead to more predictable behavior.
Conditional Prompts (Advanced)
Conditional Prompts replace the previous concept of Tasks.
They allow you to define instructions that execute only when specific conditions are met, enabling dynamic and context-aware behavior.
Examples:
If the user asks for a human → trigger Ticket Creation
If the conversation reaches a certain context → adjust tone or flow
If the user confirms an action → execute a Workflow
Best practices:
Keep conditions explicit and non-overlapping
Use Conditional Prompts for logic, not for core identity
Avoid excessive chaining to preserve clarity and performance
Where Agents Operate
After testing internally, Agents can be deployed to Channels:
Website Widget
WhatsApp
Instagram
API
The API channel allows Agents to be consumed programmatically by external systems, applications, or custom frontends.
Each channel requires a valid Connection when applicable.
Why Endless Agents Are Different
Simplicity first — Launch with just a Role and Prompt
Native data handling — Knowledge Bases and Tables live inside Endless
Structured orchestration — Tools and Workflows enable complex automation
Seamless human handoff — Built-in CRM with Tickets and Teams
Multi-LLM flexibility — Optimize cost, speed, and accuracy
👉 In Zaia Endless, an Agent is not just answering questions — it’s a scalable digital teammate that evolves with your business.
Last updated