Tag: Agentforce

Of everything Salesforce announced under AIforce at Dreamforce 2026, Agentforce Coworker is the piece most admins will meet first. It is not a pilot you apply for. In many orgs it is already switched on, because Salesforce began turning it on automatically from 10 August 2026. This guide explains what Agentforce Coworker is, what it can and cannot touch, what it costs, how to turn it on or keep it off, and how to fix the errors admins run into during setup.

Agentforce Coworker at a glance

What is Agentforce Coworker?

Agentforce Coworker is an AI assistant that sits in the Salesforce search bar inside Lightning. A user types a question in plain language, and instead of a list of matching records they get one written answer built from the data they are allowed to see. Salesforce’s own Coworker FAQ describes it as a teammate that can reason over complex requests, build a multi step plan and call backend tools to finish the task.

The simplest way to think about it: Coworker replaces “search, open five records, read, piece it together” with “ask once, get the summary”. It does not replace your agents, your flows or your reports. It sits in front of them and becomes the single entry point to them.

Agentforce Coworker timeline

• May 2026: Marc Benioff announced Coworker as an AI teammate “inside every Salesforce search bar”, and it opened as a beta for Agentforce customers.
• 10 August 2026: Salesforce started enabling it automatically for eligible orgs, on a rolling basis.
• 15 September 2026: At Dreamforce it became one of the three products inside AIforce, next to Claudeforce and Slackforce. Salesforce said 100,000 users activated it in the first 35 days.

Agentforce Coworker vs traditional Salesforce search

Classic global search is good at one thing: finding a record when you already know roughly what it is called. Coworker is built for the questions that sit between records.

Where Agentforce Coworker works

The Lightning search bar is where most users first see it, but Salesforce’s Agentforce Coworker page lists more surfaces: Slack, Microsoft Teams, Claude, ChatGPT and mobile. The point is that the same assistant, with the same permissions, follows the user into whichever tool they already have open. That is the idea behind AIforce as a whole, and it is why Coworker pairs naturally with Claudeforce for teams that already work in Claude.

What Agentforce Coworker can search and do

According to the Salesforce developer guide and the help FAQ, Coworker reads across three kinds of source:

• Salesforce CRM data: accounts, contacts, opportunities, cases, custom objects, knowledge articles and past case history.
• Slack: messages, channels and conversations the user can already access.
• Data 360 sources: Salesforce says more than 270 external sources connect through Data 360 connectors, including data lakes, knowledge bases and enterprise apps such as Jira.

On top of search, it does three things that matter in daily work:

• Create or update records. It checks permissions and validation first, and asks the user to confirm before it saves anything. Today this works only on Salesforce CRM records, not on Slack or external data.
• Route the request. If a question belongs to a specialised agent, for example a service agent or one of the named agents like Casey or Piper, Coworker hands it over rather than guessing.
• Summarise across sources. A sales rep can ask what is putting a deal at risk and get the open cases, the Slack thread about pricing and the stalled approval in one answer.

Agentforce Coworker use cases and example prompts

The value shows up when people ask the questions they currently answer by opening several tabs. These are the kinds of prompts that fit each team.

Sales

• “What should I know before my call with this account tomorrow?”
• “Which of my opportunities closing this quarter have had no activity in two weeks?”
• “Log a note on this opportunity: pricing approved, legal review next week.”

Service

• “Has this customer reported this issue before, and how was it fixed?”
• “Why are cases about login errors spiking this week?”
• “Find the knowledge article that answers this case.”

Customer success and leadership

• “Summarise open cases, renewal date and recent Slack discussion for this account.”
• “Which strategic accounts have an open escalation and a renewal in the next 90 days?”

For the wider picture of where agents earn their keep, see our Agentforce use cases guide.

How it handles security and permissions

Salesforce says Coworker “fully honors the existing Salesforce access model”. It runs with the permissions of the person using it, so if a user cannot open a record, Coworker cannot read it for them. Behind that sit attribute based access control, PII masking, toxicity detection and result grounding through Data 360, and the AIforce announcement repeats the zero data retention model for the underlying language models.

External sources need more thought. Permission aware sources carry their access rules across automatically, and federated sources enforce permissions in real time at the source. For other connectors, an admin has to create governance policies in Data 360 by hand. Data from sources that are not zero copy is ingested and stored in Data 360, which matters for data residency reviews.

The practical catch is that “respects your permissions” is only as good as the permissions themselves. Many orgs have years of broad sharing rules, public read on objects that should be private, and profiles that were cloned instead of designed. Search used to hide that problem because nobody scrolled through everything. A good AI answer surfaces it in seconds. If you have not reviewed sharing in a while, do that before you roll Coworker out widely. Our Agentforce readiness checklist covers the same ground.

Automatic enablement: is Coworker already on in your org?

Salesforce’s automatic enablement FAQ says the rollout began on 10 August 2026 on a rolling basis. Your org is in scope if it has Unmetered User Based AI seats and Einstein is active.

Some orgs are left out of automatic enablement:

• Orgs that have opted out of generative AI.
• Multi dataspace or multi org setups.
• HIPAA, health and life sciences, and government orgs.
• Flex Foundation seats without Unmetered entitlements.

If your org is in scope and you would rather roll it out on your own schedule, there are two ways to opt out: the link in the notification email Salesforce sends, or Setup > Agentforce Coworker > Opt Out of Auto Activation. Users who gain an eligible seat after the automatic switch on still need an admin to give them access by hand.

Agentforce Coworker pricing: what does it cost?

For most seat based customers, the search itself is included. Salesforce states that searching CRM data and Slack carries no extra fee for users on eligible Unmetered seats, and that their usage shows as zero consumption in the Digital Wallet.

Costs appear in two places:

• Data 360 objects. Answers that pull from connected Data 360 objects consume Flex Credits or Data Services Credits.
• Users without an eligible seat. Anyone who loses an Unmetered seat moves back to normal Flex Credit or Data Services Credit billing.

So the budget question is not “what does Coworker cost” but “which users are on metered seats, and how much Data 360 do we plan to expose”. If you are still working out how Flex Credits are counted, start with our Flex Credits explainer, and read the Core, Advanced and Max editions change alongside it, since the new editions bundle credits differently.

Requirements to turn on Agentforce Coworker

If your org was not switched on automatically, you can turn it on yourself. The setup guide and the help FAQ list these requirements.

How to turn on Agentforce Coworker, step by step

1. In Setup, type Agentforce Coworker in the Quick Find box.
2. Select Get Started with Agentforce Coworker, click Turn On and confirm. Einstein turns on automatically at this point. Setup takes a few minutes, and Salesforce shows a warning if any prerequisite is missing.
3. If your org has more than one data space, choose the data space, then select the data sources Coworker should use.
4. In the Manage Users section, click Manage and assign the Access_Ai_Search permission set group to the users who should have it.
5. For seat based access, open each user in Setup, go to Permission Set License Assignments, tick Unmetered User-Based AI and save.
6. Test with two or three users from different roles before you widen access. Ask each the same question and check that the answers differ in the way their permissions say they should.

Troubleshooting common Agentforce Coworker errors

These are the errors Salesforce lists in its troubleshooting FAQ, with the fix for each.

Limits worth knowing before rollout

• 30 language model calls per minute per user. Salesforce notes this is not technically enforced yet, but one question can trigger several calls, so heavy users will reach it sooner than the number suggests.
• Record updates are CRM only. Coworker can read Slack and Data 360, but it can only write to Salesforce records.
• Files over 75 MB are not indexed, so very large documents will never show up in answers.
• English only during the beta. Salesforce says other languages follow at general availability.
• Not yet available in GovCloud. It does work for authenticated Experience Cloud users.
• Answers are only as good as the data. Duplicate accounts, empty close dates and stale opportunity stages all show up in the answer. An AI summary of messy data is still messy data, just faster.

A sensible Agentforce Coworker rollout plan for admins

Whether Coworker is already on or you are about to switch it on, the order of work is the same:

1. Check the status. Open Setup and see whether Coworker is active and who has the Access_Ai_Search group.
2. Review sharing. Look at organisation wide defaults, sharing rules and the objects with public read. Fix what you would not want a quick question to reveal.
3. Clean the high use objects. Merge duplicate accounts and contacts and fill the fields reps rely on, such as stage, close date and next step.
4. Decide on Slack and Data 360. Connect Slack if your teams live there. Connect Data 360 sources only where the value is clear, set governance policies for any source that is not permission aware, and remember those answers consume credits.
5. Start with a pilot group. Pick one sales team and one service team, collect the questions they actually ask, and write short guidance on what Coworker is good at.
6. Measure. Track adoption, the questions that return weak answers and credit consumption for the first month before you expand.

If you need help with the sharing review, the data clean up or the Data 360 connections, our Salesforce managed services and Data Cloud consulting teams work on exactly these steps.

Frequently asked questions about Agentforce Coworker

Is Agentforce Coworker part of AIforce?

Yes. At Dreamforce 2026 Salesforce grouped Agentforce Coworker, Claudeforce and Slackforce under AIforce, its new interface layer for reaching Salesforce data from any screen.

Is Agentforce Coworker free?

Searching CRM data and Slack carries no extra fee for users on eligible Unmetered User Based AI seats. Answers that use Data 360 objects consume Flex Credits or Data Services Credits, and users without an eligible seat are billed on credits.

Was Agentforce Coworker turned on automatically?

Possibly. Salesforce began automatic enablement on 10 August 2026 for orgs with Unmetered User Based AI seats and Einstein active. HIPAA, health, government and multi org setups were excluded.

How do I opt out of automatic activation?

Use the opt out link in the Salesforce notification email, or go to Setup, Agentforce Coworker, and turn on Opt Out of Auto Activation.

Can Agentforce Coworker see data a user cannot see?

No. It runs with the permissions of the person using it, so it can only read and change what that user can already read and change.

Does Agentforce Coworker work in Slack and Microsoft Teams?

Yes. Salesforce lists Slack, Microsoft Teams, Claude, ChatGPT and mobile as surfaces alongside the Salesforce search bar.

Which editions support Agentforce Coworker?

Enterprise, Unlimited and Agentforce 1 editions, with Data Cloud or Data 360 in place.

Why can’t I see Agentforce Coworker in my org?

Usually the user is missing the required permission set licence or the Access_Ai_Search permission set group. Check both in Setup before looking for anything else.

The bottom line

Agentforce Coworker is the most visible part of AIforce because it lives where every user already clicks: the search bar. It costs little or nothing for most seat based orgs, and it may already be running in yours. The real work is not switching it on. It is making sure your permissions and data are in a state where a fast, confident answer is also a correct one. Start there, pilot small, and expand once the answers hold up.

For two years Agentforce was something you built. You picked a topic, wrote instructions, wired up actions, tested it, and hoped the thing behaved in production. At Dreamforce in September 2026 Salesforce changed the starting point: seven named agents that arrive already configured for a specific job, six of them generally available on day one.

That shift is bigger than the names suggest. A prebuilt agent is an opinion about how a job should be done, baked into software. It will fit some orgs closely and fight others. This guide goes through all seven, what each one is actually scoped to do, which cloud it needs, what is shipping today versus later, and where we would not use it.

The seven Agentforce named agents at a glance

1. Casey: the service agent that finally covers voice

Casey handles customer service issues end to end across voice, SMS, WhatsApp and web chat. The channel spread is the part worth noticing. Most deflection projects we see start and stop at web chat, because chat is where the transcript is clean and the integration is easy. Voice is where the volume and the cost actually sit, and voice is where a handover to a human has always been ugly.

What Casey is good at: repeat, policy driven questions where the answer exists in a knowledge article or a record. Order status, appointment changes, password and access issues, returns inside policy.

What it does not remove: the need for a clean knowledge base. An agent that reads bad articles gives confident bad answers faster than a human would. If your knowledge base has not been audited in a year, that audit is the first project, not the agent.

2. Paige: employee service, where the ROI case is easiest

Paige answers IT and HR service requests inside Slack and employee portals. Of the seven, this is the one with the least risk attached, because the audience is internal. A wrong answer to an employee costs a follow up ticket. A wrong answer to a customer costs the customer.

That makes Paige a sensible first deployment even for an organisation whose real target is customer facing automation. You get the operating experience, the prompt tuning habits and the escalation design without putting revenue on the line while you learn.

3. Carter: commerce assistance, not a storefront replacement

Carter works inside Commerce Cloud on product discovery, comparison and checkout assistance. It is the agent most often confused with something it is not. Carter does not replace your storefront, your catalogue structure or your merchandising rules. It sits on top of them, and it inherits their quality.

If product data is thin, if attributes are inconsistent between categories, or if the same item appears three times under different SKUs, Carter surfaces those problems to shoppers rather than hiding them. Catalogue hygiene is the prerequisite. We cover how that data flows in our guide to Salesforce ecommerce integrations.

4. Piper: inbound lead qualification

Piper engages and qualifies inbound leads across websites and email. The job is speed to lead and consistency of questioning, two things humans are reliably bad at on a Friday afternoon.

The caution here is qualification criteria. Piper applies whatever definition of a qualified lead you give it, at scale, without the quiet human correction that normally happens in the background. If your MQL definition has drifted from what sales will actually accept, an agent will expose that gap within a week. Fix the definition before you automate it.

5. Fin: the cross channel workflow agent

Fin is scoped to complex customer experience workflows that span channels, which is the vaguest brief of the seven and also the most interesting. Think of the cases that start in chat, move to email, require a back office action and end with an outbound confirmation. Those are the ones that fall through today, because no single team owns them end to end.

Fin is worth evaluating if your complaint volume is driven by process breakage rather than by product problems. It is not worth evaluating if your handoffs are undocumented, because there is nothing for it to follow.

6. Marshall: deterministic back office execution

Marshall orchestrates back office processes with what Salesforce calls deterministic execution. That word matters. Most of the anxiety around agents in finance and operations comes from non determinism: the same input producing a different sequence of steps on different days. Marshall is positioned as the answer to that, running defined processes in a defined order rather than reasoning its way to an outcome.

Where this fits: invoice handling, order processing, fulfilment exceptions, reconciliation steps that today sit in a spreadsheet and a person’s head. Where it does not: anything where the process itself is undefined. Marshall executes a process, it does not design one for you.

7. Hunter: outbound pipeline, and the one that is not GA yet

Hunter covers outbound sales pipeline from account research through to outreach, and it is the only one of the seven still in pilot, with general availability expected in November 2026. It is also the agent that debuts long horizon runtime, which is the genuinely new platform capability in this release.

Long horizon runtime means an agent can pursue a goal across days and weeks rather than inside a single session. It preserves memory between runs, survives interruption through durable execution, and can be steered mid flight without being restarted. For outbound that is the difference between a sequence and a campaign that adapts.

It is also the capability that deserves the most governance attention. An agent working a goal for three weeks accumulates three weeks of decisions nobody reviewed individually. Decide in advance what it is allowed to send, to whom, and what it must escalate.

What shipped alongside the agents

Three platform pieces came with the agent portfolio and change how the seven are used together.

Multi agent orchestration is generally available now, and routes work across the specialised agents so they operate as a team rather than seven separate deployments. This is what stops Casey and Fin from both claiming the same case.

AI Skills in Agentforce Coworker lets an employee teach a task once and have it reused across the workforce. It is in pilot now with general availability expected in October 2026.

Agent Optimizer covers building, refining, testing and analysing agent performance across the lifecycle, with general availability expected in October 2026. Until it lands, measurement of agent quality is still something you assemble yourself.

All of this sits inside the wider announcement Salesforce made at Dreamforce. If you want the commercial side, including which Flex Credit allowance comes with which tier, start with what AIforce actually changed and the Core, Advanced and Max editions.

When a named agent is the wrong answer

Four situations where we would tell a client to wait.

The underlying data is not trustworthy. Every one of these agents reads your records and your content. Duplicate accounts, stale knowledge articles and half migrated product data do not get smoothed over by an agent, they get amplified and put in front of a customer.

The process is undocumented. Marshall and Fin in particular assume a process exists. If the answer to “what happens next” depends on which person picks it up, an agent has nothing to follow.

Your volume is low. An agent earns its keep on repetition. A team handling forty cases a week will spend more effort tuning than it saves.

The job is judgement, not throughput. Complaint escalations that involve goodwill decisions, a renewal conversation with an unhappy account, anything with a legal or clinical dimension. Those stay human, with the agent doing preparation rather than resolution.

How to choose which one to turn on first

The order we recommend, and the reasoning behind it.

Start with Paige if you have an internal service desk. Lowest blast radius, fastest feedback loop, and the operating habits transfer directly to the customer facing agents afterwards.

Start with Casey if service cost is the board level number. It is the only one of the seven that touches voice, which is usually where the cost sits.

Start with Piper if speed to lead is the bottleneck. Measure current first response time before you deploy, because this is the one agent whose effect shows up in a single clean metric.

Wait on Hunter unless you are comfortable in a pilot. General availability is expected in November 2026, and long horizon runtime is new enough that early deployments are learning exercises as much as productivity ones.

Whichever you pick, scope one job, instrument it, and run it for a month before adding a second. Teams that switch on four agents at once cannot tell which one caused the change in their numbers.

What this means for existing Agentforce builds

If you already built custom agents, the named agents do not obsolete them, but they should prompt a review. Anything you built that maps closely to one of the seven jobs is now maintenance you may not need to carry. Anything you built that is specific to your business, your products or your regulatory position is exactly what should stay custom.

The practical exercise is to list your current agent topics against the seven and mark each as replace, keep or merge. Our Agentforce readiness checklist covers the questions to ask before either path, and the implementation partner guide covers how the delivery work is usually split.

The named agents are not the only way users reach Agentforce. Agentforce Coworker in the Lightning search bar routes a question to the right specialised agent on its own, and our Agentforce Coworker guide explains how that works and what it costs.

The named agents arrive alongside a busy platform release. See the Salesforce Winter ’27 release guide for the 15 changes to test in your org, including the new Agent Skills registry.

Frequently asked questions

Are all seven Agentforce named agents available now?

Six are generally available: Casey, Paige, Carter, Piper, Fin and Marshall. Hunter is in pilot, with general availability expected in November 2026.

Do the named agents replace custom built Agentforce agents?

No. They cover common, well defined jobs. Anything specific to your products, your industry rules or your internal processes still needs to be built, and the two run alongside each other under multi agent orchestration.

Which licences do the named agents need?

Each sits inside a product area, so Casey needs Service Cloud, Carter needs Commerce Cloud and so on. Consumption is drawn from the Flex Credit allowance that comes with your edition, which means two organisations on the same edition can see very different usage. Confirm current entitlements with Salesforce or your account executive before budgeting.

What is long horizon runtime?

It lets an agent pursue a goal across days and weeks instead of within one session, by preserving memory between runs, surviving interruptions and accepting steering mid task. Hunter is the first agent to use it.

Where do we start if we have never deployed an agent?

With an internal use case, a documented process and a single measurable metric. Paige on an IT or HR service desk is the usual low risk starting point.

Talk to us about which agent fits

Ashapura Softech is a certified Salesforce partner working with teams in the United States on Service Cloud, Sales Cloud, Commerce Cloud and Agentforce delivery. If you want a view on which of the seven fits your org, and what would have to be cleaned up first, get in touch.

On 15 September 2026, at Dreamforce in San Francisco, Salesforce announced AIforce. The framing Salesforce used for it is blunt: AI replaces the UI. Instead of asking people to open Salesforce to get work done, AIforce lets AI agents read and act on Salesforce data from wherever the person already is, whether that is Claude, Slack, Lightning or a tool your own team has built.

If you run a Salesforce org, this is the announcement from this Dreamforce that actually changes how your users will touch the system. Here is what was announced, what is available today, and what it is reasonable to do about it this quarter.

What is AIforce?

AIforce is a layer on top of Salesforce’s existing Agentic Enterprise architecture, not a replacement for Agentforce. It takes what already sits in your org, Customer 360 records, Data 360 context and the Agentforce agents you have configured, and exposes them to AI interfaces outside the Salesforce UI.

The practical effect is that a rep can update an opportunity, log a call, pull pipeline or ask for account research without opening a Salesforce tab. Marc Benioff described the idea as combining model intelligence with the context customers have already built inside Salesforce to create a composable system.

The word composable is doing real work in that sentence. AIforce is built on the Headless 360 toolkit Salesforce shipped in March 2026, which exposes platform capability through APIs, Model Context Protocol servers and developer tooling. Agents are assembled from those pieces rather than bought whole.

The three products inside AIforce

Claudeforce

Claudeforce is the extended Anthropic partnership. It puts Salesforce inside Claude, shipping with 37 prebuilt sales skills covering work like prospecting and pipeline management, with analytics and further skills for service, marketing, commerce and industries on the roadmap. There is also a Salesforce Development plug in for Claude Code carrying more than 40 skills for developers.

Salesforce in Claude is in beta and open to all customers now. If your team already uses Claude, this is the lowest friction way to see what the interface revolution actually feels like on your own data.

We covered the Salesforce and Anthropic partnership in detail in What is Claudeforce.

Slackforce

Slackforce brings Salesforce into Slack as an interactive surface rather than a notification feed. It includes a Slackbot assistant and Slack CRM, which lets a user create an account, log call notes and update records from a prompt without leaving the channel. Slack Code covers collaborative AI development in the same place.

For teams whose real working day happens in Slack, this closes the gap that CRM adoption programmes have been fighting for a decade. Data quality problems are usually a data entry friction problem, and this removes a large part of that friction.

Agentforce Coworker

Agentforce Coworker is an AI teammate inside the Lightning interface, working across devices and operating strictly inside your existing business rules, permissions and security model, with zero data retention. Salesforce has described it as instantly available to customers.

Coworker is the part of AIforce most admins will meet first, because Salesforce began switching it on automatically in August. We cover eligibility, cost, the opt out setting and the setup steps in our Agentforce Coworker guide.

Coworker is the one to test first if your objection to agents so far has been governance. It inherits the permission set of the person it is working for, so it cannot see what that person cannot see. Our guide to Agentforce use cases covers where agents have actually been shipped in practice.

The Headless Toolkit and AgentExchange

Underneath the three products sits the Headless Toolkit, which exposes platform elements through MCPs, APIs, plug ins and skills so you can build your own AI experience rather than take one off the shelf. AgentExchange is where partners publish integrations, with Anthropic, AWS, Google, OpenAI, DocuSign and Vercel already named in that ecosystem.

This matters for anyone with a non standard process. The interesting AIforce work in 2027 will not be turning on Coworker, it will be exposing your own objects, validation rules and approval flows as skills an agent can call safely.

Salesforce Core, Advanced and Max: the edition change to read alongside it

Salesforce also simplified its editions, effective September 2026, into Core, Advanced and Max across Agentforce Sales, Service and Industries. Every edition now bundles Agentforce capabilities such as Account Research and Service Rep Assistant, Slack and Slackbot, embedded agentic analytics powered by Tableau Next, enterprise grade data security and Premier Success Plans, along with Flex Credits: 500K on Core, 1M on Advanced and 2.75M on Max.

List pricing is 195 dollars per user per month for Core, 395 for Advanced and 550 for Max. Salesforce has said existing Agentforce 1 Edition customers can move to Max at no extra cost, legacy edition pricing is unchanged for current customers, and Industry Edition pricing is still to come this autumn.

Confirm your own numbers with your account executive before you budget against these. Published list pricing and what lands on a renewal quote are rarely the same thing, and consumption based Flex Credits change the shape of the bill.

What this actually changes for your org

Your interface strategy is now a real decision. Until this announcement, “where do users work” had one answer. Now there are four plausible answers and you should pick deliberately per team rather than let it happen by accident.

Permissions and sharing rules become the control surface. An agent that inherits a user’s permissions is only as safe as those permissions are tidy. If your profiles and permission sets have drifted over years of ad hoc requests, that debt is about to become visible in a new way.

Data quality gets more exposed, not less. An agent asked to research an account will answer from what is in your org. Duplicate accounts, stale contacts and half filled custom fields have been survivable while a human was reading the record and mentally correcting it. They are less survivable when the answer arrives as a confident sentence.

Automation you already have may be duplicated. Before you build an agent for a task, check whether a Flow already does it. Agents are the right tool for judgement and language, not for deterministic steps a Flow handles cheaply.

A sensible order of work

1. Turn on Salesforce in Claude for a small group, in a sandbox or with a limited permission set, and watch what people actually ask it.
2. Run a permissions audit before you widen access. Profiles, permission sets, field level security, sharing rules.
3. Run a duplicate and data completeness pass on accounts and contacts, since that is what agent answers are built from.
4. Pilot Agentforce Coworker with one team and one measurable task rather than across the org.
5. Model your edition options against actual usage before renewal, including what Flex Credit consumption looks like at your volume.

Steps two and three are unglamorous and they are where most of the value is. Agent quality is downstream of org hygiene, which is the bulk of what our Salesforce managed services team spends its time on.

Frequently asked questions about AIforce

Is AIforce the same as Agentforce?

No. Agentforce is the agent platform inside Salesforce. AIforce is the layer that lets those agents and your Salesforce data be reached from outside the Salesforce interface, through Claude, Slack, Lightning or your own build.

Is AIforce available now?

Salesforce in Claude is in beta and open to all customers. Agentforce Coworker has been described as instantly available. Other components, including further Claudeforce skills for service, marketing, commerce and industries, are on the roadmap rather than shipped.

What does AIforce cost?

Salesforce has not published separate AIforce pricing. The related edition pricing effective September 2026 is 195, 395 and 550 dollars per user per month for Core, Advanced and Max respectively, with Flex Credits included at each tier. Check current pricing with Salesforce directly.

What are Salesforce Flex Credits?

Flex Credits are the consumption units bundled with the new editions, 500K with Core, 1M with Advanced and 2.75M with Max. Because agent usage draws on them, two orgs on the same edition can see very different bills depending on how heavily agents are used.

Do we need Data Cloud for this to work well?

You do not strictly need it, but the quality of agent answers depends on the context available to them. If your customer data is spread across systems Salesforce cannot see, that is the gap to close first. Our Salesforce Data Cloud and Data 360 consulting page covers what that work involves.

Where should a mid sized team start?

With one team, one task, and a permissions audit first. Agent quality follows org hygiene, so the groundwork matters more than the agent configuration.

Where AIforce lands

We are a certified Salesforce partner working with teams in the United States from Irving, Texas, with our development centre in Ahmedabad. The work we expect to matter most over the next two quarters is not agent configuration, it is the permission, data and automation groundwork that decides whether an agent gives a useful answer or a confidently wrong one.

If you want a second opinion on where your org stands before you widen agent access, get in touch.

Two pieces of this are worth reading on their own. The commercial change is covered in our guide to the Core, Advanced and Max editions, and the earlier question of how the two agent platforms differ is answered in Claudeforce vs Agentforce. If you are working out a credit budget, Flex Credits explained has the arithmetic.

The seven named agents announced alongside all this are covered one by one, with status and licence notes, in our guide to the Agentforce named agents.