Salesforce Summer '26 New Features | Salesforce Dictionary

Salesforce Summer '26 Goes Official: 17 Features, Multi-Agent Orchestration, and a Quieter Chatter

Salesforce published its official Summer '26 product release announcement on May 11, 2026, formalizing the seasonal feature drop that has been sitting in sandboxes since the preview cutover on May 8. The announcement headlines 17 major capabilities, but the through-line is unmistakable: Summer '26 is the release where Agentforce stops being a bolt-on and starts behaving like the operating layer for the entire Customer 360.

For admins, developers, architects, and consultants, this release introduces a meaningful shift in defaults, the long-awaited generally available landing of agents inside Flow Builder, and a tighter security posture for orgs created on the new version. It also retires five long-tenured products. Production waves begin May 15 and complete on June 12-13, so the runway from announcement to GA is short.

Multi-Agent Orchestration: One Customer, Many Agents, Shared Context

The headline capability is Multi-Agent Orchestration. Rather than handing a customer off between disconnected bots and human queues, multiple specialized [Agentforce agents](/terms/agentforce-agents) now collaborate on a single end-to-end workflow while the customer sees a single point of contact. Context, intent, and history persist across channels and across the agents themselves.

In practice, a billing agent can hand the same conversation to a service agent and then to a retention agent without the customer re-explaining their problem and without the human supervisor losing the audit trail. Salesforce is positioning this as the architectural answer to the most common 2025 Agentforce complaint: that single-purpose agents stranded customers at the boundaries of their own scope.

For architects, the orchestration layer matters more than any individual agent. It is the piece that determines whether agentic workflows can be governed, monitored, and rolled back at the conversation level, not just at the action level.

Agentforce Self-Service: Help Agents in "10 Clicks or Less"

Agentforce Self-Service is the productized, faster-to-deploy successor to last year's bespoke service agent builds. Salesforce claims a Help Agent can be set up in 10 clicks or less and deployed across a public website, the new Portal experience, or WhatsApp, with a dynamic conversational UI that adapts to the channel.

This is the feature most likely to land on admin backlogs this summer. The setup pattern mirrors Service Cloud's earliest Web-to-Case wizards, but the runtime is fully agentic. Expect partners to start retiring legacy chatbot implementations as soon as the production waves complete in June.

Tableau MCP: Agents That Can Actually Query the Warehouse

Tableau MCP exposes Tableau's analytics engine to Agentforce agents over the Model Context Protocol, protected by the Agentforce Trust Layer. Agents can now ask Tableau questions natively, return governed answers, and cite the underlying view or dataset.

The framing in Salesforce's announcement is that this turns AI from a generalist into a "trusted data expert." The practical implication is that Tableau is now an agent-callable tool, not just a destination for humans. For data teams, this changes the calculus on row-level security and certified datasets — both become guardrails not just for dashboard consumers but for any agent that wants to reason over numbers.

Momentum, Collections, and the Customer Engagement Agent

Three revenue-side features round out the Agentforce expansion:

• Momentum captures calls, emails, and meetings and writes structured data back to Salesforce in real time. The goal is to eliminate the "what did the rep actually do this week" gap that has historically blocked agentic selling. Reps stop being the system of entry; the system of entry becomes the conversation itself.
• Collections with Agentforce scores invoices by payment likelihood using predictive AI and recommends risk-based dunning plans. For finance teams running on Revenue Cloud, this is the first time the collections motion gets a native agentic loop rather than a third-party connector.
• Customer Engagement Agent qualifies leads 24/7, holds natural conversations over website and email, and only hands off to sales when the lead is warm. It is essentially an SDR replacement for the top of funnel, and it is the feature most likely to be benchmarked against the standalone agent vendors that emerged in 2024-2025.

IT Service Domain Pack: 50+ Agents in Slack and Teams

The IT Service Domain Pack ships more than 50 specialized AI agents out of the box for Slack, Microsoft Teams, and the IT Service Desk. They are designed to resolve employee requests — password resets, license provisioning, common Tier 1 tickets — proactively, before a ticket is even filed.

This is Salesforce's clearest move yet into the internal-employee-experience space that ServiceNow has dominated. For Salesforce-on-Slack shops, the deployment story is meaningfully simpler than the equivalent ServiceNow virtual agent rollout. Per Automation Champion's Summer '26 summary, the domain pack ships with pre-built knowledge ingestion patterns for common ITSM data sources.

Storefront Next, Briefings, and Security Mesh

Three additional capabilities round out the Agentforce-adjacent surface:

• Storefront Next is an AI-first commerce storefront that promises enterprise-grade capability with rapid deployment. It is targeted at the mid-market commerce buyer who has historically chosen Shopify Plus over B2C Commerce on complexity grounds.
• Briefings delivers daily audio summaries for field teams — sales, service, and field service — based on each user's pipeline and accounts. Think of it as a morning podcast generated from your Data Cloud profile.
• Security Mesh transforms raw security alerts into actionable intelligence, prioritizing what a security operator should actually do next rather than dumping a SIEM feed in their lap.

Platform and Admin: The Changes That Will Actually Hit Your Org

Beneath the Agentforce headlines, Summer '26 contains the platform changes that admins and developers will live with for years.

Agents in Flow Builder Goes GA

The most consequential developer-facing change is that Agents in Flow Builder is now generally available. Admins can create Agentforce agents inline within Flow Builder, give them custom instructions and actions, and invoke them from any flow element. This collapses the divide between deterministic automation and agentic automation. Per Fíonta's Summer '26 overview, this lands alongside expanded testing scaffolding so agents invoked from flows can be unit-tested the same way Apex actions are.

Flow Orchestration Becomes Standard

Flow Orchestration loses its usage-based licensing limitations and becomes a standard part of the platform. Any org that was previously hesitant to adopt it because of metering can now plan multi-stakeholder workflows without procurement friction.

Chatter Disabled by Default in New Orgs

Chatter is disabled by default in any org created on Summer '26 or later. Existing orgs are untouched. This is a quiet but symbolic milestone: the feed-first paradigm that defined Salesforce's social era is no longer the default surface for new tenants. Slack is.

Decision Elements Get Real Date Operators

Decision elements in Flow now support Is Today and Is Anniversary of Today operators natively. Every admin who has ever built a TODAY() formula field just to drive a Decision branch can delete it. The Salesforce Admins release countdown flags this as one of the most-requested operator additions in years.

Field Access Review and Malware Scanning

The new Field Access Review tool gives admins a single unified view of field-level security across all profiles and permission sets. For consultants running compliance audits, this replaces a category of partner tooling that has existed for a decade.

Malware scanning in Files is now generally available, scanning uploads against known signatures before they land in storage. For regulated industries, this removes a frequently-required third-party add-on.

Database Operations Default to User Mode

For developers, the most important change is that database operations now default to user mode for any code compiled against API version 67.0 or higher. Sharing rules, field-level security, and object permissions are enforced automatically unless the developer explicitly opts into system mode. Existing code stays on its existing API version and is unaffected, but every new class written this summer will inherit the safer default. This is the culmination of a multi-year push that began with WITH USER_MODE SOQL.

Retirements: Five Products Sunset

Summer '26 formalizes the end-of-life for five products. Architects with any of these in their estate should be planning migrations now if they have not already:

• Salesforce Functions
• Legacy Chat
• Standard Omni-Channel
• Salesforce for Outlook (full retirement December 2027)
• Unified Knowledge

The Salesforce for Outlook timeline is the longest, but customers still on it should treat the announcement as the final call to migrate to the Outlook integration and Einstein Activity Capture.

Rollout Timeline

Per the official announcement and Salesforce Ben's release date preview, the production rollout schedule is:

• May 8, 2026 — Sandbox preview live (already complete)
• May 15, 2026 — First production wave
• June 5, 2026 — Second production wave
• June 12-13, 2026 — Final production wave

Admins should check the Trust status page for their instance to confirm their specific weekend. Release notes are final, and the preview window is now closed for feature changes.

What to Do This Week

For practitioners, the realistic Summer '26 prep checklist is short and load-bearing:

1. Audit API versions on triggers, classes, and managed packages. Any new code written at API 67.0+ inherits user-mode defaults — make sure that is what you want.
2. Identify Functions, Legacy Chat, Standard Omni-Channel, and Unified Knowledge usage and put migration on a roadmap.
3. Pick one Help Agent use case to pilot Agentforce Self-Service before the June production waves complete.
4. Inventory Chatter dependencies before spinning up any new orgs — the default is now off.
5. Test agents inside Flow Builder in your preview sandbox while it is still cheap to break things.

Summer '26 is not a release where admins can defer reading the notes. The defaults have shifted, the agent surface has expanded into the platform's core automation tool, and five products are now on the clock.