The platform's agent layer
Agentforce agents live inside Salesforce. They read the same records your team reads, act through the same APIs, respect the same permissions, and leave the same audit trail. Grounded in Data 360, they reason over one real-time view of the customer instead of a stale export.
That placement is the point: the agent is not a chat window beside the CRM. It is a worker inside it.
What consuming actually means
An agent consumes when it processes real work in production. Every case it reads, every action it takes, is consumption. A proof of concept that sits in a sandbox consumes nothing, which is exactly why so many Agentforce stories end at the demo.
When a rep or a buyer asks whether an Agentforce deployment is real, consumption is the honest test. Deployed and consuming means the agents are doing the work today, at volume, with the numbers to show for it.
What a consuming journey looks like
Our six-agent journey runs the customer lifecycle end to end, from first match to first response.
Listing Match & Outreach
Matches against the pool and reaches out proactively, with no manual prompting.
Viewing Coordinator
Books, confirms and reschedules across calendars autonomously.
Pattern Detector
Catches systematic failures before customers do.
Noise Filter
Keeps 60-80% of false cases away from the support team.
Resolution Recommender
Cuts time to resolution with historical context.
First Response
Takes routine cases from hours to seconds, 24/7.
Real estate is one expression of the journey. The same agents, recalibrated, run a service queue or a connected-asset estate.