---
schema_version: "1"
id: 35f2565b764947f0d3aa5475835e11ee1701354caedc30620fdf04fb5fc5883e
title: Define the Technical Requirements
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ai/264-0-0/agent_plan_requirements.md
canonical_url: https://help.salesforce.com/s/articleView?id=ai.agent_plan_requirements.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c3460a4a3b7a17ecc5ace112a44f19563440173b7cce92446862800c02050f97
description: "When planning an AI agent, gather technical requirements that will help you build the right solution. Key factors to explore include: data, channels, routing and escalation, and security controls."
products:
  - Agentforce
  - Cross Cloud
release: "264"
---
# Define the Technical Requirements

When planning an AI agent, gather technical requirements that will help you build the right solution. Key factors to explore include: data, channels, routing and escalation, and security controls.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions. <a href="https://help.salesforce.com/s/articleView?id=ai.agent_setup_explore_types.htm&amp;release=264.0.0&amp;type=5" title="Learn about agent types and default templates for specific clouds and common use cases.">Required add-on licenses vary by agent type.</a></td></tr></tbody></table>

## Data

Your organization needs to be data-ready to start an AI project, which means the data for the project is accurate, complete, available, accessible, and securely governed. When defining the data requirements for your Agentforce use case, be sure to assess the data quality, migrate and integrate data, establish data governance, and create a plan for data analytics. To learn more about data requirements, see [AI + Data: Project Planning](https://trailhead.salesforce.com/content/learn/modules/ai-data-project-planning).

## Channels

Consider the channels where the AI agent will operate. How will the agent engage with internal or external users? How will the agent be presented to users? See [Deploy Your Agent to Channels](https://help.salesforce.com/s/articleView?id=ai.agent_parent_deploy.htm&language=en_US) to learn more about the different options for deploying agents to channels, such as Slack, email, and messaging platforms.

## Routing and Escalation

AI agents sometimes need to escalate conversations to a live representative. Some reasons for escalating to a rep can include company policy, brand requirements, security measures, risk management, or regulatory compliance.

During the planning process, define all the ways in which human decision-making and oversight will occur during the course of the AI agent’s work. Clear guidelines about when and how reps should step in will make it easier for your organization to configure the right guardrails as you start prototyping your agent.

## Security Controls

When you start planning your AI agent, consider permissions and access for admins, employees, customers, and the AI agent itself.

- Admin Access: To create and manage AI agents in Salesforce, you need the Manage AI Agents user permission and the required permissions for your [agent type](https://help.salesforce.com/s/articleView?id=ai.agent_setup_explore_types.htm&language=en_US), or the Customize Application user permission.
- Employee Access: If your employees interact with the AI agent in Salesforce, the agent runs in the context of the currently logged-in Salesforce user. See [Trust and Agents](https://help.salesforce.com/s/articleView?id=ai.copilot_trust.htm&type=5&language=en_US).
- Customer Access: If your agent is deployed to external channels, such as your website, there are probably certain actions you don’t want an AI agent to perform on behalf of customers unless they’re verified. The way you design your authentication solution for Agentforce depends on the security and identification requirements for your particular use case. See [Maintain Trust with Agentforce Actions](https://help.salesforce.com/s/articleView?id=service.service_agentforce_trusted_private_actions.htm&type=5&language=en_US).
- Agent Access: Some AI agents, such as service agents, operate as an agent user, and the agent user has a dedicated user profile and role in Salesforce. The actions the AI agent can take depend on the permissions it’s assigned. See [Best Practices for Agent User Permissions](https://help.salesforce.com/s/articleView?id=ai.agent_user.htm&language=en_US) to find out how to control what data your AI agent can access.

#### See Also

- [_Trailhead_: Agentforce: Agent Planning](https://trailhead.salesforce.com/content/learn/modules/agentforce-agent-planning)