Skip to main content
FlowDesk logoFlowDesk

Is Claudeforce in open beta? Not as of 2026-08-29

Claudeforce (Salesforce in Claude) is not in open beta as of August 29, 2026 — access is pilot-only, with an open beta planned for September 2026 but no exact date or standalone pricing announced. This dated status check shows what access reality looks like today, what Claudeforce actually covers for work productivity, and how to re-verify before the beta window opens.

VerifiedPricingNo standalone pricing announced; inference billed on consumption via AnthropicExportNo separate export format announcedPlatformsSalesforce CRM; Anthropic ClaudeLocal-firstNo

As of August 29, 2026, Claudeforce is not in open beta. Access is limited to select pilot customers, while an open beta is planned for September 2026. Salesforce and Anthropic have not announced an exact beta date or standalone pricing. The August 26 launch coverage confirms that the product exists; it does not prove that a sales team can access it publicly today.[1][2]

Enterprise cloud gateway with a pending-access lock and CRM data streams

What “available” means on August 29

The clearest dated account is the August 26 CIO report. It describes Claudeforce as being used internally and by pilot customers, while noting that there was no public open beta at launch.[1] A second report published August 27 says access is limited to select pilot customers and places the planned open beta in September, without giving a specific date or standalone price.[2]

That makes the current status fairly narrow: announced, in internal use, and being tested with selected customers are all supported descriptions. “Open to anyone who wants to try it” is not. The two reports are independent, dated third-party accounts, so they provide the strongest support in the available evidence. The vendor’s August 26 press release, Claudeforce product page, and waitlist page were not independently verified here at the level needed to replace that distinction.

Timeline from August 26 through August 29 ending before an unconfirmed September beta date

There is a Salesforce-hosted page titled “Join the waitlist to be first in line for Claudeforce.”[3] Its existence shows that Salesforce has provided a path for expressing interest. It does not establish that submitting a form grants immediate access, that every applicant qualifies, or that the page represents an open beta. The body text and eligibility fields were not verified, so those details should remain unresolved.

QuestionVerified position as of Aug. 29, 2026
Is Claudeforce publicly available?No public access is verified; the available reports describe pilot-only access.
Is it in open beta?No.
When is open beta scheduled?September 2026 is planned, but no exact date is announced.
Is standalone pricing published?No standalone pricing has been announced.
Can people express interest?A Salesforce waitlist page exists, but its process and eligibility are unverified.

The distinction matters operationally. A team preparing a pilot can monitor the vendor announcement, product page, and waitlist status. It should not treat a waitlist submission—or the word “launch”—as a production commitment. No edition, plan, or geographic eligibility is stated in the launch material available for this check. That absence is not evidence that access is free, global, or available to every Salesforce customer.

The productivity scope is sales work inside CRM context

The useful question is not whether Claudeforce is a general-purpose workplace assistant. The material supports a more specific description: it is aimed at CRM and sales workflows. Two independent recaps report 37 prebuilt sales skills.[5][6] The described work includes preparing for meetings, analyzing deal health, and reviewing pipelines against live CRM context.

CRM data flowing through MCP and a permissions gate to sales workflow tasks

That context is connected through the Model Context Protocol, or MCP, and actions are routed through Salesforce permissions. In practice, the proposed value is less about giving a worker another place to write notes and more about letting Claude work with authorized CRM records and sales processes. The available evidence does not support expanding the product into note-taking, migration, or personal knowledge management.

Service, Marketing, and Commerce capabilities are described as coming later, without firm dates. They should not be used to inflate what a team can evaluate in the current pilot window.

Permissions change the pilot decision

Because Claudeforce is expected to operate on live CRM context and route actions through Salesforce permissions, access is not only a question of whether a user can open Claude. The relevant question is what that user, connected account, and workflow are allowed to read or change.

A third-party explanation says inference is priced on a consumption basis contracted separately with Anthropic, without publishing dollar figures. It also recommends auditing permissions and starting with read-only use before piloting.[4] That is a sensible control boundary while the commercial model and beta conditions remain incomplete: test the quality of CRM-grounded answers before allowing the assistant to write back or trigger consequential actions.

One possible source of confusion is the word “beta” in Salesforce-related material. The beta wording identified in the available evidence refers to Salesforce Hosted MCP Servers infrastructure, not to Claudeforce’s customer availability.[4] Those are different layers of the system and should not be collapsed into one access claim.

What to re-check before September

This status is deliberately point-in-time. September may bring a change after this article’s last-checked date, but the planned month is not an operating date. Before asking a sales team to plan around Claudeforce, verify these items again:

  • Look for an exact open-beta date in the Salesforce announcement or Claudeforce product page.
  • Confirm whether the beta is genuinely open or still restricted by customer type, region, Salesforce edition, or invitation.
  • Check for standalone pricing, usage charges, and any separate Anthropic inference terms.
  • Review the current waitlist language rather than assuming that its presence equals approval or immediate access.
  • Define a read-only test using the CRM records and permissions the team is actually prepared to expose.

Teams that want to prepare workflows can use the existing Claudeforce sales workflow automation setup guide without treating its preparation steps as proof that the product is publicly accessible. Readers comparing the waiting period with Salesforce’s other automation direction can also review Claudeforce versus Agentforce, where the absence of published productivity and pricing data remains relevant.

The dated verdict is therefore simple: do not treat Claudeforce as publicly available on August 29, 2026. Treat it as a pilot-limited CRM and sales workflow product with a September open beta planned but not dated. Wait for an actual beta date and commercial terms before making an access or purchasing decision.

References

  1. Salesforce, Anthropic partner to deliver Claudeforce | CIO — CIO, August 26, 2026. Source
  2. Claudeforce: Salesforce in Claude, 37 Skills, Availability & How It Works — ProjectMonet, August 27, 2026. Source
  3. Join the waitlist to be first in line for Claudeforce — Salesforce. Source
  4. Claudeforce Explained: What Salesforce + Anthropic Actually Ship — Apex Hours. Source
  5. Salesforce-Anthropic Claudeforce Q2 Earnings 2026 — Cynoteck. Source
  6. Salesforce and Anthropic announce Claudeforce — LinkedIn, Edmund Ho. Source

Where Claudeforce shows up elsewhere

Comparisons

No comparison references Claudeforce yet.

Migration guides

No tested migration path involving Claudeforce yet.

Setup guide

No setup guide for Claudeforce yet.

Spot outdated pricing or a platform detail that has changed?