> For the complete documentation index, see [llms.txt](https://docs.zaia.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zaia.app/quick-start/publish-your-docs.md).

# Key Concepts

Zaia Endless is built around a set of **core concepts**.\
Understanding these will help you design Agents more effectively and avoid unnecessary complexity.

***

### Agent

The central unit of Endless.\
Defined by **Role + Prompt + Settings**.

**Example:** “Assistant specialized in financial client data.”

**Best practice:** Start with the simplest configuration (Role + Prompt), then add Tools, Knowledge, or advanced capabilities only if needed.

***

### Role

A short sentence that summarizes what the Agent does.\
It helps position the Agent’s purpose.

**Example:** “Customer support agent for SaaS products.”

***

### Prompt

The main instruction set that defines how the Agent behaves.\
Supports up to **5000 characters**.

**Example:**\
“You are a sales assistant. Always ask the customer their name and product of interest. Be polite and concise.”

***

### Temperature

Controls the **creativity** of the Agent’s responses:

* `0%` → Fully methodical (ideal for factual Agents like finance or legal).
* `100%` → Highly creative (ideal for brainstorming or marketing).

***

### Effort

Defines how many **steps** the Agent can take to reach an answer.\
Range: **10–100**.

* **Low effort (10–20):** Simple tasks, FAQ-style Agents.
* **High effort (80–100):** Complex Agents orchestrating multiple Tools and Workflows.

***

### Planning

When enabled, the Agent creates a **plan** at the start of execution, considering available Tools and resources.

**Recommended for:**\
Agents operating in complex environments or executing multi-step logic.

***

### Reasoning

Controls the **depth of reasoning** applied by the Agent when generating responses.

Available modes:

* **Low:** Faster responses, suitable for simple conversations and FAQs.
* **Medium:** Balanced reasoning for most business use cases.
* **High:** Deeper analysis and structured thinking, ideal for complex decision-making or problem-solving.

> ⚠️ Higher reasoning levels may increase response time.

***

### Tools

Extensions that allow the Agent to go beyond the Prompt.\
Each Tool must be explicitly created and linked.

**Examples:**

* **Memory Tool** → Save variables like name, deadline, or budget.
* **Table Tools** → Insert, update, or search Table data.
* **Workflow Tool** → Execute a Workflow.
* **Ticket Tool** → Transfer the conversation to a CRM Team.
* **HTTP Tool** → Connect to external APIs.

**Best practice:** Only add Tools your Agent will actually use.

***

### Knowledge Base (KB)

A structured repository of documents, FAQs, or policies.\
Agents can search KBs using the **Knowledge Base Search Tool**.

***

### Tables

Native databases in Zaia Endless.\
Used to store and query structured data such as leads, CRM records, or inventory.

**Available operations via Tools:**

* Insert
* Update
* Search
* Semantic / similarity search

***

### Workflows

Sequences of steps that automate business logic.\
Workflows must be created first, then linked using a **Workflow Execution Tool**.

**Example:**\
“Check product availability → calculate delivery time → return result to the user.”

***

### MCP (Managed Connector Provider)

Native integrations with external applications.\
Require a **Connection** (OAuth or API Key) to activate.

**Examples:**

* Google Calendar → Create or list events
* Gmail → Fetch emails
* Supabase → Query external databases
* Notion / Airtable → Manage content

***

### Connection

Authentication that enables MCPs or Channels.\
Without a Connection, the Agent cannot access the external service.

***

### CRM Team

Groups of human operators that can receive conversations from Agents.\
Must be created before adding a **Ticket Tool**.

***

### Ticket Tool

The **only supported way** for Agents to transfer conversations to humans.\
Always linked to a CRM Team.

***

### Channels

Where the Agent interacts with users.

**Available options:**

* **Widget** (Web)
* **WhatsApp**
* **Instagram**
* **API**

**Best practice:**\
Test the Agent first using the internal chat (no channel required), then publish to external channels.

***

### Conditional Prompts (Advanced)

Conditional Prompts allow you to define **instructions that are executed only when specific conditions are met**.

They replace the previous concept of Tasks and enable more flexible, context-aware behavior.

**Examples:**

* If the user says *“finalize”* → Execute a closing prompt.
* If the user asks for a human → Trigger the Ticket Tool.
* If the conversation reaches a certain context → Change Agent behavior dynamically.

**Best practices:**

* Keep conditions specific and non-overlapping.
* Use Conditional Prompts for logic, not for core Agent identity.
* Avoid excessive chaining to maintain clarity and performance.