--- schema_version: "1" id: 5801eaad0fa8c34c1c81227425c06d648612e867372275b5a5f0f063864ebb44 title: Considerations for Using Agentforce Prospecting collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/sales_agent_prospecting_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.sales_agent_prospecting_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 9e1e79740db54c2cde367488478ca6da6d80479ef369f096a1fb135b468a6378 description: Review these considerations about Agentforce Prospecting. products: - Sales Cloud - Agentforce release: "264" --- # Considerations for Using Agentforce Prospecting Review these considerations about Agentforce Prospecting. ### Required Editions
Available in: Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions with the Agentforce for Sales or Agentforce for an Industry add-on, or in Agentforce 1 Sales and Industry Editions where included. Requires each user to have the Agentforce for Sales or Agentforce for an Industry add-on to access actions.
## Agent Versioning Admins can create, manage, and iterate on new versions of their agents before or after activation. To create a new version of an existing agent, go to the agent and click **New version**. ## Agent Customization Begin customizing your agent in the guided configuration from Agentforce for Sales. To customize the agent further, open it in Agentforce Studio. The prospecting template in Agentforce Studio includes the agent's subagents, which you can adjust to research accounts the way your top sellers do. After you customize an agent in Agentforce Studio, the guided configuration locks for that version. To return to editing in guided configuration, create a new version. Creating a new version resets the prospecting agent’s script and discards custom actions and instructions added in Agentforce Studio. ## Deploying Multiple Agents You can deploy up to 10 prospecting agents per org. Create a separate agent for each business segment, and align your agents with your company’s go-to-market structure. For example, create distinct agents for different: - Company sizes: Create separate agents to handle the unique qualification rules, account research steps, and complexity variations inherent to small businesses versus enterprise corporations. - Geographic regions: Create separate regional agents for region-specific qualification criteria, schedules, and market needs. - Vertical markets: Create separate agents when the core business value proposition changes drastically between industries, requiring entirely distinct account research criteria. ## Deploying from Sandbox to Production You can build and test an agent in a sandbox, but deploying it with change sets or metadata isn’t supported. Metadata deployment across environments can stop the agent from working correctly. Instead, configure the agent in production to mirror your sandbox settings. Before you turn on your agent in production: - Re-establish and authenticate connections to external data vendors, such as ZoomInfo, in production. - Assign the agent and users the required permissions in production. - Test the agent's behavior with a small, specific set of target accounts before enabling the agent broadly in production. ## Data Retention The agent includes these research entities, which store the history of each person and account the agent researches and its rationale for generating or not generating a prospect. - [Account Prospecting Agent Research](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_accountprspagntrsrch.htm) - [Contact Prospecting Agent Research](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contactprspagntrsrch.htm) - [Lead Prospecting Agent Research](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_leadprspagntrsrch.htm) - [Prospecting Agent External Company Research](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_prspagntextlcorsrch.htm) - [Prospecting Agent External Person Research](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_prspagntextlpersrsrch.htm) Salesforce doesn't guarantee retention of this data for more than two years. ## Prospect Ownership The agent assigns prospects only to users who have prospecting agent permissions. How and to whom prospects are assigned is based on how the agent is configured. Assign all prospects to a single user, or distribute them evenly among a group of sales reps. ## Past Engagement Data in Prospect Summaries Prospecting agent can reference available past-engagement data, including call transcripts, calendar events, and emails, when it writes prospect summaries. For each account report source, select whether to prioritize contacts with past engagements and select the minimum engagement level to consider. This prioritization setting applies to scheduled and manual report runs. Manual account runs don’t apply the configured boost, but it can use existing past-engagement insights when evaluating Salesforce contacts. ## Prospecting Limits The open prospects per sales rep that you specify during agent configuration determines how many prospects appear for each user on the Approval Required tab of the Prospecting page. This limit applies to scheduled and manual report runs and doesn’t reset each week. When a sales rep reaches the limit, report runs stop generating prospects for that rep until the outstanding count falls under the limit. Manual account runs skip this limit check when the action starts. Prospects created by the action that are awaiting approval still count toward that rep’s outstanding total for the same agent and can reduce capacity for later report runs. ## Account Research - Report runs research only the accounts in the report that you gave the agent. To research an account that isn't in the report, add it to the report or click Generate Prospects from Account on the account record. - After an account is successfully processed in a report run, the agent skips the account for one calendar month. This applies even if the account doesn’t qualify or no prospects are found. To research the account sooner, click Generate Prospects from Account on the account record. - If no eligible sales rep has room for new prospects, the report run can finish without processing the account. The account doesn’t start a cooldown, so a later report run can research it. - If the agent sets the existing account owner as the prospect owner, the owner must be an eligible prospecting user. If Route Prospects from Additional Account Owners is enabled, accounts owned by non-prospecting users can be routed to the selected sales reps for unassigned prospects in agent configuration. Accounts without an eligible owner or configured recipient are skipped. - If researching an account reaches the 10-minute limit, the agent stops processing that account and keeps any prospects already created. ## Starting and Scheduling Your Agent to Run - Activate the agent before starting a run. - Each agent can have only one report run queued or in progress at a time. - When promoting queued report runs, the scheduler prioritizes manual runs over scheduled runs. It can stop an unfinished scheduled run from an earlier scheduling cycle. This cleanup doesn’t stop manual report runs, but a manual run can still fail or be stopped explicitly. - If your org has reached its concurrent report-run limit, a new report run waits in the queue until a slot opens. ## Data Vendors Connection to external data vendors such as ZoomInfo is optional. ZoomInfo is the default data vendor for Agentforce prospecting. To use another data vendor, create compatible replacement actions by using Apex or an autolaunched flow, and replace the corresponding actions in Agentforce Studio. If a vendor connection is unavailable, the agent can continue with Salesforce CRM contacts when the failure supports fallback. Other vendor errors can cause account processing or the run to fail.