Salesforce MVP Hall of Fame · Certified Partner since 2010
A Salesforce-native agent, only when the desk is here.
The first week is in the org, reading what already exists. Agentforce inherits sharing, topics, and actions. We implement it when service, sales, or internal queries live in the CRM. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks
Practice
The Agentforce work we actually take.
Enablement happens in your org. These are the decisions we will ask you to make before anyone builds.
Agentforce Network
Brokers, A2A, and a registry. Not a pile of prompts that call each other.
Agent Broker
Guided determinism. Not every hop is a model call.
Trusted identity
On-behalf-of. The agent acts as the user, or we will not call it production.
Governed path
Every tool call and model call through a MuleSoft gateway.
Agent Fabric
One register of the agents, tools, and policies touching Salesforce, with the traces to match.
When we refuse
Slack-first teams run Agentforce in Slack when the work and permissions live in Salesforce. Work across other tools, warehouse-first data, or a model Salesforce will not host goes custom or Claude.
Enablement
Turn it on in the org. Then govern it.
Connected apps, Einstein, and topics are the floor. They are not the program.
Retrieval
One matching shape, more than one desk.
Graph for relationships. Vectors for similarity. MCP tools behind a gateway. Same shape at more than one desk.
Peers
One runtime among several.
Agentforce is the right seat when the work and the permissions live in the org. It is not the ceiling: it delegates to code agents and takes work back from them.
Questions
What we actually say.
- Is Agentforce the same as Einstein Copilot?
- No. Einstein recommends. Agentforce acts. If a partner conflates them, they have not shipped this.
- Do we need Data Cloud first?
- You need grounded, permissioned context. Sometimes that is Data Cloud. Sometimes it is clean Knowledge and a sharing model that already works. We will not quote a build before that check.
- When do you refuse Agentforce?
- When the work spans tools Salesforce does not hold, when the system of record is a warehouse or ERP, or when you need a model Salesforce will not host. Then we assemble a custom stack, often Claude, and connect it.
- Can a Slack-first team run Agentforce?
- Yes. Agentforce now runs inside Slack, so the team asks in the channel and the agent answers from Salesforce with Salesforce permissions. That fits when the work and permissions live in Salesforce. When the job spans other tools, we put Claude or a custom agent in Slack instead.
Next
What to read next.
From the blog
What Agentforce will cost to run.
Research-led notes on pricing and control before you renew.
The brief · one email
Name the desk. Name the record.
We will tell you Agentforce, a custom runtime, or neither.