Beyond CRM: How Salesforce Engineered an Enterprise Agent Platform for Any Workload

By Muralidhar Krishnaprasad.

Enterprises move quickly to adopt agent-based systems, yet many still assume they need to assemble bespoke stacks on hyperscalers to support serious, non-CRM workloads. Inside Salesforce Engineering, the challenge looked different. Our goal: design Agentforce, Data 360, and the broader platform as the enterprise-standard agent foundation. This foundation supports mission-critical systems, rich data context, and long-lived agent lifecycles without being tied to any single product surface.

Join us as we explore how Salesforce Engineering solved that problem at the platform level. We will examine how established perspectives shaped architectural choices, how the team integrated trust and governance from the start, and how we prioritized data, metadata, and transparency to build an agent platform that scales across enterprises and ecosystems.

Extending Salesforce Beyond CRM to Power Enterprise Agent Workloads

Salesforce not only powers sales and service workflows for enterprises around the world, but it’s foundation also now reaches far beyond traditional CRM tasks. Agentforce and Data 360 support enterprise-grade agent systems across different industries and mission-critical environments.

The platform allows you to design agents that manage policy engines, custom backends, and specific industry logic within one architecture. Instead of treating agents as simple CRM additions, Salesforce provides the tools and governance needed to work across various systems. This ensures your workloads operate reliably at an enterprise scale.

Internally, our engineering team built the platform with a different intent. Design choices ensure Agentforce remains open, extensible, and customizable. Primitives like AgentScript and AgentGraph introduce deterministic structure into non-deterministic systems.

These primitives do not rely on CRM objects or workflows. Instead, they provide a generic mechanism for orchestrating tools, actions, and reasoning flows across enterprise systems. Data 360 complements this approach acting as the system of context, harmonizing and unifying disparate data from both inside and outside of CRM, which enabnles agents to reason over structured data, unstructured data, and metadata.

Engineering Enterprise Trust, Security, and Governance for Agents

Enterprise agents operate close to sensitive data, business processes, and user identity. This proximity makes trust a non-negotiable requirement. Because even small failures in isolation or access control cause outsized consequences, the architecture treats trust as more than an application-level concern.

Agentforce builds on foundational Salesforce platform capabilities like identity, credential context, and policy enforcement. It also adds specific protections for agentic behavior. A dedicated trust layer addresses threats such as prompt injection and impersonation. This layer ensures that critical variables come from trusted actions and governed data inputs rather than raw user prompts. Furthermore, the system treats agent identity as a first-class concept to enable secure interactions within Salesforce and across external systems.

Data governance remains a priority throughout the Agentforce and Data 360 integration pipeline. The system enforces rigorous guardrails and validates data before it undergoes chunking, indexing, or exposure for reasoning. These steps ensure that only policy-compliant information gets RAG’d into an agent’s context. Together, these controls allow agents to operate across systems and vendors while they preserve enterprise expectations around security, auditability, and data protection.

Context beyond Data — Metadata, Personalization, Memory and insights for Reliable Agent Reasoning

Reliable agent reasoning requires more than data and tools as context. Data and tools need accompanying metadata depth and semantic grounding to provide the full context over data as enterprise sources evolve. Simple metadata decoration fails in complex environments, so the core platform and Data 360 utilizes deeper metadata enrichment and derives relationships, extracts implicit structures, and uses business terms and glossaries to create rich semantic representations. Agentforce agents get to reason with deep metadata context that reflects actual meaning instead of relying on static declarations or human descriptions alone.

Further, Data 360 not only stores agentic conversation history and other application engagement signals but also curates them into short-term, long-term, and episodic conversation memory context and derives further affinities and insights to be maintained as users personalization profile. Preferences, historical interactions, and behavioral signals unify into an intelligent context layer. This enables agents to critically enhance context with key conversational memory and enriched user profiles, enabling agents to reason and process with deep user-specific context and respond in a personalized way. When enriched metadata, personalization and memory context meets core data and tools context, it creates a powerful foundation for reliable and trust-worthy enterprise-grade reasoning.

Keeping the Agent Platform Open Across Models, Tools, and Execution Surfaces

Enterprise customers demand flexibility. They require the freedom to choose models, integrate existing tools, and deploy agents across different surfaces. Locking into a single model provider or workflow remains unviable for modern business.

Agentforce supports multiple reasoning and prompt-build models, including those users provide. It leverages open standards like MCP to enable structured sharing of data and context and consistent tool invocation among AI agents and external systems. It also uses open standards like A2A to support orchestration of agents running both within and outside the Agentforce ecosystem. With MCP, users can expose tools through MCP servers that they host internally, via MuleSoft Agent Registry as part of MuleSoft Agent Fabric, or elsewhere — making them immediately available to agents. This approach integrates existing systems without duplicating tooling or rewriting logic.

Agents operate across various surfaces. Users can access Agentforce agents from Salesforce applications or external interfaces to meet users where they work. This flexibility supports incremental adoption so teams start with focused use cases and expand as confidence grows.

All this sits on Data 360’s open approach to common data foundation via connectors and also zero-copy operations with major ecosystem vendors along with open format file based data sharing.

Avoiding Fragmentation in Multi-Vendor Agent Systems

Architectural fragmentation creates concerns as teams adopt agents across various vendors. Separate stacks for reasoning, orchestration, and governance increase coordination overhead. MuleSoft Agent Fabric addresses this complexity by providing a unified layer for agent discovery, cross-platform orchestration, identity propagation, governance and observability.

MuleSoft Agent Fabric allows you to register and orchestrate agents regardless of the vendor. This ensures heterogeneous agent ecosystems operate without duplicating infrastructure while maintaining strict isolation.

Policy-controlled context sharing remains a central feature. Users define exactly what data moves between agents when they interact across domains. These policies apply at the data and interaction layers to prevent unintended leakage and enable controlled collaboration across systems.

Agent Monitoring and Observability — Operating a Fleet of Agents in Production

Enterprise agent programs don’t fail in the build phase — they fail after the first successful deployment. Once agents start handling real customer and employee work, the system can turn into a “black box”: users see outcomes, but not the reasoning path, tool calls, or configuration gaps that caused them. At that point, monitoring is no longer a nice-to-have SRE add-on; it becomes a core platform capability for trust, reliability, and iteration speed.

Agentforce approaches this problem by treating observability as a single mission control for both IT and business teams — not just dashboards, but a feedback system that connects production behavior back to configuration changes. Agentforce observability is positioned explicitly around this loop: monitor, analyze, and optimize performance in near real time, combining deep inspection with adoption and consumption visibility so teams can tie agent behavior to outcomes and cost.

Looking Ahead

Agentforce and Data 360 engineering decisions reflect a core platform philosophy. We build foundational capabilities first so higher-level agent behaviors emerge safely. By prioritizing trust, context, and interoperability, the platform supports both single-agent use cases and complex multi-agent systems and also extending manageability of multi-vendor agents with MuleSoft Agent Fabric.

Responsible agent adoption requires solving platform problems rather than focusing solely on certain generative AI aspects like model selection or prompt tuning and/or just narrowly focusing on few application use cases. Addressing these foundational issues upfront allows agents to operate reliably and securely at scale and across a wide variety of workloads — CRM or not.