The original Headless proposition<\/a> was built around separating CRM capabilities from the Salesforce interface, allowing data and functionality to be accessed across different environments. \u00a0<\/p>\nToday, it has expanded to address one of the pressing limitations that becomes more evident\u00a0as AI agents take on more customer-facing work. \u00a0<\/p>\n
For example, an agent may have access to Salesforce but still reaches the boundary of what has been explicitly connected or configured for it, causing it to stall\u00a0and hand the task back to an employee. \u00a0<\/p>\n
Furthermore, accessing CRM capabilities is only useful if agents can work with the customer context required to make appropriate decisions and actions. \u00a0<\/p>\n
With data work\u00a0often involving\u00a0sourcing fields, mapping schemas, building segments, and activating information across tools and teams, processes that can take create severe delays. \u00a0<\/p>\n
For customers, these unnecessary gaps in Headless 360 can result in slower resolutions, inconsistent experiences, and interactions that lack the context needed to feel relevant or trustworthy.\u00a0<\/p>\n
Inside Salesforce\u2019s Agent-Ready Headless Architecture\u00a0<\/p>\n
Most notably, Salesforce\u2019s Headless 360 MCP Server is now available in open beta, improving on the earlier model by allowing agents to discover the Salesforce capability they need at runtime.\u00a0<\/p>\n
Rather than requiring developers to predefine every API or feature, agents can\u00a0now discover, understand, and invoke Salesforce capabilities dynamically. \u00a0<\/p>\n
As a\u00a0metadata-aware\u00a0server, the MCP enables\u00a0agents\u00a0to\u00a0inherit existing object relationships, validation rules, and automations alongside the user\u2019s Salesforce own permissions and policies, allowing them to work within\u00a0already established business logics.\u00a0<\/p>\n
Secondly, Salesforce is extending the architecture across its wider\u00a0CX portfolio,\u00a0giving agents access to capabilities spanning customer engagement, sales and data integration. \u00a0<\/p>\n
In service, Headless capabilities can bring dispatching, Field Service scheduling, and support workflows into external applications\u00a0and other customer touchpoints.\u00a0<\/p>\n
For marketing, the\u00a0Marketing Engagement MCP allows marketers to manage automation, customer\u00a0journeys, and\u00a0data extensions through natural language inside Slack.\u00a0<\/p>\n
Data 360\u2019s\u00a0new MCP Server also\u00a0exposes roughly 200 APIs, enabling authorised agents to analyse, structure, and activate customer data without teams manually completing each step\u00a0across separate tools.\u00a0<\/p>\n
As a result,\u00a0this extends Data 360 into a platform where agents can also build and activate customer data. \u00a0<\/p>\n
Furthermore,\u00a0Prebuilt Data 360 Skills are designed to support common workflows with general availability targeted for August 2026.\u00a0<\/p>\n
Finally, the\u00a0expansion adds a broader conversational and development layer, with Slackbot\u2019s MCP Client\u00a0now connected to\u00a0Slackbot with more than 20 partner applications, including Docusign, Notion, and Zoom. \u00a0<\/p>\n
From here,\u00a0users can ask Slackbot to perform actions across applications while retaining existing permissions and data boundaries, enabling Agent Skills and Plugins\u00a0to\u00a0then package reusable\u00a0rules and resources\u00a0into governed, agent-readable instructions. \u00a0<\/p>\n
As of right now, more than 100 prebuilt Skills are available, giving organizations\u00a0the ability to\u00a0reuse verified capabilities across different workflows instead of relying on individual prompts.\u00a0<\/p>\n
Are Businesses Ready for Agents to Act?\u00a0<\/p>\n
For CX teams, the\u00a0expansion enables agents to execute capabilities wherever customer and employee work takes place. \u00a0<\/p>\n
For example, a service agent can now\u00a0take action across cases, scheduling, customer data, and other workflows, while external agents can access governed Salesforce capabilities without requiring\u00a0separate integrations. \u00a0<\/p>\n
In fact, early customers are\u00a0reportedly\u00a0seeing measurable gains, with Engine\u00a0cutting\u00a0its time to production by 90%, while VentureCrowd reduced its development cycles by 90%.\u00a0<\/p>\n
For CX, this could reduce handoffs and screen switching across customer-facing\u00a0operations, giving\u00a0customer data a more active role in the experience. \u00a0<\/p>\n
Data 360\u00a0now provides\u00a0the\u00a0context agents need to make decisions and execute actions based on relevant customer information\u00a0rather than retrieving\u00a0records. \u00a0<\/p>\n
CX leaders must now assess whether their organizations are ready for agents to execute work rather than assist employees, agent handling\u00a0will become\u00a0critical\u00a0as they become more capable. \u00a0<\/p>\n
Salesforce\u2019s approach makes those controls part of the architecture, enabling\u00a0agents to\u00a0inherit\u00a0the existing rules and capabilities within the organization.\u00a0<\/p>\n
In a previous conversation<\/a>,\u00a0Simon Harrison, Founder of Actionary,\u00a0told CX Today\u00a0that this shift is changing how people will interact with enterprise software.\u00a0<\/p>\n\u201cThis is the future of applications,\u201d he said.\u00a0<\/p>\n
\u201cIt is hands down the only way we will decide to use applications in the future.<\/p>\n","protected":false},"excerpt":{"rendered":"Salesforce\u00a0has today expanded Headless 360 with an MCP-based architecture that lets AI agents discover and act on existing…\n","protected":false},"author":2,"featured_media":144833,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[405,7537,644,7633,37839],"class_list":["post-144832","post","type-post","status-publish","format-standard","has-post-thumbnail","category-agentic-ai","tag-ai-agents","tag-artificial-intelligence-agents","tag-crm","tag-customer-journey-analytics-software","tag-headless-cms"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/144832","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=144832"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/144832\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/144833"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=144832"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=144832"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=144832"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}