- Salesforce Managed Services
Agentforce 360 is Salesforce’s current agentic AI platform. It bundles the agent-building tools sold before as standalone Agentforce, the renamed Data 360 (formerly Data Cloud), Customer 360 Apps, and a new Enterprise MCP Registry into one connected system. It reached general availability on October 13, 2025, at Dreamforce, the fourth major release since Agentforce first shipped in September 2024.
In plain terms, Agentforce 360 lets a company build AI agents that look up information, take action inside Salesforce and beyond it, and hand off to a person when a task needs judgment. Pricing runs on three separate models that don’t mix inside one org: pay-per-conversation, Flex Credits, or a per-user license. Salesforce reports that Agentforce and Data 360 combined have crossed $2.9 billion in annual recurring revenue. Gartner, on the other hand, expects a meaningful share of agentic AI projects across the industry to get canceled by 2027 over cost and unclear ROI.
This guide covers every component, what each edition actually costs, what changed through 2026, how the numbers hold up against independent research, and how to tell if Agentforce 360 actually fits your business before you sign anything.
TL;DR
One platform, four releases, one rebrand
Agentforce 360 pulls Salesforce’s agent-building layer, Data 360, Customer 360 Apps and the Enterprise MCP Registry into a single bundle that went GA in October 2025. Knowing what each piece does and which release added it is the fastest way to read any Agentforce quote accurately.
Where Agentforce budgets actually break
Three pricing models that cannot mix in one go: a Data 360 line that often lands near $60,000 a year and gets quoted late, and flex credits that burn five to eight actions in a single messy support conversation. The license number is rarely the number that matters.
What we check before you sign
We map the failures nobody demos: topic misclassification, agent-user permission errors between sandbox and production, and tests that pass while the answer is still wrong. As a certified Salesforce partner, we size the licensing with you before the contract, not after.
What is Agentforce 360?
Agentforce 360 is Salesforce’s umbrella name for its full agentic AI stack. Before October 2025, “Agentforce” referred to the agent-building and runtime layer on its own, sold and evaluated as one product among several. Agentforce 360 folds that layer together with Data 360 (the data foundation), Customer 360 Apps (the Sales, Service, Marketing, and Commerce products most Salesforce customers already run), and an Enterprise MCP Registry that governs which outside tools and data sources an agent is allowed to reach.
The core idea hasn’t changed since version 1.0. An agent reads a request, decides what to do about it, takes an action, and either resolves the case or hands it to a human. What’s changed is how much of that decision-making the platform now does on its own and how tightly it’s grounded in a company’s actual CRM data rather than a general-purpose model’s training data.
That grounding is the real differentiator. A generic AI chatbot answers from what it learned during training, which means it can sound confident about your return policy while being completely wrong about it. Agentforce 360 answers from your accounts, your cases, your product catalog, and your actual policies, because it’s built on top of Salesforce rather than bolted onto it. That’s also why migrating an existing chatbot or copilot deployment onto Agentforce tends to be a rebuild rather than an import.
Einstein Copilot was folded into this stack before the 360 rebrand. It was retired in January 2025 and renamed, with no change in functionality, to an Agentforce agent type. If you see “Einstein Copilot” in older documentation or an old implementation plan, it’s what you’d now call an Agentforce agent. Salesforce has also started calling the whole product line a “Digital Labor Platform,” which signals how it wants the category understood: agents as labor a business hires and manages, not a feature attached to a support widget.
A quick history: from Agentforce 1.0 to Agentforce 360
Salesforce has shipped four major Agentforce releases in a little over a year, and most competitor content on this topic either buries the version history or leaves it out entirely. Here it is in one place.
Agentforce 1.0 | September 2024 | The first agentic layer on Salesforce. Autonomous agents for customer-facing and internal use cases. |
Agentforce 2.0 | December 2024 | The Atlas Reasoning Engine, which lets an agent plan and execute multi-step tasks instead of matching a single intent to a single action. |
Agentforce 3.0 | June 2025 | Command Center for observability into agent behavior in production, plus support for the Model Context Protocol (MCP). |
Agentforce 360 | October 13, 2025 | Bundled Data 360, Customer 360 Apps, and an Enterprise MCP Registry with the platform. Added Agentforce Builder, Agent Script, and native Agentforce Voice. |
Agentforce 1.0 moved Salesforce from chatbots and rule-based automation into agents that could take real action across a case. Agentforce 2.0 mattered because the Atlas Reasoning Engine was the first version that could handle a request requiring more than one step. Agentforce 3.0 was less about new capability and more about production readiness: Command Center gave admins visibility into how agents were actually behaving with real customers, and MCP support opened the door to connecting agents to tools outside the Salesforce ecosystem.
Agentforce 360 is the version that stitched everything into one story. Instead of separately evaluating Agentforce, Data Cloud, and your existing Sales or Service Cloud, you’re now evaluating one bundled platform where those pieces are meant to work together by default.
A few retirements sit alongside this timeline and matter if you’re maintaining an older Salesforce deployment. Legacy Chat, also known as Live Agent, was retired around February 2026, which pushed any remaining chatbot-only customers toward Agentforce whether they’d planned the move or not. Einstein Bots and Agentforce share no authoring objects, so a move from Einstein Bots to Agentforce is a full rebuild, not an upgrade path, and that’s worth budgeting for separately if you’re still running Einstein Bots anywhere in your org.
Every major component of Agentforce 360
Agentforce 360 isn’t one product wearing a new name. It’s a set of distinct components that work together, and understanding each one makes the pricing and evaluation sections later in this guide much easier to follow.
Agentforce 360 Platform. This is the core layer where agents actually get built, deployed, and run. When most people say “Agentforce” in casual conversation, this is what they mean, even though it’s technically just one piece of the broader 360 bundle.
Data 360. The renamed Data Cloud. It unifies customer data pulled from across your systems, CRM records, transaction history, support tickets, and more, so an agent has something accurate and current to ground its answers in rather than guessing. This is also the component that carries the hidden cost most buyers don’t budget for, which the pricing section below covers in detail.
Customer 360 Apps. Your existing Sales, Service, Marketing, and Commerce products, now built to be agent-aware so they can trigger an Agentforce agent and receive a handoff back from one. If you’ve already invested years into configuring these clouds, that configuration carries forward into how your agents behave.
Enterprise MCP Registry. A governance layer built around the Model Context Protocol, an open standard for connecting AI agents to outside tools and data sources. The registry is what controls which external connections an agent is actually allowed to use, which matters a lot for security and compliance teams evaluating this platform.
Atlas Reasoning Engine. Introduced in Agentforce 2.0, this is what lets an agent break a complex request into a sequence of steps and work through them, instead of matching one intent to one pre-built response. It’s the difference between an agent that can answer “what’s my order status” and one that can also handle “my order arrived damaged, I need a replacement shipped to a different address, and please update my billing info too.”
Agent Script. A deterministic, rules-based control layer that sits alongside the Atlas Reasoning Engine. Salesforce added this after its own leadership publicly signaled reduced confidence in letting an agent act with pure, unconstrained autonomy. Agent Script lets admins pin down exactly what an agent can and can’t do in specific, sensitive situations, which is increasingly where serious implementations spend their design time.
Agentforce Builder. A conversational, natural-language tool for building and editing agents, meant to lower the technical bar so business teams, not only developers, can create and adjust one.
Command Center. Added in Agentforce 3.0, this gives admins real visibility into how agents are performing and failing once they’re live, rather than relying on spot checks or customer complaints to catch problems.
Agentforce Voice. Native voice capability, generally available at Dreamforce ’25. It integrates with existing contact-center systems, including Genesys, Five9, Amazon Connect, NiCE, and Vonage, rather than trying to replace that infrastructure outright. This matters if your contact center already runs on one of those platforms, since it changes the integration conversation significantly.
Intelligent Context. Grounds agent responses in unstructured data, PDFs, internal wikis, policy documents, not only the structured records that live in CRM fields. This closes a real gap for companies whose institutional knowledge lives in documents rather than database tables.
Agentforce Vibes. An enterprise “vibe coding” IDE built around an agent called Vibe Codey, launched October 2, 2025. It’s aimed at developers building on the platform itself, not at customer-facing agents, so don’t confuse it with the components above when you see it in release notes.
How the components fit together
It helps to picture the flow rather than memorize the component list on its own. Data 360 grounds an agent in unified, accurate customer data before it ever responds to anything. The Atlas Reasoning Engine and Agent Script then decide what the agent should actually do with a given request, one handling flexible multi-step reasoning and the other enforcing hard boundaries the agent can’t cross. Agentforce Builder is where a team actually constructs that logic, whether that’s a developer working in detail or a business user working conversationally. The Enterprise MCP Registry decides what outside systems the agent is allowed to reach while it works, which keeps a support agent from suddenly having access to your finance system just because someone connected it once for a different project. Command Center watches all of this once it’s live and flags where behavior is drifting from what was intended. And Customer 360 Apps, meaning Sales, Service, Marketing, and Commerce, are where the agent actually shows up to your team and to your customers.
Walk a real support case through it. A customer submits a question through Service Cloud. Data 360 pulls their account history so the agent has real context. The Atlas Reasoning Engine figures out this is a two-step request, a return plus a billing update, and Agent Script confirms the billing change falls within limits the agent can make on its own. The agent executes both, and Command Center logs the interaction for later review. None of these pieces does much in isolation. The value is in how tightly they’re wired together, which is also why moving into or out of this stack tends to be a rebuild rather than a configuration swap.
Agentforce 360 editions and pricing explained
Agentforce 360 pricing runs on three separate models, and Salesforce doesn’t currently let you mix them inside a single org. Picking the right one up front matters more than it sounds like it should, because switching later means rearchitecting how usage gets tracked and billed.
|
|
|
Pay-per-conversation | $2 per conversation (a 24-hour session) | Customer-facing agents with unpredictable or spiky volume |
Flex Credits | $500 per 100,000 credits. A standard action costs about 20 credits (~$0.10); a voice action costs about 30 credits (~$0.15) | Mixed internal and external use where you want granular, usage-based billing |
Per-user editions | Agentforce add-on: $125/user/month. Industries add-on: $150/user/month. Agentforce 1 Edition: from $550/user/month | Predictable, seat-based budgeting for heavy internal agent use |
Pay-per-conversation is priced per 24-hour session, not per message, so a customer who asks five follow-up questions within the same day still counts as one conversation. This model tends to fit best when volume is genuinely unpredictable, seasonal spikes, a new product launch, a support surge after an outage, since you’re never paying for capacity you don’t use.
Flex Credits launched in May 2025 and suit organizations still figuring out how much agent usage they’ll generate. A standard action, looking up an order or updating a field, costs around 20 credits, roughly ten cents. A voice action runs about 30 credits, roughly fifteen cents. That granularity is useful, but a single complicated support interaction can burn five to eight actions, which adds up faster than teams expect in the first few months.
Per-user editions work best when agent usage is heavy, predictable, and mostly internal, think an operations team using agents constantly throughout the day rather than a customer occasionally messaging in. The Agentforce add-on runs $125 per user per month, the Industries add-on (built for sector-specific workflows) runs $150 per user per month, and the full Agentforce 1 Edition starts at $550 per user per month for organizations that want the complete platform bundled into one license.
The number that catches most buyers off guard isn’t on the table above at all. Data 360 is priced and billed separately from Agentforce licensing, and practitioners and consultancies report it typically starts near $60,000 a year, often quoted to a buyer only after the Agentforce conversation is already well underway. It’s easy to budget around the $2-per-conversation number or a straightforward per-user fee and then discover, mid-implementation, that the data foundation underneath it costs more than the agent layer itself.
If your evaluation touches revenue operations specifically, quoting, renewals, billing, it’s worth looking at Agentforce Revenue Management directly, since that piece runs on a different cost basis again. Revenue Cloud Advanced, the platform underneath it, lists at $200 per user per month, and it ties directly into the Salesforce CPQ migration question covered later in this guide. This is also one of the places where a partner-side view of licensing tends to save real money, which we cover further down.
A quick example makes the pricing decision easier to reason about. A support team handling 2,000 customer conversations a month would spend roughly $4,000 on pay-per-conversation pricing. That same team, run as five full-time agents on the Agentforce add-on, would cost $625 a month in per-user licensing instead, plus Data 360. The crossover point is usually somewhere between a few hundred and a couple thousand conversations a month, depending on how many people actually need seat access versus how much of the work is genuinely agent-driven. Running the math on your own volume before committing to a model, rather than defaulting to whichever one a sales rep leads with, is worth the extra hour it takes.
Key Agentforce 360 terms to know
A handful of terms come up constantly in Agentforce documentation and sales conversations, and knowing them up front makes the rest of an evaluation go faster.
Agent: the autonomous unit built to handle a specific job, from answering a support question to qualifying an inbound lead.
Topic: a category of user intent an agent is trained to recognize, like “billing question” or “password reset.” Misclassifying a topic is the single most common way an Agentforce deployment goes wrong, covered in more detail in the evaluation section below.
Action: a concrete task an agent can execute, such as an API call, a Salesforce Flow, or an Apex method. An agent’s usefulness is really a function of how many well-built actions it has access to.
Atlas Reasoning Engine: the reasoning layer that lets an agent plan and carry out a multi-step task rather than responding to a single intent.
Agent Script: the deterministic, rules-based layer that constrains exactly what an agent is and isn’t allowed to do.
MCP, or Model Context Protocol: an open standard for connecting an AI agent to outside tools and data sources, governed inside Agentforce 360 by the Enterprise MCP Registry.
Flex Credit: the consumption-based currency used to pay for individual agent actions under the Flex Credits pricing model.
Grounding: the process of connecting an agent’s answers to verified, real data instead of letting it rely on a model’s general training, which is the entire reason Data 360 exists as a component.
Agent User: the internal Salesforce user record an agent runs as, and the source of most of the sandbox-to-production permission errors covered in the evaluation section.
Data 360: Salesforce’s unified customer data platform, formerly known as Data Cloud, renamed as part of the Agentforce 360 bundle.
What changed with Agentforce in 2026
Most of the big architectural changes, the 360 rebrand itself, the Enterprise MCP Registry, native Voice, landed at Dreamforce in October 2025. What 2026 actually brought was scale, real production usage at a level the platform hadn’t seen before, and a much clearer picture of where it still struggles.
By Salesforce’s fourth-quarter fiscal 2026 results, reported on February 25, 2026, Agentforce ARR alone had reached roughly $800 million, up 169% year over year, with Agentforce and Data 360 combined exceeding $2.9 billion, including $1.1 billion in Informatica Cloud ARR. The company also reported more than 29,000 Agentforce deals closed since launch, with Agentforce accounts in production increasing nearly 50% quarter over quarter. Salesforce introduced a new metric during this period, Agentic Work Units, meant to measure actual agent output rather than raw token consumption, reporting 2.4 billion delivered to date. By the first quarter of fiscal 2027, Agentforce ARR had climbed further to about $1.2 billion.
Legacy Chat, Salesforce’s older Live Agent product, was formally retired around February 2026, which meant any customer still running it had to move to Agentforce whether or not that was already on their roadmap for the year.
The more interesting shift through 2026 was cultural rather than a single product release. Forrester reported limited measurable adoption or impact from AI agents around Dreamforce 2025, and Salesforce’s own leadership had already signaled reduced confidence in letting agents act with pure, unconstrained autonomy. That’s a big part of why Agent Script, the deterministic control layer, got noticeably more attention through 2026 than it did at launch. As more customers moved from pilot projects into real production usage, the practitioner community also started documenting concrete, unresolved failure patterns rather than theoretical risks, which the evaluation section further down covers directly.
Real-world results: adoption and ROI
The published wins are genuinely strong, when they come from real, named deployments rather than marketing copy with no attribution behind it.
Wiley, a publisher, used Agentforce alongside Service Cloud to onboard seasonal support agents 50% faster during peak enrollment periods, which contributed to a 213% return on investment and $230,000 in documented savings, according to Salesforce’s published Wiley case study.
OpenTable’s restaurant-facing agent hit 73% case resolution within three weeks of launch, and the company now handles roughly 11,000 conversations a week across its combined restaurant and diner agents, a 40% improvement over its prior chatbot, based on details in Salesforce’s OpenTable case study.
Salesforce’s own support site is arguably the most closely watched deployment of all, since it’s the vendor running its own product on its own platform with nothing to hide behind. Across more than 500,000 customer conversations, Agentforce has resolved more than 84% of questions coming through help.salesforce.com, with only 4% of conversations requiring handoff to a human support engineer, according to Salesforce’s own account of the rollout.
Those top-line numbers hold up reasonably well against broader industry benchmarks too. Enterprise median case deflection sits around 41% in a deployment’s first year, top-quartile performers reach roughly 59%, and mature Data Cloud deployments with significant grounding work behind them report deflection rates in the 70-90% range.
The necessary counterweight to all of this is Gartner’s prediction that over 40% of agentic AI projects across the industry, not specific to Salesforce, will be canceled by the end of 2027, driven by escalating costs, unclear business value, or inadequate risk controls. Gartner also notes that only a fraction of vendors claiming agentic capability actually deliver it, a pattern it calls “agent washing.” Published case studies show what’s achievable under good conditions with a well-resourced team. They don’t show the base rate across every company that signs a contract, and the base rate matters more once you’re the one responsible for the outcome.
What to check before you commit
A handful of things are worth confirming before you sign anything, because they show up in real production environments far more often than a vendor demo would suggest.
Total cost, not just the license line. Add Data 360 (commonly around $60,000 a year), implementation services, and ongoing prompt and workflow tuning to whichever pricing model you’re evaluating. The sticker price on any single component rarely reflects the actual annual budget you’ll need.
Topic and action misclassification. Salesforce’s own admin documentation names “the wrong topic is chosen” and “the wrong action is chosen” as the two most common failure modes in live deployments. Ask whoever is implementing for you exactly how they test for this before go-live, not after customers start noticing. It’s a fair question to put to us too, and we’d rather answer it during scoping than after launch.
The sandbox-to-production gap. A recurring, well-documented issue is an Agent User permission error, specifically INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, where an agent works perfectly in a sandbox and then fails once it goes live. Some Data Library custom retrievers show “Ready to use” and pass cleanly in the Retriever Playground, then fail at runtime with that same kind of permissions gap, an open issue the Trailblazer Community has been actively tracking since a thread from May 2026.
Tests passing while the output is still wrong. Automated tests can confirm an agent responded and still completely miss that the response itself was hallucinated. Manual review of real, messy conversations matters more here than it typically does for traditional software QA, where a passing test is usually a reliable signal.
Flex-credit consumption running away. A single complicated support interaction can burn five to eight actions under the Flex Credits model. That’s manageable with monitoring in place and a genuine surprise without it, especially in the first few months after launch when nobody yet has a feel for what normal usage looks like.
One caution on statistics you’ll see cited elsewhere. Some of the more dramatic failure numbers circulating online, claims along the lines of “77% of implementations fail on dirty data,” trace back to consultancies selling competing products, with no audited or named source behind them. Treat any statistic without a specific, checkable source as directional at best, not as established fact.
Agentforce 360 compared with the alternatives
Agentforce 360 isn’t the only agentic AI platform on the market, and it’s worth understanding roughly where it sits relative to the rest of the field, even though a full head-to-head comparison is outside the scope of this guide.
Agentforce 360 | Native Salesforce CRM and workflow data | Strongest when you’re already running Salesforce as your system of record |
Microsoft Copilot Studio | Microsoft 365 and Dynamics integration | Better fit inside a Microsoft-first stack |
ServiceNow AI Agents | IT service management workflows | Ranked #1 in the 2025 Gartner Critical Capabilities report for AI agents, strongest for ITSM use cases |
Genesys / Five9 | Contact-center infrastructure | Agentforce Voice integrates with these platforms rather than replacing them |
A broader set of AI customer-experience tools competes for some of the same budget, including dedicated conversational AI vendors and voice-first support platforms. Most compete on breadth across CRM systems rather than depth inside any one of them, close to the inverse of Agentforce 360’s positioning.
The honest takeaway is that Agentforce 360’s biggest advantage is depth of integration with data you already hold in Salesforce, not raw model capability, which is broadly comparable across serious platforms in this category. If most of your customer data lives outside Salesforce, that advantage shrinks considerably, and we’d tell you as much rather than push a fit that isn’t there.
Which edition or capability fits your business
The right starting point depends less on company size on its own and more on where the actual workload sits and how predictable that workload is.
If you’re testing a single use case before committing further, pay-per-conversation pricing keeps the initial cost proportional to real usage, and it’s the lowest-risk way to validate one agent before expanding into a second or third.
Sales-heavy organizations tend to start with Agentforce for Sales or a dedicated Agentforce SDR Agent, automating lead qualification, follow-ups, and pipeline updates so reps spend more of their time on opportunities that are actually worth closing rather than administrative busywork.
Support-heavy organizations generally see the fastest, most measurable win from Agentforce for Service, which is also where most of the published ROI numbers cited earlier in this guide actually come from.
Marketing teams looking to automate campaign execution, lead nurturing, and audience segmentation without adding headcount are the natural fit for Agentforce Marketing.
Regulated industries, healthcare in particular, need to weigh governance, data handling, and compliance requirements before deployment more heavily than a typical rollout would, which is exactly where Agentforce for Healthcare focuses its approach.
Companies facing the Salesforce CPQ end-of-sale deadline are working under a different kind of urgency than most of the categories above. CPQ went end-of-sale on March 19, 2025, with no official end-of-life date published yet, though the ecosystem broadly expects one somewhere around 2029-2030 based on Salesforce’s usual end-of-sale-to-end-of-life cadence. There’s no automated migration tool available, and because CPQ runs on managed-package custom objects while Revenue Cloud Advanced runs on standard platform objects, the move is a genuine reimplementation rather than an upgrade, typically running $100,000 to $500,000 on top of license costs. Agentforce Revenue Management is the natural landing spot for that migration, and it’s worth starting the evaluation well before the deadline forces a rushed decision. We handle both sides of that move, the licensing structure and the reimplementation itself, and starting early is what keeps the cost at the lower end of that range.
Organizations with a lot of external tools and data sources an agent needs to reach, internal systems, third-party APIs, legacy databases that predate Salesforce, should budget extra time specifically for Agentforce integration services, since that’s usually where an otherwise straightforward rollout slows down the most.
A realistic path to getting started
Whichever edition you start with, a rollout that avoids the pitfalls above tends to follow the same shape. Start with one well-scoped use case rather than automating a whole department at once, since a narrow first deployment is far easier to test and to walk back. Get Data 360 grounded correctly before building agent logic on top of it, because an agent grounded in inconsistent data will confidently produce wrong answers no matter how well the reasoning layer is configured. Write Agent Script rules for the sensitive actions you don’t want handled autonomously, refunds above a threshold, account deletions, anything with legal or financial weight. Test in a sandbox that mirrors production permissions, not just production data. Launch with Command Center monitoring on from day one. Then expand only once the first use case is genuinely stable, not just technically live.
Buying Agentforce 360 through a certified Salesforce partner
There’s a part of this decision that rarely makes it into product guides, and it’s the part that usually costs the most money: how you actually buy.
VALiNTRY360 is a certified Salesforce partner, which means we sit on the same side of the table as you during the licensing conversation rather than across from it. In practical terms, we can look at your real usage projections and tell you which of the three pricing models genuinely fits, instead of whichever one is easiest to sell. We can flag the Data 360 line before it appears late in a quote and breaks a budget signed off months earlier. And because we work across the full Salesforce product line, not just Agentforce, we can look at your existing Salesforce, Service Cloud, Marketing Cloud and Data 360 commitments together and structure scope around what you’ll actually use.
That last point matters more than it sounds. Most Agentforce quotes get evaluated in isolation, separate from the Salesforce spend a company already carries. Looked at together, there’s usually room to right-size an edition, adjust seats against consumption, or sequence a rollout so you aren’t paying for capacity a year early. We do that analysis as part of scoping, not as a separate engagement.
The same applies well beyond Agentforce. Whether you’re renewing existing licenses, adding a new cloud, weighing Revenue Cloud Advanced against staying on CPQ a while longer, or evaluating Data 360 on its own, we can bring you the partner-side view of what’s available and what’s negotiable before you commit to a number.
How we approach Agentforce 360 implementations
Implementing Agentforce 360 well is less an AI problem than it is a data and architecture problem. Getting Data 360 grounded correctly, scoping Agent Script rules so an agent doesn’t overstep its intended boundaries, and testing thoroughly for the sandbox-to-production gaps covered earlier all take genuine Salesforce-specific experience, not just general familiarity with AI tools.
At VALiNTRY360 we work across Salesforce implementation and consulting broadly, not only Agentforce rollouts, which matters because most Agentforce projects touch existing Sales, Service, and Marketing configurations carrying years of prior customization. You can see examples across our Salesforce case studies, covering Sales Cloud and Service Cloud rollouts, data migrations, and territory management.
If you’re still weighing whether Agentforce 360 fits your business, or you’re already committed to it and want help avoiding the pitfalls this guide covers, talk to our team about your specific setup before you scope the project. We’d rather help you size it correctly up front than fix it after launch.
FAQ’s
- What is the Atlas Reasoning Engine in Agentforce 360?
It is the layer that lets an agent plan and execute multi-step tasks rather than matching one intent to one response. It was introduced in Agentforce 2.0 and remains the core reasoning component today. - Do I need Data 360 to run Agentforce 360?
Practically, yes for most real deployments. Data 360 grounds agents in unified customer data. Without it, agents answer from limited context and produce unreliable results, which is why it is billed separately. - How long does an Agentforce 360 implementation usually take?
It depends on scope and data readiness. A single well-scoped use case moves faster than a multi-department rollout. Most delays come from grounding data correctly, not from building the agent itself. - What is the Model Context Protocol in Agentforce?
MCP is an open standard for connecting AI agents to external tools and data sources. The Enterprise MCP Registry governs which of those connections an agent is actually permitted to use. - Can Agentforce agents work outside of Salesforce?
Yes, through MCP connections and API actions. The Enterprise MCP Registry controls which external systems an agent can reach, which keeps a support agent from accessing unrelated internal systems. - What is Agent Script and why does it matter?
Agent Script is a deterministic, rules-based control layer that constrains what an agent can do. It matters most for sensitive actions like refunds, account changes, or anything with financial or legal weight. - Is Agentforce 360 available for Salesforce Essentials or smaller editions?
Availability depends on your current Salesforce edition and licensing. Smaller editions often require upgrades before Agentforce becomes viable, which is worth confirming during licensing review rather than after purchase. - How do you measure whether an Agentforce agent is working?
Case deflection rate, resolution accuracy, and handoff rate are the usual measures. Command Center provides production visibility, but manual review of real conversations catches hallucinated answers that automated tests miss. - What skills does my team need to maintain Agentforce agents?
Salesforce admin skills cover most day-to-day tuning. Agentforce Builder allows conversational edits, but topic design, action configuration, and data grounding benefit from Salesforce architecture experience. - Can Agentforce 360 support multiple languages?
Yes. Salesforce runs its own support agents across several languages covering the majority of global case volume, and multilingual support is configurable for customer-facing deployments. - What happens when an Agentforce agent cannot resolve a request?
It hands off to a human, provided handoff rules are configured correctly. Poorly configured handoffs create dead ends, which is a common issue caught during live testing rather than development. - Does Agentforce 360 work with a non-Salesforce data warehouse?
Data 360 supports zero-copy connections to external data sources, so records can be referenced without full migration. Integration scope should be assessed before committing to a rollout timeline. - Is Agentforce 360 secure enough for regulated industries?
It includes governance controls, access management, and the MCP Registry for connection permissions. Regulated deployments still require deliberate compliance design rather than relying on default configuration. - Can we pilot Agentforce 360 before committing to a full rollout?
Yes. Pay-per-conversation pricing suits a narrow pilot on one use case. Validating a single agent before expanding reduces risk and produces usable data for the wider licensing decision. - Should we migrate from Einstein Bots to Agentforce now?
Einstein Bots and Agentforce share no authoring objects, so it is a full rebuild. With Legacy Chat already retired, planning the move deliberately is better than waiting for a forced deadline.