Agentforce : Service Agent Readiness & Setup Best Practices Guide

1. Before You Begin

Use this guide to confirm that your Salesforce org is correctly configured for Agentforce before creating or deploying a service agent. This guidance applies when validating setup readiness, permissions, data access, and environment consistency.

2. Required Platform Prerequisites

Before configuring the Agentforce Service Agent, confirm the following platform capabilities are available in your org:

• • Lightning Experience is enabled
  • Data Cloud is provisioned and accessible
  • Einstein Generative AI is enabled
  • Einstein Trust Layer is available
  • Agentforce is enabled in Setup

If any prerequisite is missing, Agentforce setup may partially succeed but fail at runtime.

3. Required Enablement Order

Follow this order to avoid setup failures:

• • Enable and verify Data Cloud
  • Enable Einstein Generative AI
  • Verify Einstein Trust Layer settings
  • Enable Agentforce

Note: Data Cloud and Einstein provisioning can take 15–60 minutes. Retrying setup too early may result in misleading errors.

4. Editions, Licensing, and Permissions Validation

This is one of the most common causes of Agentforce setup failures. Agentforce may appear enabled, but users are blocked due to missing permissions or licenses.

Required Salesforce Editions

Agentforce Service Agents are supported in:

• • Enterprise, Performance, Unlimited, and Developer Editions
  • Foundations or Agentforce 1 Editions

Some standard agent actions may require additional add-on licenses depending on the use case.

Required Permission Set Licenses

Ensure the following permission set licenses are assigned where applicable:

• • Agentforce Service Agent Builder
  • Agentforce Service Agent User
  • Data Cloud
  • Einstein Prompt Templates
  • Messaging for In-App and Web (if using Enhanced Chat)

Missing permission set licenses often result in missing UI options or silent failures.

Required Admin Permissions (Builder / Setup Users)

Admins configuring Agentforce must have:

• • Manage AI Agents
  • Manage Agentforce Service Agents
  • Customize Application
  • Manage Flows
  • View Setup and Configuration
  • Configure Messaging (if deploying to chat channels)

Best practice: Assign the Agentforce Service Agent Configuration permission set instead of granting permissions individually.

Agent User Permissions

Agentforce agents run as a dedicated Agent User, not as the logged-in admin or service rep.

By default, the Agent User has minimal access for security reasons. You must explicitly grant:

Permission Sets / Groups

• • Agentforce Service Agent Secure Base
  • Agentforce Service Agent User permission set group (includes Data Cloud User and Prompt Template User)

Object Access

• • Case: Read, Create (Edit/View All if updating cases)
  • Contact: Read (View All recommended)
  • Any custom objects referenced by flows, Apex, or prompts

Action Execution Permissions

• • Run Flows (for flow-based actions)
  • Execute Prompt Templates (for prompt-based actions)

If an agent action fails, always verify that the Agent User — not the admin — has access to the referenced objects and automation.

5. Agent User Readiness

Agentforce agents run as a dedicated agent user, not the logged-in admin.

Best practices:

• • Assign an appropriate role to the agent user
  • Grant object access required by agent actions
  • Validate permissions for flows, prompts, and data access

If the agent can’t access records, review the agent user — not the admin user.

6. Data & Knowledge Readiness

Agents rely on trusted, well-prepared data.

Before creating a Data Library:

• • Review content for clarity and structure
  • Avoid overly complex tables or poorly formatted PDFs
  • Ensure permissions allow the agent user to access the data
  • Verify the search index status it should be in Ready status.

Refer to Troubleshoot Agentforce Data Libraries for ingestion and visibility validation steps.

7. Common Readiness Issues