AgentForce Deployment Process Best Practices

Pre-Deployment Manual Steps

* Verify that the Target Org has valid licenses for Agentforce. If needed, you can match licenses to production.
* Verify that the Target org has Einstein enabled
* Setup → Einstein Setup
* Click the Turn on Einstein toggle, and make sure Einstein is On
* Verify that the Target Org has Bots enabled
* Setup → Einstein Bots
* Click the Einstein Bots toggle, and make sure Einstein Bots is On.
* Verify that the Target Org has Agents enabled
* Setup → Agents
* Click the Einstein Copilot for Salesforce toggle, and make sure it is set to On.
* Note: If you do not see the “Agents” option, refresh Setup. If you still don’t see the option or if you get any unexpected errors, check that you have the necessary Agentforce permission sets.
* Create a user and Profile in the Target Org that the Agent will run as
* Create a user with License ‘Einstein Agent’ and set the Profile to ‘Einstein Agent User’.
* Verify that the Target Org has Data Cloud enabled. This is not strictly necessary for Agents to run, but DataCloud is required for so many features that it is hard to imagine a scenario without it.
* Go to Data Cloud Setup.
* To enable Data Cloud, click Get Started.
* In your production org, select Data Cloud Setup.
* In the Quick Find box, enter Feature Manager, and then select Feature Manager.
* In the Data Cloud in the sandbox panel, click Enable.
* If the Target org is a sandbox, you must have Data Cloud in Sandboxes enabled in production.

Deployment Steps

• Make per-environment changes to your metadata.
• The Agent metadata specifies a running user. The value in this field will need to change to point to the correct running user in the Target Org. The field to change is <botUser>, which can be found in your Agent’s bot-meta.xml file.
• The agent created in a higher org will generate a new ID on creation. Therefore, Flows that reference the agent need to be updated as the deployed agent will not have any Inbound Omni Channel Flows assigned to it. In the “flows” metadata folder > XXX-flow-meta.xml, type fields. Look for the coPilotId value and update its ID.
• Retrieve and deploy the "genAiPlanner" object from the source organisation before deploying the bot object.
• Check the "v1.botVersion-meta.xml" file to identify the required "genAiPlanner" and ensure it is deployed first.
• Using the Salesforce CLI, deploy your metadata.

Post-Deployment Manual Steps

• Ensure that the agent is activated.
• Navigate to Embedded Service Deployments in setup and publish your ESA Web Deployment.
• Ensure all deployed flows have the correct version active.
• Add the deployed Permission sets from the Source org to the Agent user in the Target org (either manually or scripted).
• Update other permissions as needed.
• Common misses - give access to new Apex, Objects, Fields

Note: If there are any references, you must remove them pre-deployment and then manually add them again in the target org. This adds a pre- and post-deployment step. (EmbeddedServiceDeployments, Flows, Apex etc.)