On this page
- What does Salesforce require before you turn on Agentforce?
- How do you set up the agent user safely?
- Is your data ready for an agent?
- Will your automation fight the agent?
- How do you test the agent before launch?
- Which checks should you fix first?
- What does readiness cost compared with a launch?
- How do you run this checklist with Clientell AI?
- Sources
- Common questions about the Agentforce readiness checklist
An Agentforce readiness checklist is a list of org checks you run before an AI agent goes live. It covers five areas: platform setup, the agent user, data, automation and testing. Salesforce's own Service Agent readiness guide says most setup failures come from missing prerequisites and permission gaps.
Clientell AI, the AI Salesforce admin, runs these checks for you. The free Agentforce readiness audit is read-only and lists every gap with a drafted fix.
What does Salesforce require before you turn on Agentforce?
Agentforce runs in Enterprise, Performance, Unlimited and Developer Editions (Set Up Your Agent). Check yours in Setup > Company Information.
Salesforce's Service Agent readiness guide gives an order. Follow it, or setup can half work and then fail at run time.
- Turn on Data Cloud and confirm it is provisioned.
- Turn on Einstein generative AI in Setup > Einstein Setup.
- Check the Einstein Trust Layer settings, such as data masking for personal fields.
- Check that Agentforce is on. Salesforce planned to switch it on for every org in August 2026 (Enable Agentforce). If you still see the toggle in Setup > Agentforce Agents, turn it on.
- Wait before you retry. Data Cloud and Einstein can take 15 to 60 minutes to provision (readiness guide).
Data Cloud is now called Data 360. For when you need a full build, read does Agentforce require Data Cloud.
How do you set up the agent user safely?
Agentforce Service agents run as a dedicated agent user, not as the admin or the rep (readiness guide). That user starts with minimal access. The agent can only do what this user can do.
- Assign the permission set licenses. The guide names Agentforce Service Agent Builder, Agentforce Service Agent User, Data Cloud and Einstein Prompt Templates.
- Assign the agent user's permission sets. Use "Agentforce Service Agent Secure Base" and the "Agentforce Service Agent User" permission set group.
- Grant object access, and no more. A service agent needs Read and Create on
Caseand Read onContact. Add only the custom objects its flows, Apex and prompts touch. - Grant run rights. Add "Run Flows" for flow actions and "Execute Prompt Templates" for prompt actions.
- Give the agent user a role. Without one, sharing rules may hide the records it needs.
- Give builders one permission set. Use "Agentforce Service Agent Configuration" instead of granting Manage AI Agents and Manage Flows one by one.
Expected result: the agent can read a test Case and its Case.ContactId in a sandbox chat. If an action fails, check the agent user first, not the admin (readiness guide).
Wide access is the bigger risk. If the agent user can edit every Account, so can the agent. The org access risk quiz shows how exposed your current users are.
Is your data ready for an agent?
An agent answers from the fields it reads. A blank field gives it nothing to work with. Run these checks on the objects the agent will touch.
- Find blanks on key fields. Build a report on
Caserecords whereCase.ContactIdis blank, and onContactrecords whereContact.AccountIdis blank. Fix or close them. - Turn on duplicate rules. Go to Setup > Data > Duplicate Management > Duplicate Rules. Salesforce ships standard rules for accounts, contacts and leads (duplicate management). Activate them before the agent creates records.
- Clean picklists the agent filters on. "Closed Won" and "closed_won" on
Opportunity.StageNamelook like two stages to an agent. - Enforce required fields with validation rules. A field required only on the page layout can still be blank when an API call saves the record.
- Check grounding content. For a Data Library, review articles and PDFs for clear structure. Confirm the search index shows Ready status (readiness guide).
Will your automation fight the agent?
The agent updates a record. Then a flow or trigger fires and changes it again. To the user, the agent looks wrong. These checks find that clash.
- List every record-triggered flow per object. Open Flow Trigger Explorer from the Flows page in Setup. It shows all before-save and after-save flows for an object and trigger (Flow Trigger Explorer).
- Find old Workflow Rules. Go to Setup > Process Automation > Workflow Rules and sort by Active. Salesforce ended support for Workflow Rules and Process Builder on 31-12-2025 (Salesforce Help).
- Migrate what still runs. The Migrate to Flow tool handles many cases. The Process Builder to Flow guide covers what it skips.
- Check failed runs. In Setup, search Quick Find for Paused And Failed Flow Interviews and open it. A flow that fails quietly leaves records half updated.
- Look for Apex triggers that repeat flow logic. If a trigger and a flow both set
Case.Statuson save, one will overwrite the other.
How do you test the agent before launch?
Agentforce Testing Center runs batches of test prompts against an agent and checks the subagent (formerly topic), action and response it picks. It runs in a sandbox only (Testing Center considerations).
- Write test cases from real questions in your
Casehistory, including messy and rude ones. - Run them in a full or partial copy sandbox, so the agent reads real-shaped data.
- Log in as a test user with a sales or service profile and repeat the top cases. That checks the user's access, not just the agent's.
- Check the records after each run. Testing Center scores the agent's answer. It does not check every field the agent and your flows changed.
For a deeper guide, read Agentforce Testing Center vs real testing.
Which checks should you fix first?
Swipe sideways to see all columns
| Order | Area | Why first | Typical fix |
|---|---|---|---|
| 1 | Agent user | Most failed actions trace back to it (readiness guide) | Permission sets, object access, a role |
| 2 | Automation overlap | A clash makes a good agent look wrong | Flow Trigger Explorer review, retire Workflow Rules |
| 3 | Platform setup | Missing pieces fail at run time | Follow the enable order above |
| 4 | Data | Blank and duplicate records give wrong answers | Duplicate rules, validation rules, reports on blanks |
| 5 | Testing | Proves the first four in a sandbox | Testing Center plus manual checks by profile |
Fix data last only because it takes longest, not because it matters least. Start the data work in week one and let it run alongside the rest.
What does readiness cost compared with a launch?
A readiness check is cheap next to the launch it protects. As of October 2026, Salesforce lists Agentforce at $0.10 an action on Flex Credits, $2 a conversation, or $125 per user a month for an add-on (Agentforce pricing). Fixing an org mid-project adds partner hours that rarely appear in the first budget. The Agentforce implementation cost guide breaks down both lines.
How do you run this checklist with Clientell AI?
Clientell AI reads your org first and makes no changes during a scan. It drafts fixes in a sandbox, and it asks before it changes anything in production. See how Clientell AI keeps your org safe.
Try it in Clientell AI: "Check my org for Agentforce readiness: list the agent user's object access, every record-triggered flow on Case, and Contacts with a blank AccountId." Start the 14-day trial, no card.
Prefer a report first? Run the free, read-only Agentforce readiness audit. If the findings make you rethink the tool, compare Agentforce alternatives in 2026.
Common questions about the Agentforce readiness checklist
What does "ready" mean for Agentforce?
Salesforce publishes no readiness score. In practice, ready means the prerequisites are on, the agent user has the right access, and the data and automation it touches are clean enough to trust.
Which Salesforce editions support Agentforce?
Enterprise, Performance, Unlimited and Developer Editions (Set Up Your Agent). Some agent actions need extra add-on licenses.
Does Agentforce require Data Cloud?
Salesforce's Service Agent guide lists a provisioned Data Cloud as a prerequisite (readiness guide). A full Data 360 build is a separate choice that depends on your use case.
Why can my agent not see records?
The agent runs as the agent user, so check that user's role and object access first. Admin access does not carry over to the agent.
Is the Clientell AI readiness audit free?
Yes. The audit is free and read-only. See the audit page for what it covers.
Sources
Salesforce documentation
- Agentforce: Service Agent Readiness and Setup Best Practices Guide
- Set Up Your Agent
- Considerations for Testing Center
- Flow Trigger Explorer
- Workflow Rules and Process Builder End of Support
- Duplicate management
- Agentforce pricing
Last reviewed October 2026
Last updated: October 22, 2026




