Claudeforce: what Salesforce and Anthropic actually shipped

You have seen the headline. Salesforce put its CRM inside Claude, and depending on which write-up you read, you will never need the Salesforce app again.

Here is what is actually true five days in. One product is in pilot with selected customers. Its price is not published. The Salesforce edition it needs is not published. The Claude plan it needs is not published. Thirty-seven skills were announced and three of them have names. And nothing in the announcement puts a single new company or contact into your CRM.

That last point is the one worth your time, so it gets its own section below, and if it is the only thing you came for then skip to it: the section is called what it reasons over, and what it does not fetch. Everything between here and there is a reference on what shipped, for people who have to make decisions about it.

The rest of this describes the state of things on 1 September 2026, six days after the announcement and before open beta. Several of the facts below are expected to change in September.

First, the naming, because the coverage has already muddled it.

Claudeforce is the partnership. Salesforce in Claude is the product

Salesforce's press release of 26 August 2026 uses Claudeforce for the expanded partnership between the two companies. The thing you can install is called Salesforce in Claude, described in that release as "a Plugin that understands the sellers' entire revenue cycle and acts on it, giving them an AI CRO, with 37 prebuilt sales skills."

Most of the coverage treats Claudeforce as the product name. Salesforce's own Claudeforce page is loose about it too. If you are searching for documentation, searching for the plugin name will get you further.

On the spelling: it is Claudeforce, with a lowercase f. Both Salesforce's press release and its product page write it that way. The question has already produced a 39-comment thread in r/salesforce comparing it to the Salesforce versus SalesForce confusion that has run for decades, so it is worth two seconds of certainty.

The ten names, in one place

Ten product names are in play across this announcement, several of them new, and the coverage uses them interchangeably. This is the map.

What ships now, and what is only announced

The release is precise about status, and the precision gets lost in summary. Salesforce in Claude "is available to select pilot customers now and expects to launch in open beta in September 2026."

Salesforce attaches one line to all of that which is worth reading literally: "Customers should base purchasing decisions on products and services currently available."

The 37 skills, and the three with names

Three are named in the release: meeting prep, deal health review, and pipeline review. The product page groups the remainder into unnamed categories covering daily briefings and pipeline review, deal strategy and stakeholder mapping, account health and expansion, and call prep and follow-up, under the line "Put these 37 sales skills to work, from prospecting to close."

The full list is not published anywhere first-party.

That gap matters more than it looks, and the sharpest version of why came from practitioners rather than from press. The top thread on the announcement in r/salesforce, at 135 comments, makes the point that the skills people build for themselves are tied to how their own org has been configured, and that generic skills will only move the needle if they adapt from an org's metadata. Salesforce's release gestures at this: onboarding "reads a seller's enterprise context, Salesforce, Slack, and any connector in Claude, to stand up a tailored dashboard." Whether that reaches down to custom objects and a decade of accumulated field-level oddity is exactly what the pilot will answer, and it is unanswerable from the outside today.

How it connects

Setup is administrator-side and one-time. In Salesforce's words, "an admin connects Salesforce in Claude a single time, with authentication and permissions managed centrally, and every seller on the team gets access from day one." Actions are routed back through Salesforce, so "business rules are always enforced when an action is taken."

For anyone who has watched a well-meaning integration write garbage into a CRM, that routing is the reassuring part of the announcement. Your validation rules and sharing model still apply.

Headless 360 is the architecture underneath, and it is older than this

Salesforce in Claude sits on Headless 360, which Salesforce describes as "an architectural transformation that exposes every capability Salesforce has built over 25 years directly as an API, a Model Context Protocol (MCP) tool, or a CLI command." That page lists 60+ MCP tools and 30+ prebuilt skills, already names Claude among the models you can connect, and carries a Connect Claude to Salesforce workshop. Its developer blog is dated May 2026.

So the plumbing predates the Claudeforce branding by several months. If you want to understand what the plugin can reach, Headless 360's documentation is the more useful read.

One name in the release is worth knowing is not a thing yet. AIforce, described as "Salesforce's trusted enterprise harness that brings all your business data and workflows to any agent through MCP servers, APIs, and CLI tools," has no product page, no documentation, and no entry in Salesforce's product navigation, Trailhead or developer docs. Marc Benioff's own quote uses it almost interchangeably with Headless 360, which has all of those. Read it as a label wrapping Headless 360 and Data 360 rather than as something you can switch on.

Data 360 unifies what you already own

Data 360, formerly Data Cloud, is described as "the real-time data engine that powers the entire Salesforce platform." Its job is to take data scattered across your own systems, lakes, warehouses, CRM and apps, and resolve it into one view without moving it. The page advertises 200+ connectors.

Every one of those connectors points at something you already have. Data 360's own product page makes no claim to sell or supply third-party company or contact records, and third-party enrichment exists around Salesforce as separate partner relationships.

One qualification, because Salesforce's own documentation supplies it. A separate Sales Cloud feature called Prospecting Center is described in Salesforce's help docs as "powered by Data 360" and as using external as well as internal signals to score accounts. So Data 360 has been wired to a capability that reaches outside your own systems. That feature is not part of Salesforce in Claude, and it is being retired, which is the subject of a later section.

Hold onto that. It comes back below.

Where Claude actually sits inside Agentforce

The release says Claude "is available in Agentforce, serving as a reasoning model for the Atlas Reasoning Engine, powering Agentforce Vibes and Agentforce Coworker by default, and available in Agent Builder."

Check that against the product pages and something odd turns up. The Atlas Reasoning Engine page calls Atlas "the brain of Agentforce" and does not name Claude, Anthropic, or any model at all. The Agentforce Vibes page refers only to "a context-aware model of your choice." The Agent Builder page does not mention Claude or Anthropic anywhere. Agentforce Coworker's page lists Claude as one of the surfaces Coworker appears on, alongside Salesforce, Slack, Microsoft Teams, ChatGPT and mobile, rather than as the model running it.

The confirmation lives in the developer documentation instead. Salesforce's supported models page lists Claude variants as selectable and states that the AWS-hosted default option "uses Anthropic Claude Sonnet 4 on Amazon Bedrock."

None of this contradicts the release. Marketing pages lag, and Claude's role is documented where engineers look for it. It does mean that if you are checking what your own org will actually run, the developer docs are the authority and the product pages are not yet updated.

The Slack layer, and one claim to hold at arm's length

Slack is the part of this that is furthest along, and it is also where the release makes its boldest claim.

Slack's own help centre states that "starting August 3, 2026, Claude Tag will replace the current Claude app in Slack." Anthropic's own support documentation says Claude Tag "is available on Team and Enterprise plans in beta." Read that carefully: Team and Enterprise there are Claude's organisation plans, not Slack's pricing tiers. Any Slack workspace can use it. Only a Primary Owner or Owner of the Claude organisation can configure it, channel work bills to the organisation, and direct messages bill to the individual account.

Slack Code is live rather than announced. Slack's own post, published around 20 August 2026, describes dedicated code channels where teams and coding agents plan, write and review code together, with live diffs, previews, approval workflows and automatic archival, and says it "is live today for teams using Claude (Anthropic), Devin (Cognition), GitHub (Copilot), and Vercel integrations, with OpenAI (ChatGPT) available soon." The Slack plan required is not stated.

The claim worth reading carefully is the default-model one, because its scope is narrower than the summaries of it. Salesforce's release says Claude is the default model for Slack AI, Slackbot, Salesforce in Claude, Headless 360, Agentforce Coworker and Claude Code across Salesforce's engineering organization. That is a statement about how Salesforce runs itself, not about what arrives in your workspace.

The customer-facing version in the same release is separate and narrower still: Claude is "the AI model powering Slackbot for Salesforce customers and employees."

Slack's own Dreamforce post on its native AI describes Claude as one of several partner integrations, with no default-model language anywhere on it. So if you are deciding what your team will be using next quarter, the answer for Slackbot is Claude, and for the rest of Slack's AI surface the public record does not yet say.

One number from that part of the release is worth one sentence and no more. Salesforce reports Slackbot "driving 8.1M hours of annualized productivity gains, up over 2x quarter-over-quarter" among its own employees, with no headcount base, no definition of a productivity hour and no method published, which makes it an internal self-report rather than something to plan against.

Where your data goes

Salesforce's supported models documentation is specific: "Anthropic and Amazon models are operated on Amazon Bedrock infrastructure entirely within the Salesforce Trust Boundary. In contrast, other models are operated by Salesforce partners, either inside a shared trust zone or through the LLM provider directly."

If you go looking for a fuller explanation of the Trust Boundary, be careful which page you land on. Salesforce's general Einstein Trust Layer article describes the concept and states a zero-retention policy with external providers, but it still uses OpenAI and Azure OpenAI as its examples and does not mention Anthropic, Claude or Bedrock at all. The supported-models page is the one that ties the Trust Boundary to Anthropic. The general trust page has not caught up.

You can still run a different model

One take on this announcement has travelled further than the others: that Salesforce has closed itself off to competing models and ended vendor-neutral enterprise AI.

Salesforce's own documentation says otherwise. Agentforce's bring-your-own-LLM option "currently supports Amazon Bedrock, Azure OpenAI, OpenAI, and Vertex AI from Google." The same page notes that using BYOLLM consumes 30% fewer Einstein Requests than other models.

Claude being the default is a real change and defaults matter enormously in practice, because most orgs never change one. The switch still exists.

What each announcement since 2024 added

Claudeforce is the fourth Salesforce and Anthropic announcement in two years, and the four fit together in a way that is hard to see from any one of them.

Two years of work, running in both directions, with the pieces landing in a sensible order. The direction of travel on 26 August is the new part: everything before it brought Salesforce data toward Claude, and this brings Salesforce actions into Claude.

What it reasons over, and what it does not fetch

Now the part that decides whether any of this is for you.

Dario Amodei's quote in the release is the clearest statement of the boundary, and it comes from Anthropic's own chief executive: companies can "point Claude at the customer information and business context that they've been building in Salesforce for decades, and use it to actually run and grow their businesses."

Point Claude at what you have built. Every capability in the announcement reads that way once you look for it. Sellers "reason over live revenue context, automate pipeline updates, and take governed action." Anthropic's own documentation for connecting Salesforce says connecting it "lets Claude read accounts, contacts, opportunities, and cases (and write, if you grant it)," and recommends read-only as the starting point. Data 360, as covered above, unifies your own systems, and the one Salesforce feature documented as pulling external signals through it is on its way out.

Nothing here finds you a company you had never heard of. Nothing here tells you which companies opened a role last week, or verifies that the contact you are about to email still works there. The plugin is very good news if your CRM is full and you cannot get answers out of it. It does nothing at all if your CRM is empty.

There is a corroborating detail, and it is a quiet one. Salesforce does have a feature that blends external signals with CRM data for prospecting, called Prospecting Center, which analyses "your CRM and external data". It has no mention of Claude or Claudeforce in its documentation, and it is being retired: scheduled for retirement in all Salesforce orgs as of April 2026, available to existing customers until April 2027.

The direction is toward reasoning over the record you hold, and away from acquiring records you do not.

What Salesforce has not published

Collected in one place, because it is most of what a buyer needs.

Anthropic, for its part, has published nothing about this announcement. Its newsroom for that week carries posts on alignment, security, hardware standards and personnel, and no Salesforce post. Every fact about how the product works comes from Salesforce. That is worth one raised eyebrow and no more than one.

If the records are not in there yet

Everything above assumes the reasoning problem is your problem: the data exists, and you cannot get a straight answer out of it. For a lot of teams that is exactly right, and Salesforce in Claude looks like a real improvement when it reaches general availability.

If you are earlier than that, the shape of your problem is different. You need to know which companies to approach and whether the person listed against one is still there, and no amount of reasoning over an empty object solves it. That is a data problem, and it is the one we work on. Our piece on what Claude can and cannot do for lead generation goes through the same boundary from the model's side. If the records you do hold are in your own network rather than in a CRM, the LinkedIn connections export is the file worth starting from, and it comes with an expectation gap worth knowing about first. And the accuracy claims data vendors publish about themselves is worth reading before you buy any of it.