Configuring a Zia Agent requires more than simply switching a feature on. Each agent needs to understand when to act, what context to consider, and how to map that information into the tools it uses. Getting this foundation right determines whether an agent performs reliably from day one or requires constant adjustment. This guide covers the three core concepts and the full activation process.

Three Foundational Concepts

Before activating any agent, it helps to understand the three building blocks that define how it operates:

1. Trigger

The trigger defines when the agent activates. It combines three elements: the module the agent monitors (Leads, Contacts, Deals, and so on), the conditions that must be met for the agent to fire (field values, record status, time-based criteria), and optionally a manual button that allows a CRM user to invoke the agent on demand on a specific record. The trigger is the agent’s entry point — if it is too broad, the agent will run constantly and consume excessive credits; too narrow, and it may rarely activate at all.

2. Context

Context is the information the agent receives about a record when it fires. This includes field values from the triggering record, related data from linked records (such as associated contacts, accounts, or activities), and communication signals — email history, call logs, and engagement patterns. The richer and more relevant the context, the more accurately the agent can respond. Providing too little context results in generic outputs; providing irrelevant data adds noise without value.

3. Parameter Mapping

Parameter mapping connects CRM field values to the inputs the agent’s tools expect. When a tool the agent uses requires a specific piece of information — an account name, a deal value, a contact’s email address — parameter mapping tells the agent which CRM field to draw that value from. Accurate mapping is critical: a misconfigured mapping means the agent passes the wrong data to its tools, producing incorrect or incomplete outputs.

Step 1: Configure the Agent Portal

Before any individual agents can be deployed, the Zia Agents portal must be connected to your CRM organisation. There are two routes to this setup:

• Via Marketplace: Navigate to Marketplace › Zoho › Zia Agents and click Setup now.
• Via Setup: Navigate to Setup › General › Agents and follow the portal connection process from there.

This step only needs to be completed once per CRM organisation. Once the portal is connected, all subsequent agent deployments are managed from within it.

Step 2: Choose a Deployment Mode

Each agent can be deployed in one of two modes:

• Connection: The agent operates through a standard integration connection. This is simpler to set up but provides less auditability for AI-driven actions.
• Digital Employee: The agent receives its own CRM identity — a named profile that owns the records and actions it creates. This mode is recommended for organisations where compliance, governance, or audit clarity matters, as it provides a clear separation between AI-driven and human-driven activity in the record history.

Step 3: Activate the Agent

Once the portal is configured and the deployment mode selected, activate the agent through the following process:

1. Navigate to Setup › General › Agents and click Setup Now for the relevant agent.
2. Select the module the agent will operate in — Leads, Contacts, Deals, or another supported module.
3. Define the trigger type — specify the conditions that must be satisfied and, if required, configure the manual trigger button.
4. Configure context data — select the fields, related record data, and communication signals the agent should receive when it fires.
5. Set up manual buttons if you want team members to be able to invoke the agent on a specific record from the record detail page.
6. Map parameters — connect CRM field values to the tool inputs the agent requires.
7. Click Activate to deploy the agent into your live CRM environment.

Post-Activation Monitoring

After an agent goes live, ongoing monitoring ensures it continues to perform as expected. Key areas to review regularly include:

• Version ID alignment — confirm the version running in CRM matches the latest published version in Zia Agents. A mismatch indicates an update is available.
• Trigger hit rate — review how frequently the agent is firing. Unexpectedly high rates may indicate over-broad trigger conditions; too few activations may indicate the trigger criteria are too restrictive.
• Output quality — periodically review the actions or records the agent has created or modified to ensure outputs match expectations and no errors are accumulating.
• Credit consumption — monitor how many credits the agent is using relative to the value it is generating, and adjust trigger conditions if consumption is disproportionate to the benefit.