Implementing Agentforce: What Changes in Salesforce
Agentforce agents choose their own actions, which raises the stakes on data quality, permissions and team metrics. What changes, and what to fix first.
By Abhineet Jain, Product HeadUpdated November 8, 2026Agentforce, Salesforce, Agentic AI, RevOps
Most teams first treat Agentforce the way they treated Flow, as one more automation surface to configure. That is enough for a convincing demo, and teams that stop there rarely reach a deployment. With a flow, the admin settles every branch at build time. With an agent, the agent itself picks which configured action to run, at request time. Flows and Apex still do the work inside each action, but the decision about the next step has moved, and most of what follows comes from that shift.
Data quality comes first
Rule-based automation can live with messy data, because a person usually reads the record afterward and makes allowances for what is wrong. An agent takes the record at face value and acts on it, many times a day, with nobody reading over its shoulder.
Before any agent work starts, audit the objects the agent will read and write:
- Find out which fields anyone still maintains and which were abandoned years ago. An agent treats them all the same.
- Merge duplicates. If one customer exists as three accounts, an agent asked about that customer may give three answers.
- Fix broken relationships. People learn to ignore a contact still attached to a closed account, or a case with no parent, but an agent treats both as current.
This work is slow and shows nothing in a demo, yet it does more for the final result than anything else on the plan. When an Agentforce program stalls, it is usually stuck here.
Permissions stop being an IT detail
What an agent can touch depends on whose access it runs with. Agents in employee channels such as Lightning Experience or Slack are limited by default to what the person using them can reach. Service agents on customer channels need deliberate setup, and Salesforce’s own guidance is to grant them only the actions and access the job requires. The useful test is the worst outcome an agent could produce while working exactly as configured.
Give each agent its own narrowly scoped permission sets, and avoid reusing a broad integration user. Then decide, action by action, which ones need a person to confirm them. Refunds, credits, contract changes and anything else that moves a customer’s money or commitments usually belong on that list. For sensitive actions, Salesforce also recommends building customer verification into the action’s flow.
The operating model shifts from tickets to exceptions
Agents pay back most when they take the routine tier of work off the team entirely, which leaves people with the cases that need judgement. Handling today’s tickets slightly faster is worth far less.
That changes how the team is measured. Once the routine queue is gone, queue depth says little, and exception rate and escalation quality become the numbers to watch. Teams that keep the old metrics tend to conclude the agents achieved nothing, because the dashboard is still counting work that was removed on purpose.
Where agents tend to pay back first
The best early candidates are high-volume processes with clear rules and a defined path for exceptions. In commerce and operations, that often means:
- Cart recovery, order routing, and post-purchase problems such as late shipments or address changes.
- Multi-step back-office work that crosses teams, for example finance approvals or product lifecycle changes.
Start with one of these and keep its scope tight until it has proved itself.
Build governance in from the first release
Every agent should go live with guardrails, an audit trail and a route to a person. If logging arrives only after launch, the first incident will come before you can explain it, and someone will ask what the agent did and why while you have no record to answer from.
That record is also what earns the trust of a compliance team, which otherwise tends to accept an agent reluctantly at best.
A realistic sequence
- Audit and clean the data on the objects in scope.
- Define the permission model and escalation policy before the build starts.
- Deploy one narrow, high-volume workflow with full logging.
- Redefine measurement around exceptions.
- Widen scope only once step 3 has run cleanly under real load.
Step one is the main body of work. Programs that treat it as paperwork to clear before the real project begins are the ones that struggle.
Cube27 implements Agentforce and runs Salesforce in production through Salesforce & enterprise platforms and Agentic AI & automation. Talk to a Solutions Architect about your Agentforce rollout.