The Short Answer
An Agentforce readiness assessment takes a few weeks; a failed pilot costs months and erodes internal trust. It's therefore worth answering five questions in advance: Is there a defined process with an owner? Is the data the agent will rely on reliable? Is there a maintained knowledge base? Is the permission model clear? And is there someone to operate the agent after launch?
The assessment isn't a yes/no question. It generates a score for each axis and a gap map, allowing for a more precise decision: to proceed, reduce scope, or defer and close a specific gap first.
The decision framework for Use Case suitability appears in Agentforce for Enterprises.
Five Readiness Axes
| Axis | Critical Question | Weakness Indicator | Minimum Threshold for Pilot |
|---|---|---|---|
| Process | Is the process defined and does it have a named owner? | Every team performs it differently, no documented process | One documented process with an Owner and known volume |
| Data | Are the fields the agent will read reliable? | Fields are empty or filled with free text | 90% completeness in critical process fields |
| Knowledge | Is there an approved source for answers? | Old or contradictory articles | 20 updated articles for common scenarios |
| Permissions | Is it clear what each user is allowed to see and do? | Broad and uncontrolled permissions | Mapping of Profiles and Permission Sets to the process |
| Operations | Who monitors, corrects, and approves changes? | No owner after launch | Operational Owner and weekly review routine |
Axis 1: The Process
The most common failure isn't technological. Organizations choose a process without an owner, and then there's no one to decide on questions that arise during construction: what happens in an exception, when to escalate, what constitutes a correct answer. Without a decision-maker, the technical team invents rules while the business operates with different expectations.
Practical test: Ask four people who perform the process to describe it in writing. If you get four significantly different versions, the process is not ready for agent automation—it's ready for documentation and agreement first.
Volume is also needed. A process that occurs ten times a month won't justify the cost of building and maintenance, even if it's annoying. A good candidate is a process with significant volume, high repeatability, and variation in inquiry phrasing—exactly where rigid rules break down.
Axis 2: The Data
Perfect data quality isn't required across the entire Org. Quality is needed in the fields the agent will read or update for the chosen process. The assessment is narrow and measurable: take the list of relevant fields and measure completeness, value consistency, and duplicates in related records.
Three tests that provide a quick answer: the percentage of critical fields filled, the number of duplicate records in the central object, and the percentage of cases where the necessary information comes from an external system rather than Salesforce. The third test is surprising—it uncovers a dependency on an integration that wasn't budgeted.
Free text is a particular red flag. When essential information lives in a comments field, the agent will have to infer it, which is precisely where hard-to-trace errors occur.
The recommended order for addressing data gaps is detailed in Salesforce Data Quality Metrics.
Axis 3: The Knowledge
Knowledge is assessed not by quantity, but by coverage and validity. Take the twenty most common inquiries and check for each: Is there an approved article, when was it updated, and who is the owner? Coverage of half the scenarios with up-to-date articles is better than full coverage with old articles.
An easily overlooked weakness: articles written for internal audiences only that are simultaneously used for customer responses. They may contain phrasing, prices, or exceptions that should not be exposed externally, and this separation must be done before connection.
The agent operates on behalf of a user, so the existing permission model becomes the AI's security model. If permissions are broad and uncontrolled today, the agent will increase exposure rather than create it. The assessment examines three things: who is authorized to read the data in the process, what write operations are required, and who approves a sensitive operation.
For every action the agent performs, it must be defined whether it is reversible. An irreversible action—financial credit, case closure, sending a message to a customer—requires a human approval point in the initial stage, and therefore affects process design, not just settings.
Planning approval points by risk is detailed in Human-in-the-Loop in Agentforce.
Axis 5: Operations
An agent isn't a project with an end date. It's a component that requires Traces monitoring, error handling, content updates, and cost control. An organization without someone to do this—even part-time—will see a gradual decline in quality within a quarter.
The minimum: a named operational owner, a weekly review routine for failed calls, an agreed-upon change process for updating Instructions, and a monitored monthly budget. If none of these four exist, the gap on this axis is larger than it appears at the outset.
Translating the Score into a Decision
| Status | Interpretation | Recommended Action |
|---|---|---|
| All axes at or above threshold | Fully ready | Pilot on one process with Go/No-Go criteria |
| Weakness only in Operations | Can be compensated with support | Pilot with external support and parallel internal capability building |
| Weakness only in Knowledge | Focused content gap | Four to six weeks of Knowledge training, then pilot |
| Weakness in Data or Permissions | Significant risk | Do not start agent; close the gap as a separate project |
| Weakness in three or more axes | Organization not ready | Choose a narrower sub-process and re-assess |
Scenario: Financial Organization Discovers the Wrong Process Was Chosen
A financial organization requested an agent to handle customer detail change requests. The readiness assessment revealed that the process goes through two external systems, every change requires regulatory approval, and monthly volume is modest. The Permissions and Data axes scored low.
During the same assessment, another process emerged that no one had considered: answering status questions about existing requests. It relied on one reliable field in Salesforce, involved no write operations, and its volume was eight times higher. The pilot was shifted to this process.
The practical outcome of the assessment was not "ready or not ready", but a candidate replacement. This is the main contribution of a readiness assessment—it's cheap enough to run on three candidates and select the one with the fewest dependencies.
Readiness Checklist
- ☐ A single candidate process with a named owner is chosen
- ☐ Monthly volume and repeatability rate are measured
- ☐ Completeness of critical process fields is checked
- ☐ Duplicates in the central object are checked
- ☐ Dependencies on external systems are identified
- ☐ Knowledge coverage for the twenty most common inquiries is mapped
- ☐ Internal content is separated from customer-facing content
- ☐ Read and write permissions for the process are mapped
- ☐ Reversible versus irreversible actions are classified
- ☐ An operational owner and post-launch review routine are defined
When an external party is needed to conduct the assessment and translate it into a Roadmap, Agentforce and AI Services is the practical path forward.