Your Salesforce project already has an architect, an admin and a project manager. The glossary would now like a seat at the table. It has brought its own spreadsheet.
If you have paused halfway through a slide to ask whether Claudeforce became AIforce, the question is understandable. Several names describe different layers, while others really have changed. Here is a friendly translation guide, checked on 30 October 2026. The distinctions matter when you scope a project or read a quote.
Claudeforce, AIforce and SIforce: give each name a job
Claudeforce did not simply become AIforce. Salesforce's own explanation separates the Anthropic partnership, called Claudeforce, from the underlying interface layer, called AIforce. Salesforce in Claude is the product experience that brings Salesforce work into Claude. Think of a project introduction: partnership, platform layer, product. Three name badges, three different jobs.
Then SIforce joined the conversation. In an October post announcing the new name, Marc Benioff said AIForce was officially SIForce. Meanwhile, the Salesforce announcement and Trailhead page checked for this article still use AIforce. An announced name and the wording in a particular help page can therefore differ. Keep both in your search notes; check the actual product and entitlement before treating the announcement as a change to your implementation.
This is where the glossary earns its chair. Add an alias column. It is cheaper than holding the same meeting twice.
A small map for the next meeting
| Name on the slide | How to read it | Useful next question |
|---|---|---|
| Claudeforce | Salesforce–Anthropic partnership | Which connected experience are we discussing? |
| AIforce / SIforce | Interface-layer documentation and the newer announced name | Which release and entitlement apply to this project? |
| Salesforce in Claude | The connected product experience | What can this user read or change? |
| Data Cloud / Data 360 | Data Cloud was rebranded Data 360 | Which data operations and pricing model are in scope? |
| AppExchange / AgentExchange | Familiar marketplace name and the unified marketplace | Which publisher, listing and package are we evaluating? |
| Sales Cloud / Agentforce Sales | Labels encountered across product and release pages | Which edition, feature and licence does the quote specify? |
There are genuine renames in that map. Salesforce documents Data Cloud becoming Data 360. Its April 2026 marketplace update brought AppExchange, AgentExchange and Slack Marketplace into a unified AgentExchange. The older name in a bookmark is a reason to check the destination, rather than assume the app vanished.
Another documented change is the Einstein Copilot for Salesforce agent-type rename to Agentforce. That specific release note describes a naming change without a functionality change. It does not mean every product carrying the Agentforce name is identical to the old assistant.
Sales terminology needs the same care. The current sales product page says Sales Cloud, while a release page uses Agentforce Sales. Keep the feature and edition beside the name. A slide heading is a poor place to hide a purchasing assumption.
The project still needs the same practical answers
For each capability, write down its current name, older search terms, official source, licence or SKU, intended users and acceptance check. For a connected assistant, include a restricted-access test and a clearly defined action it must refuse. For a data project, record identity rules, refresh needs and billable operations. Those details let people agree on the work even when their reference documents use different labels.
Update the glossary and training notes when terminology changes. Change API identifiers, integrations and configuration only when the relevant technical documentation calls for it. Your automation should not need a new passport every time the presentation gets a new title.
If the conversation turns from names to budget, use our Agentforce pricing guide. If it turns to build tooling, the Vibes pilot guide covers a different workload. The glossary can translate the meeting. The scope and acceptance checks still have to finish it.
Make the project scope clearer than the slide title
We can help map the product, entitlement and acceptance checks to the work your team needs to do.
Four fields, no call required. We reply within one business day.
Frequently asked questions
Was Claudeforce renamed AIforce?
No. Salesforce describes Claudeforce as its Anthropic partnership, AIforce as the underlying interface layer, and Salesforce in Claude as a product experience delivered through that partnership. These names describe different things.
Where does SIforce fit?
Marc Benioff announced AIforce as SIforce in an October 2026 post. Salesforce documentation checked on October 30 still uses AIforce. Match the announcement to current product documentation and your actual entitlement rather than assuming every label has changed everywhere.
Does a product rename require a migration?
The name alone does not answer that. Check the release note for your feature, its availability, licence requirements and any documented migration steps. Keep marketing names separate from API identifiers and configuration changes.