AIforce: Salesforce in Claude and Slack explained

AIforce is the layer Salesforce launched at Dreamforce on 15 September 2026 to make its data, workflows and permissions usable from Claude, Slack and the Lightning interface. For a manufacturing IT lead the honest status is this: Salesforce in Claude is a beta for sales teams, Agentforce Coworker needs Data 360, and the rename to SIForce is so far a CEO post on X. I would not plan a rollout now. I would clean up permissions, decide which interface each user group works in and run one small pilot in sales.

What is AIforce?

Salesforce calls AIforce “a live interface layer that brings the full power of Salesforce to wherever people and agents work” (announcement, 15 September 20261). In plain terms: users ask questions, update records and start workflows from another tool without opening Salesforce. In Salesforce’s architecture picture, AIforce sits above Data 360, Customer 360 and Agentforce. It has four parts:

• Claudeforce, or Salesforce in Claude. A prebuilt MCP server inside Claude with 37 sales skills, plus a Salesforce Development plug-in for Claude Code with more than 40 skills. MCP (Model Context Protocol) is the open standard through which an AI tool calls functions in another system; I explain it in MCP for IT leads.
• Slackforce. Slackforce Surfaces for live interfaces in Slack, Slackbot as a personal assistant over Slack and Salesforce data, Slack CRM and Slack Code.
• Agentforce Coworker. An AI teammate in Lightning that reasons over accounts, activity and history and calls the Agentforce agents you have already deployed.
• Headless Toolkit. MCPs, APIs, plug-ins and skills that expose the platform to your own AI tools.

Two directions are easy to mix up. In the Claudeforce release of 27 August 20262, Salesforce names Claude as a reasoning model for the Atlas Reasoning Engine and the default model for Agentforce Coworker and Slackbot, and says that through Amazon Bedrock Claude is available within the Salesforce Trust Boundary. That is Claude inside Salesforce. Salesforce in Claude is the reverse: your CRM data goes to the Claude app your employees use. For data protection these are two different cases.

Is AIforce now called SIForce?

Officially, not yet. On 9 October 2026 Marc Benioff posted on X: “The era of Super Intelligence is here. AIForce is officially SIForce.” I can only confirm this through secondary sources. Salesforce Ben reported on 12 October3 that there did not appear to be any official announcement from Salesforce and that it had asked Salesforce for comment. Up to today I found no press release or help article from Salesforce that uses SIForce.

The background is a US executive order of 29 September 2026, “Inaugurating The Era of Super Intelligence”4. It tells executive departments and agencies to say “Super Intelligence” instead of “Artificial Intelligence” in their own documents. Private companies are not mentioned, so nothing obliged Salesforce to rename anything. Salesforce Ben counts SIForce as the third name for this layer in just over six months, after Headless 360 at TDX in April and AIforce at Dreamforce.

For your own documents I would write “AIforce” and add “(announced by the CEO as SIForce)” once. Order forms and contracts use whatever name Salesforce prints there, and that is the name that counts.

1. 29 Apr 2026Hosted MCP servers generally available
2. 27 Aug 2026Claudeforce: Claude becomes default model for Coworker and Slackbot
3. 15 Sep 2026AIforce launched at Dreamforce
4. 29 Sep 2026US executive order on "Super Intelligence" for agencies
5. 9 Oct 2026Marc Benioff on X: AIforce is now SIForce
6. 12 Oct 2026Salesforce Ben finds no official announcement

Status October 2026: most of it is only announced

The announcements are bigger than what you can switch on. Status on 27 October 2026:

• Salesforce in Claude is a beta. According to Anthropic’s setup guide5, it runs on paid Claude plans for organisations that Salesforce approves through its beta sign-up, needs the latest Sales Cloud enterprise edition and works in chat and Claude Cowork on web and desktop. Claude acts as the user’s own Salesforce account and by default asks for approval before each change is written.
• Agentforce Coworker is “instantly available” according to the announcement. Salesforce’s own Coworker blog6 says both “Generally Available” and “in beta”, and lists Microsoft Teams, ChatGPT, Claude and a desktop app as “coming later this year”. The setup documentation7 requires Enterprise, Unlimited or Agentforce 1 Edition plus Data Cloud or Data 360.
• Slackforce is listed as GA in October in the Dreamforce 2026 roundup8; I found no separate release note confirming it. Slackbot actions already have fixed prices in Flex Credits, per Slack workspace, according to the rate card of 31 August 20269.
• Hosted MCP servers, through which external AI tools such as Claude reach an org, have been generally available since 29 April 202610 for Enterprise Edition and above. The current documentation adds that they are intended for customers with Flex Credits and that usage may be billed. Who may read what through them is the topic of hosted MCP servers and data access.

37

sales skills in Salesforce in Claude (beta)

40 Flex Credits

per standard action in Slackbot

200 Flex Credits

per advanced action in Slackbot

On cost, the announcement says: “Pricing and packaging are subject to change.” The rate card lists Headless Platform Interactions, the meter for agentic API and MCP calls, as “TBA”. Why that becomes a budget line is explained in MCP calls as a budget risk.

For manufacturers, AIforce helps sales more than service today

Right now AIforce helps sales more than service. According to Anthropic11, the 37 skills cover account research, call preparation, pipeline review and CRM updates. That fits key account managers and dealer managers who prepare visits and maintain opportunities. Salesforce’s announcement lists skills for service, marketing, commerce and industries only for “the near future”. Heads of after-sales and field service have nothing to test yet.

The second point is the ERP. Salesforce in Claude reads Salesforce. If order status, delivery dates and stock live only in SAP or proALPHA, a sales rep asking “which orders of this dealer are late?” gets an answer built on incomplete data, delivered with full confidence. Which ERP data belongs in Salesforce, or behind an API the agent can call, has to be settled before anyone opens a chat window.

The third point is the collaboration tool. Many machine builders work in Microsoft Teams. Slackforce brings nothing there, and for Coworker in Teams Salesforce only says “later this year”. I would not buy Slack to get an AI interface.

The fourth point is permissions. “Every transaction runs as the authenticated user”, Salesforce writes about hosted MCP. That is correct, and it is also the risk. If your sales reps can see all cases, warranty claims and dealer price agreements because sharing was set too broadly years ago, a chat shows it in seconds instead of after ten clicks.

Worked example: a machine builder with Teams and SAP

Assume a machine builder with 80 Sales Cloud users in sales and dealer management, Service Cloud for after-sales, SAP as ERP and Microsoft Teams for collaboration. All numbers and circumstances are assumptions. A few sales reps already paste account data into private AI tools.

The IT lead sorts the four AIforce parts:

• Salesforce in Claude: the pilot candidate for ten key account managers, provided the edition qualifies for the beta and the company buys a paid Claude plan. Before the pilot, the sharing model for cases and price agreements is reviewed, and approval before each write stays on.
• Agentforce Coworker: waits. The company has no Data 360 licence, and Teams support is announced for later.
• Slackforce: not relevant, the company works in Teams.
• Headless Toolkit: relevant for IT and the implementation partner, because hosted MCP servers and the Claude Code plug-in are the developer path. What partners may do with it belongs in the contract.

The outcome is one small pilot in sales and a week of permission clean-up. In my judgement that is the right size for a beta whose prices Salesforce has not fixed.

Find the shadow use, then check permissions and contracts

1. Find the shadow use. Ask which teams already copy Salesforce data into Claude, ChatGPT or Copilot. A governed connector with the user’s own permissions beats copy and paste.
2. Assign one interface per user group. For example Lightning for service agents, Claude for key account managers, Teams for everyone else. Five parallel AI surfaces mean five support topics.
3. Review sharing and field-level security for cases, warranty claims, price agreements and dealer accounts before any chat tool reads them.
4. Read your Claude contract. Salesforce promises that business data “is not retained by the model provider”. Check data processing, training settings and hosting region in your own agreement with Anthropic, because that is where the data goes.
5. Budget a pilot. Prices are subject to change and the MCP rate is open. Whether Data 360 is worth buying for Coworker, or Claude seats for the sales team, is a question for make-or-buy and licence planning.
6. Keep the name AIforce in your documentation until Salesforce confirms SIForce in writing.

Whether to build your own Agentforce agents is a separate decision, covered in Agentforce for manufacturers: start now or wait?. For AIforce itself the order of the list above applies: permissions, data and contracts first, then the interface.

Sources11

1. 1announcement, 15 September 2026 (opens in a new tab)salesforce.com
2. 2Claudeforce release of 27 August 2026 (opens in a new tab)salesforce.com
3. 3Salesforce Ben reported on 12 October (opens in a new tab)salesforceben.com
4. 4“Inaugurating The Era of Super Intelligence” (opens in a new tab)whitehouse.gov
5. 5Anthropic’s setup guide (opens in a new tab)support.claude.com
6. 6Coworker blog (opens in a new tab)salesforce.com
7. 7setup documentation (opens in a new tab)developer.salesforce.com
8. 8Dreamforce 2026 roundup (opens in a new tab)salesforce.com
9. 9rate card of 31 August 2026 (opens in a new tab)salesforce.com
10. 10generally available since 29 April 2026 (opens in a new tab)developer.salesforce.com
11. 11Anthropic (opens in a new tab)claude.com