Before jumping into the setup steps, it helps to understand the three key decisions that shape how an agent operates inside CRM. Every agent configuration comes down to these three things.
Choosing the activation condition decides the entry point for your agent's actions.
You start by selecting the module where the agent should be activated. For example, if the agent should assist with sales deals, you pick the Deals module. This determines the data scope the agent can access during execution.
Then you select the event trigger—the starting point for the agent. The agent can be triggered for all records in the module, or only for specific records that meet certain conditions.
You can also choose to trigger the agent manually through a custom button, giving users the option to invoke it on demand from within a record.
Once the activation conditions are set, you select what additional information gets passed to the agent at the time of execution. This is what gives the agent enough context to act meaningfully.
You can send fields from the current record, related module information, signals from various sources (like email sentiment, missed calls, or unopened messages), and user or system metadata. Without this context, the agent won't know what to do, or might act with incomplete or irrelevant data.
For example, if you want an agent to suggest the next best action for a deal, you need to give it access to existing calls, meetings, and tasks, as well as when notes are created or edited in the record. These details are passed as signals.
If your agent uses tools that expect certain inputs—such as record IDs, email addresses, module names, or dates—you need to tell the system where those values should come from. This mapping connects the agent's tools to the right CRM data.
This step is essential when the agent works in on-trigger mode. The agent waits for a specific event in CRM, pulls the latest data from that record, and passes it to the tools it's connected to. Mapping ensures the right values reach the right parameters.
If your agent operates based on model selection or constant (for example, an agent that answers general questions about Zoho CRM concepts), this mapping step isn't required since it doesn't need dynamic inputs from CRM.
Before you activate an agent, the first step is to configure the agent portal for your CRM org.
Once configured, you can access the portal details in this section. Click on Configure Agents to head to the Agents tab in CRM.
You can also configure the portal directly from the all-new Agents tab under the General setup category.
Once your agent is created (or hired from the Store) and tested, you deploy it into Zoho CRM from the Zia Agents platform. The deployment method you choose determines how the agent is identified in CRM and how its actions are tracked.
With this method, the agent is connected to CRM through a standard integration. Actions performed by the agent are logged under the identity of the user who deployed it. The agent does not have a separate identity in CRM.
To deploy:
You will be redirected to the CRM page, where you can proceed with setting up the agent's activation conditions.
When you deploy an agent as a Digital Employee, it gets its own identity in your CRM. The agent is registered in Zoho Directory with a unique @ziaagent.ai email address and is assigned its own role and profile just like a regular CRM user. Every action the Digital Employee takes is logged under this identity, not under the deploying admin's name.
This gives you two things. First, clear audit visibility—you can tell exactly which actions in the CRM were performed by the agent versus by human users. Second, permission control—since the Digital Employee has its own role and profile, its access to modules, fields, and data follows the same permission model as your CRM users.
To deploy:
This opens the Deploy Agent pop-up with four steps:
a. Applications Link the required portals from your Zoho Directory account. Select the service (for example, Zoho CRM) and choose the org/portal you want to deploy the agent into. Click Continue.
b. Permissions Choose a role and a profile for the Digital Employee. The available roles and profiles are fetched from the portal you selected in the previous step. Click Save, then Continue.
c. Identity Set a first name, last name, and email address for the Digital Employee. This is the identity that will appear in CRM audit logs and activity trails for every action the agent performs.
d. Summary Review the configuration and click Deploy.
Once deployed through either method, the agent appears under the Draft column in the Agents tab (Setup > General > Agents) in CRM. From here, you set up and activate the agent.
To activate an agent, first you need to add it to your CRM org.
On Zia Agents, follow the steps for creating an agent:
Once the agent is tested, you can choose to deploy it, and once the agent is deployed, it will be available under the Draft column.
Setting up an agent
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
All-in-one knowledge management and training platform for your employees and customers.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.