What "Agentforce 360" actually means
Agentforce 360 is the umbrella for every agent surface inside Salesforce: customer-service agents that resolve cases, sales agents that nudge reps mid-deal, marketing agents that draft journeys, and the long tail of custom agents you build in Agent Builder. The "360" suffix mirrors Customer 360 and signals that one agent identity has access to the same unified customer record across clouds.
The four building blocks
Every Agentforce deployment combines the same four primitives. Knowing these by name is the fastest way to read a Salesforce architecture diagram.
- Atlas Reasoning Engine - the planner that decides which agent action to call next.
- Agent Builder - the low-code surface where admins assemble topics, instructions, and actions.
- Data 360 - the grounding layer that gives agents access to customer data without copies.
- Agent Actions - the library of pre-built and custom actions agents can invoke (Apex, Flow, Prompt Templates, MuleSoft APIs).
When Agentforce earns its keep
High-volume, low-judgement workflows where the cost of a junior employee + their context-switch overhead outweighs the per-task cost of an agent. Tier-1 service triage, lead qualification, post-call summarisation, and renewal outreach are the early wins.
Where it falls down today
Agentforce is opinionated about grounding through Data 360. If your customer data lives in 12 systems with no MDM strategy, expect 4-6 weeks of data plumbing before the first agent ships. Pricing also runs on a Flex Credits model that rewards predictable usage; ad-hoc workloads are expensive.