Most Salesforce teams found out about this one the hard way. Integration alerts started firing overnight in the US, users in Europe and Asia could not log in, and the usual escape route, opening a case with Salesforce Support, was broken too. By the time the US woke up, the fix was already rolling out, so plenty of people only saw the tail end and assumed it was over.

It wasn’t, at least not for every org. Salesforce itself reported that scheduled jobs were not running as expected for some customers even after access came back. That is the part of a Salesforce outage that quietly causes problems weeks later: a nightly sync that never ran, a renewal reminder that never went out, a batch job that stopped halfway.

This guide covers what happened, what is confirmed and what is not, a practical checklist for admins, how to check whether Salesforce is down right now, and what to put in place before the next one.

What happened during the Salesforce outage on 16 September 2026

Salesforce tracked the incident on its Trust status site as incident 20004433. The timeline below is built from Salesforce’s status updates as reported by Salesforce Ben and CIO.

So the hard outage lasted about 7 hours 36 minutes, and the incident stayed open for roughly 11 hours while Salesforce confirmed every instance was stable.

How big was the outage?

Salesforce’s Trust site described “hundreds of instances” affected across all regions. Reports that track the Trust record say the list peaked above 1,000 instances during the incident, and was later trimmed to 912 of about 3,243 once Salesforce removed instances that had never been affected. Salesforce also said the impact was “narrower than initially understood”.

A few details matter for working out whether your org was hit:

• GovCloud was not affected, according to Salesforce’s updates.
• Hyperforce instances recovered last. The final stretch of the incident involved a subset of Hyperforce instances.
• It was an application problem, not a network one. Independent monitoring cited by CX Today saw HTTP 503 errors and timeouts with no network degradation.
• Well-known companies felt it. CX Today reported effects at PayPay, Sage (UK and Ireland support teams), Vonage and Veeva CRM users. In one case, web forms kept collecting leads but the data had to sync into Salesforce after recovery.

What caused the Salesforce outage?

Here is what Salesforce has said, and nothing more. Requests stalled while waiting for a response from an internal login service, and those stalled requests used up server resources. Early on, Salesforce suspected an external dependency affecting its legacy login server, but its third-party infrastructure provider reported no issues. Salesforce also pointed to increased load on a core system component.

Salesforce apologised and said it would establish “the technical trigger, the underlying cause, and preventive action”. As of 14 October 2026, we could not find a published root cause analysis on the Trust site or in Salesforce’s public statements. Until one appears, treat any detailed explanation you read online as a guess.

If your business depends on Salesforce, ask your account executive for the post-incident report. It is the only way to know whether the fix covers the kind of failure that hit your org.

A second incident a few days later: Data Cloud

Around 19 September, Data Cloud activations in the US-East-1 region were down for 13 hours 41 minutes. Salesforce said that problem came from a third-party cloud storage service and that it was preparing an alternate storage option. If you use Data Cloud (now Data 360) activations to feed marketing or ads, check that segments activated that week actually reached their destinations.

Not related: Chrome and Edge freezing

Around the same time, some users on Chrome and Edge 153 saw the Salesforce interface freeze. Salesforce linked that to an external Chromium update, separate from the outage. A Chrome fix was released first. If users still report freezing, check their browser version before assuming it is another outage.

Post-outage checklist for Salesforce admins

If your org was on an affected instance, logins working again does not mean everything caught up. Here is the order we would work through it. Most of it takes an afternoon.

1. Confirm your instance and the impact window

Find your instance on status.salesforce.com and note when it was affected. Use that window for every check below. Write it down; you will need it for your incident log and for any conversation with Salesforce.

2. Check scheduled Apex and scheduled jobs

Salesforce reported scheduled jobs not running as expected after access returned. Run this query in the Developer Console or Workbench and look for jobs whose last run is before the outage when they should have run during or after it:

SELECT CronJobDetail.Name, CronJobDetail.JobType, State, PreviousFireTime, NextFireTime
FROM CronTrigger
ORDER BY PreviousFireTime

Any job that missed its slot needs a manual run. Also check Setup, then Scheduled Jobs, for dashboard refreshes and reporting snapshots, which fail quietly.

3. Check batch and queueable Apex that failed or stopped

SELECT ApexClass.Name, JobType, Status, ExtendedStatus, NumberOfErrors, CreatedDate
FROM AsyncApexJob
WHERE CreatedDate >= 2026-09-16T07:00:00Z
AND CreatedDate <= 2026-09-17T00:00:00Z
AND Status IN ('Failed', 'Aborted')

Batch jobs that failed partway may have updated some records and not others. Re-run them only if the job is safe to run twice; otherwise fix the gap by hand or with a targeted job.

4. Review paused and failed flows

Go to Setup, then Paused and Failed Flow Interviews. Scheduled-triggered flows that did not run will not show up here, so compare them against what should have happened that day (for example, reminder emails or status updates).

5. Reconcile integrations

This is where most of the damage hides. For each integration (ERP, billing, marketing automation, support tools):

• Check the integration’s own error log for failed calls in the outage window.
• Look for duplicates. Retry logic often creates the same record twice when the first call actually succeeded.
• Look for gaps. Records created in the other system during the outage may never have reached Salesforce.
• Check the integration user’s Login History (Setup, then Login History) for failures, and make sure no one rotated credentials in a panic during the outage.

6. Check web-to-lead, web-to-case and inbound email

Forms and email-to-case are the front door for customers. Compare the number of leads and cases created that day against a normal day. If your form tool stores submissions, re-send the missing ones.

7. Confirm support cases you tried to log

Case creation on Salesforce Help was disrupted. If you opened a case with Salesforce during the outage, confirm it actually exists.

8. Write a short incident log

Record the impact window, what failed, what you fixed and what is still open. It takes 20 minutes and makes the next outage much easier, and it is the evidence you need if you raise the issue at renewal.

How to check if Salesforce is down right now

When users say “Salesforce is down”, it is usually one of three things: a real Salesforce incident, a problem in your own org (a broken flow, a permission change, an expired integration credential), or a browser or network issue on the user’s side. Here is how to tell them apart quickly.

1. Check Trust first. Open status.salesforce.com, search for your My Domain or instance name, and look for open incidents or maintenance.
2. Subscribe to alerts. Trust lets you subscribe to notifications for your instance. Do it now, for your admin and one backup person, so you are not relying on users to tell you.
3. Test from a second network and browser. If Salesforce works on mobile data but not in the office, the problem is probably local.
4. Check scheduled maintenance. Release weekends (like the Winter ’27 upgrades) and planned maintenance can briefly limit access. Trust lists them in advance.
5. Check your own recent changes. If only some users or one process is affected and Trust is green, look at recent deployments and Setup Audit Trail before blaming Salesforce.

Does Salesforce owe you credits for the outage?

We have not seen any report of Salesforce offering credits for this outage. Whether you are entitled to anything depends on what your contract says, so check your order form, your Master Subscription Agreement and your Success plan, and ask your account executive directly.

Even if there is nothing in the contract, an outage of this size is a fair point to raise at renewal, especially if you have your incident log and the business impact written down.

How to make your org less exposed next time

No customer can stop Salesforce from having an outage. What you can control is how much damage one does. These are the changes we would prioritise:

• Make integrations safe to retry. Use upserts with external ID fields instead of plain inserts, so a retried call updates the same record instead of creating a duplicate.
• Queue instead of failing. Put a message queue or middleware between Salesforce and critical systems, so data waits during an outage and flows in afterwards.
• Give integrations their own users. Integrations running on a named employee’s login are hard to monitor and break when that person leaves. Salesforce is also moving AI agents to their own registered identities from November; our guide to what AIforce changes in your implementation covers that.
• Monitor from outside Salesforce. A simple check that alerts you when logins or key API calls fail will tell you about the next outage before your users do.
• Agree a fallback for the front line. Decide in advance how sales and support will work if Salesforce is unavailable for half a day: which shared inbox or spreadsheet they use, and who enters the data afterwards.
• Write the runbook now. Turn the checklist above into a one-page document with names next to each step.

If you would rather have someone else watch your org, our Salesforce managed services team handles monitoring and post-incident clean-up, and our guide to Salesforce integration with other tools covers building integrations that survive this kind of failure.

Our take: the outage itself was fixed within a working morning in the US. The real cost for most companies will come from the quiet failures afterwards, such as a sync that skipped a night or a job that ran halfway. If you have not checked those yet, an hour spent on the checklist above is worth it.

Frequently asked questions

When was the Salesforce outage in September 2026?

It started on 16 September 2026 at 07:50 UTC (12:50 AM Pacific), during Dreamforce. Service was healthy from 15:26 UTC, and Salesforce marked the incident resolved at 18:59 UTC the same day.

What caused the Salesforce outage?

Salesforce said requests stalled while waiting on an internal login service, which used up server resources, and that a core system component was under increased load. It has not published a full root cause analysis as of 14 October 2026.

How many Salesforce instances were affected?

Salesforce described hundreds of instances in all regions. Reports tracking the Trust record put the final figure at 912 of about 3,243 instances. GovCloud was not affected.

Is Salesforce down today?

Check status.salesforce.com and search for your instance or My Domain. If Trust shows no incident, the problem is more likely in your org, your network or your browser.

Did Salesforce give credits for the outage?

No credits have been reported. Any entitlement depends on your contract and Success plan, so ask your account executive.

What should admins check after a Salesforce outage?

Scheduled jobs and scheduled flows, failed batch and queueable Apex, paused and failed flow interviews, integration errors, duplicates and gaps, web-to-lead and email-to-case volumes, and any support cases you tried to open during the outage.

How we put this guide together

The timeline and cause come from Salesforce’s Trust status updates for incident 20004433, as reported by Salesforce Ben, CIO and CX Today, cross-checked against each other. Where sources disagreed (for example on duration), we used the times Salesforce itself confirmed. The checklist reflects how we would approach recovery in a Salesforce org; the queries use standard Salesforce objects. We will update this page if Salesforce publishes a root cause analysis.

Three names in two months. Headless 360 in spring, AIforce at Dreamforce, and SIForce last week. If you look after a Salesforce org, the obvious worry is that one of these quietly turns into a migration project nobody budgeted for.

We read Salesforce’s own impact notes so you don’t have to, and the honest answer is: it’s smaller than it sounds, but it isn’t nothing. This guide walks through the AIforce impact on your Salesforce implementation, what stays exactly as it is, the dates that matter, and the checklist we’d work through before the new rules switch on. If you want the background on the announcement itself, start with our explainer What Is AIforce?

What is Salesforce AIforce?

AIforce is Salesforce’s interface layer for AI. It brings Salesforce data, workflows and permissions into the tools people already work in, so a rep can ask Claude or Slack about an account instead of opening Salesforce. Salesforce first showed the idea at TDX 2026 under the name Headless 360 and launched it as AIforce at Dreamforce on 15 September 2026.

It arrives in three forms, all running on the same foundation:

• Claudeforce (Salesforce in Claude): a prebuilt MCP server with 37 sales skills that lets Claude read and act on Salesforce records. It launched in beta for Salesforce customers. Our guide to Claudeforce covers it in detail.
• Slackforce: Salesforce context and actions inside Slack, such as creating accounts or logging notes from a prompt.
• Agentforce Coworker: an AI teammate inside the Lightning interface that works within existing permissions and can call the Agentforce agents you have built. See our Agentforce Coworker guide.

Under all three sits the Headless Toolkit: the MCP servers, APIs, skills and plug-ins that expose the platform to outside AI tools. That toolkit is where the implementation impact comes from.

AIforce is now SIForce: what the rename means

On 9 October 2026, Marc Benioff posted on X: “AIForce is officially SIForce.” The rename followed a US executive order that asks federal agencies to say “super intelligence” instead of “artificial intelligence”.

For your org, the rename changes nothing yet. No features, prices or availability were announced with it, and Salesforce’s help documentation still uses the name AIforce. Our advice is the same as for the Agentforce product names Salesforce reversed in September: keep contracts, order forms and internal documents on the current names until your account team confirms how they will appear at renewal. In this guide we use “AIforce”, because that is the name in Salesforce’s own documentation today.

Do you need to migrate to AIforce?

No, not in the usual sense. There is no data migration, no new object model and no rebuild of your flows, reports or page layouts. AIforce reads from the org you already have.

The “migration” is narrower and more technical. It applies to agents: any AI tool, script or MCP client that connects to Salesforce on its own. Salesforce’s help article Understand AIforce Impact sets out two changes for them.

What Salesforce AIforce changes in your implementation

1. Salesforce agent registration: every agent gets its own identity

Right now, a lot of AI tools get into Salesforce by borrowing someone’s login or a shared integration user. Under the new model, admins register each agent through a feature called Agentic Identity. The agent gets its own identity on the platform, and you can give it a narrower permission set than any human user has.

Security-wise, this is a good change. An agent with its own identity can be limited, watched and switched off without touching a person’s account. The catch is the work behind it: someone has to find every agent, register it, and swap its OAuth credentials so Salesforce knows it’s talking to an agent and not a human.

2. Headless Platform Interactions: a new meter for agent calls

Each successful call a registered agent makes to Salesforce, over MCP or direct API, is metered as a Headless Platform Interaction (HPI). HPIs are tracked in Digital Wallet and paid for with Flex Credits, under the Customer 360 Platform section of the Flex Credits rate card.

Two details matter for budgeting:

• The price isn’t set yet. The HPI multiplier is listed as “TBA”, and Salesforce says it will give 30 days’ notice before metering begins.
• Your org must be on Flex Credit billing. Salesforce names Salesforce Foundations (listed at $0) or another SKU that enables Flex Credits. If Flex Credits are new to you, our guide to Agentforce pricing and Flex Credits explains how they work.

3. The deadline depends on how you buy and connect

Salesforce is targeting November 2026 for agent registration, the new security controls and the billing model.

Our take: the rename gets the headlines, but the meter is what will show up in budgets. If your renewal falls in the next six months, it’s worth getting the agent inventory done now, while the multiplier is still “TBA” and nothing is being charged.

4. Sandboxes stay free

HPIs are only charged in active production orgs. Sandboxes, scratch orgs and Developer Edition orgs aren’t metered, so your team can build and test agents without using credits.

What stays the same

Most of your implementation doesn’t change at all. This is the part teams worry about most, so here it is side by side.

Where your current setup will show its gaps

AIforce doesn’t create new problems in an org. It makes the existing ones visible faster, because an AI answer is only as good as the data and permissions behind it.

• Over-wide permissions. Every AIforce request runs as the user who makes it. If a profile has collected extra access over years of quick fixes, Claude or Slack will show that data to anyone who asks the right question. Permission sets that were “fine because nobody looks there” stop being fine.
• Duplicate and stale data. An agent asked to brief a rep on an account reads whatever is in the org. Duplicate accounts and opportunities stuck in old stages produce answers that sound confident and are wrong. Approval steps catch bad writes, not bad reads.
• Agents nobody listed. Scripts, browser extensions and MCP clients set up by individual teams are easy to miss. Under the new rules, an unregistered agent is both a security gap and an unplanned bill once metering starts.
• Integrations running on a person’s login. If an integration or AI tool uses a named employee’s account, it breaks when that person leaves, and it hides what the tool is actually doing. Registration is the right moment to fix this.

If you want to measure these gaps before the November changes, our free CRM health-check template covers permissions, data quality and integrations in 30 checks.

AIforce readiness checklist for existing Salesforce orgs

Here’s the order we’d tackle it in. For most mid-sized orgs this is a few days of admin time, not a project. Start with the inventory; everything else depends on knowing what’s actually connected.

1. Inventory every agent. List each AI tool, script and MCP client that connects to Salesforce, who owns it, and which user it runs as today.
2. Split production from sandbox. Only production calls will be metered, so note which connections touch production.
3. Design one permission set per agent. Give each agent the least access it needs. Don’t reuse an admin or a sales manager’s profile.
4. Confirm Flex Credit billing. Check whether your org already has Salesforce Foundations or another SKU that enables Flex Credits.
5. Note your renewal date. Existing API-based agents move to the new billing model at renewal, so that date sets your timeline.
6. Plan the credential switch. Each agent will need new OAuth credentials tied to its registered identity. Schedule the reconnection so nothing breaks mid-quarter.
7. Clean the data your first use case touches. Merge duplicate accounts and close out stale opportunities on the objects your pilot will read.
8. Pilot read-only first. Start one team on Salesforce in Claude or Agentforce Coworker with read access, check the answers, then allow writes with approval.
9. Watch for Salesforce’s notices. The Agentic Identity announcement starts the three-month clock, and the 30-day HPI notice tells you when billing begins.

Frequently asked questions

AIforce vs Agentforce: is it the same thing?

No. Agentforce is the set of AI agents that do work inside Salesforce. AIforce is the layer that lets people and agents reach Salesforce from Claude, Slack and Lightning. Agentforce Coworker is where the two meet. Our comparison of Claudeforce vs Agentforce goes deeper.

Is SIForce a different product from AIforce?

No. SIForce is the new name Marc Benioff announced on 9 October 2026 for the same product. No feature or pricing change came with it.

Do we have to pay extra for AIforce?

Salesforce hasn’t published a single AIforce price. What is confirmed is that registered agent calls to production orgs will be metered as Headless Platform Interactions and paid in Flex Credits, at a rate still listed as “TBA”. Confirm your entitlements with your account executive.

Will our existing integrations be billed as HPIs?

Traditional integrations keep their current pricing. The new meter applies to AI agents and MCP clients that are registered under Agentic Identity.

Which Claude plan does Salesforce in Claude need?

Published sources disagree, so check the current admin setup guide on AgentExchange or ask your Salesforce account team before you budget for it.

When do the new rules start?

Salesforce is targeting November 2026. New purchases from 17 September 2026 and anyone using a Salesforce MCP server have three months from Salesforce’s Agentic Identity notice to register agents. Existing customers with API-based agents move over at renewal.

The bottom line

AIforce, now SIForce, is not a migration of your Salesforce org. It is a new front door, and the house behind it stays the same. The work is in the doorway: knowing which agents come in, giving each one its own key, and budgeting for the new meter before it starts.

Ashapura Softech can run an AIforce readiness review for your org, covering an agent inventory, a permission audit and a Flex Credit estimate. Our Salesforce Agentforce consulting team handles agent setup and permissions, or you can talk to our Salesforce team directly.

How we put this guide together

Everything about registration, billing and deadlines here comes from Salesforce’s own help article on AIforce impact, dated 17 September 2026. Product details come from Salesforce’s Dreamforce announcements, and the rename from Marc Benioff’s post on 9 October. A few things are still open (the HPI price, final packaging), and we’ve said so where they come up rather than guessing. We’ll update this page when Agentic Identity goes live.

Most US companies that search for a custom ERP development company are not starting from zero. They already run QuickBooks, a few spreadsheets, maybe an old Access database that one person understands, and a packaged ERP trial that did not fit. The question is not really “who builds ERP?” It is “who can I trust with the system that runs my orders, stock, billing and payroll for the next decade?”

This guide covers how to choose a custom ERP development company: how to decide whether you need custom at all, what to check in a vendor, which questions to ask on the first call, how pricing models work, and the red flags we see buyers miss. If you already know you need custom and want to see budget ranges, our custom ERP software development page breaks down cost tiers and timelines.

In this guide:

• Do you actually need a custom ERP?
• What a custom ERP development company should deliver
• Custom ERP development company vs ERP implementation partner
• 8 things to check before you shortlist
• Questions to ask on the first call
• Pricing and engagement models
• Why ERP budgets slip
• Red flags
• Shortlist scorecard
• FAQ

First, do you actually need a custom ERP?

A good vendor will ask this before you do. Custom ERP makes sense when your core process is the thing that makes you money and no packaged product handles it without heavy workarounds. It makes less sense when your processes are standard (buy, stock, sell, invoice) and you just have not configured a packaged system properly.

A company that only sells one of these three options will usually steer you toward it. Ask every vendor on your shortlist which option they would pick for you and why. The honest ones will sometimes tell you not to build.

What a custom ERP development company should deliver

“ERP development” covers very different scopes. Before you compare quotes, make sure each vendor is quoting the same thing. A complete engagement normally includes:

• Discovery and process mapping. Workshops with finance, operations, sales and warehouse staff, ending in a written scope and a prioritised module list.
• Solution design. Data model, integration map (CRM, eCommerce, payroll, banks, carriers), user roles and permissions.
• Build in phases. Usually finance and inventory first, then purchasing, production or projects, then reporting.
• Data migration. Cleaning and moving customers, items, open orders and balances from the old system.
• Testing and training. User acceptance testing with your own staff, plus role-based training material.
• Go-live and support. A hypercare period after launch, then an agreed support and maintenance plan.

If one quote is half the price of the others, check which of these it leaves out. Data migration and training are the two items most often missing.

Custom ERP development company vs ERP implementation partner

These two get mixed up in search results, but they sell different things. An ERP implementation partner configures an existing product such as NetSuite, Dynamics 365, Odoo or Zoho. They set up the modules, migrate data and train users, but the core software belongs to the vendor. A custom ERP development company writes the system itself, so you get software shaped around your process, and you take on more responsibility for it.

Some firms do both, which is useful if you are not sure yet. Our own team works as an Odoo implementation partner and also builds custom modules, so the build or configure question gets an honest answer rather than a sales one. If Zoho is on your shortlist, our guide to Zoho ERP for SMBs covers what it handles out of the box.

8 things to check before you shortlist a custom ERP development company

Questions to ask a custom ERP development company on the first call

You will learn more from how a vendor answers these than from their slide deck:

1. Which part of our process would you not customise, and why?
2. Can you show us an ERP screen you built where the client’s workflow drove the design?
3. Who exactly will be on our project, and how many other projects are they on?
4. How do you handle a change request in the middle of a phase? What does it cost?
5. What did your last ERP project get wrong, and what did you change afterwards?
6. What happens to our code and data if we stop working with you?
7. What will it cost per year to keep this system running after go-live?

Question 5 is the most useful one. Every team that has shipped ERP has a story about a migration that ran long or a module that users ignored. A vendor with no answer either has not done much ERP work or is not being straight with you.

How pricing and engagement models work

Custom ERP projects are usually priced in one of three ways:

• Fixed price per phase. Good for well-defined phases after discovery. Expect the vendor to add a buffer for risk.
• Time and materials. You pay for hours used. Flexible, but needs a strong product owner on your side to control scope.
• Dedicated team. A monthly fee for a set team. Common for long programmes and for ongoing improvement after launch.

Where the team sits changes the rate a lot. For context, the US Bureau of Labor Statistics puts the median annual wage for US software developers at $135,980 (May 2025), before benefits and overhead. That is why many US companies use a blended model: a US-based lead and analyst for discovery and stakeholder work, with a larger delivery team offshore or nearshore for build and testing.

Whatever the model, insist on a short paid discovery phase before a fixed quote for the build. A vendor who quotes a full ERP from a one-hour call is guessing, and you will pay for the guess later through change requests.

Why ERP budgets slip, and how a good vendor protects you

Overruns are common in ERP work, and they are rarely a sign that you picked a bad ERP. If you are still deciding whether your business is ready for one, start with why a growing business needs an ERP system. In Panorama Consulting’s 2024 ERP Report, 33% of projects went over their expected budget, and the median project cost was about US$450,000. The most cited causes were extra technology requirements found mid-project (51%), underestimated staffing or organisational issues (39%), underestimated consulting fees (33%) and scope growth (26%).

Most of those are planning problems, not coding problems. When you compare vendors, look for the ones who:

• Run a proper integration inventory in discovery, so “extra technology” does not appear in month six
• Tell you how much of your own staff time the project will need, by role and by phase
• Price data migration and training as separate line items
• Build a contingency into the plan and explain it, rather than hiding it in day rates

Red flags when hiring a custom ERP development company

• A fixed price for the whole ERP before any discovery work
• No mention of data migration, training or support in the proposal
• Reluctance to put code ownership in the contract
• The senior people on the sales call disappear once the contract is signed
• References they cannot or will not share, even under NDA
• Pushing a single platform for every client, whatever the fit

A simple scorecard for your shortlist

Score each custom ERP development company from 1 to 5 on each line, multiply by the weight, and compare totals. Adjust the weights to your situation; a regulated business might raise security to 20%.

Notice that price is only 10%. The cheapest build is often the most expensive system to own, once rework and support are added in.

How we approach custom ERP at Ashapura Softech

We are a US software company based in Irving, Texas, and a certified Salesforce and Odoo partner. That matters for ERP buyers in one specific way: we do not have to push you toward a full custom build. If Odoo or Zoho covers most of your process, we will say so and build only the modules that are unique to you. If your workflow genuinely needs a custom system, we start with a paid discovery phase, give you the source code and documentation, and agree a support plan before go-live.

If you are weighing up vendors now, we are happy to do a free 30-minute scoping call. Bring your current process and the systems you need connected, and you will leave with a clearer view of build versus configure, whether or not you work with us. Book a call here.

Frequently asked questions

What does a custom ERP development company do?

It designs and builds an ERP system around your own processes instead of configuring a packaged product. A full engagement covers discovery, solution design, phased development, data migration, testing, training and support after go-live.

How long does it take to build a custom ERP?

For a mid-sized US business, a first release covering finance and inventory usually takes four to nine months, including discovery, migration and testing. Larger programmes with production, projects and multiple entities often run twelve months or more, delivered in phases.

Is custom ERP cheaper than NetSuite or Dynamics in the long run?

Sometimes. Custom ERP costs more upfront but has no per-user licence fees, so it can cost less over five to ten years for companies with many users. It also comes with ongoing maintenance costs that you own. Compare total cost over at least three years, not just the build quote.

Should I hire a local US company or an offshore team?

Many buyers use a mix: a US-based lead for discovery, decisions and stakeholder meetings, with a larger offshore or nearshore team for build and testing. What matters most is a fixed overlap in working hours and a single accountable contact.

Who should own the source code?

You should. Make sure the contract transfers ownership of the source code, database schema and documentation to your company, and that you have access to the code repository throughout the project.

Can a custom ERP connect to Salesforce or Zoho CRM?

Yes. Most custom ERP projects include a CRM integration so that quotes, orders, customer records and invoices stay in sync. Ask each vendor for an example of a CRM to ERP integration they have built and how they handle sync errors.

About the author: Ankur Pandey is Marketing Manager at Ashapura Softech, where he works with the delivery team on Salesforce, Zoho, Odoo and custom ERP projects for US businesses. He writes about how mid-market companies choose and roll out business software.

Ashapura Softech has built Salesforce to Zoho Migration, a platform that moves a complete Salesforce org into Zoho CRM: the structure, the users and the data. It is made for companies already using Salesforce that want to move to Zoho CRM without losing records, links or owners on the way.

You can run it yourself from one workspace, or have our team run it with you. This post shows what the product does and how it works.

What Salesforce to Zoho Migration does

Who it is for

Salesforce to Zoho Migration is for companies that are already using Salesforce and want to move to Zoho CRM. If your team works in Salesforce today, the platform takes everything you have built there, your objects, fields, users and records, and sets it up in Zoho CRM so your team can carry on working in Zoho without starting from scratch.

How Salesforce to Zoho Migration works: three simple stages

You connect your Salesforce org and your Zoho CRM org in one workspace. The platform then guides you through three stages, in order.

Key features of Salesforce to Zoho Migration

Beyond the three stages, these features keep the migration safe, predictable and within your Zoho API budget.

Use it yourself or with our team

You can run Salesforce to Zoho Migration on your own or with Ashapura Softech, whichever suits your team.

See the features, screenshots and a free demo form on the Salesforce to Zoho Migration product page.

Frequently asked questions

Quick answers to the questions Salesforce users ask most before moving to Zoho CRM.

Related reading

More guides from our team on moving to Zoho CRM.

Need a fixed-scope estimate for your team? Book a free 30-minute consultation with our Zoho team.

Zoho CRM implementation cost is the question most US buyers ask after they see the licence price, because the licence is rarely the biggest number. This guide covers what a Zoho CRM rollout actually costs in 2026, how long each phase takes, and which decisions move the budget. It is written for owners, sales leaders and operations managers at small and mid-size US businesses who are comparing a do-it-yourself setup with hiring a Zoho partner.

All licence prices below are Zoho’s published US list prices, and all service ranges come from published partner and pricing research, linked in the sources section. We have not invented a single “average”, because there is no honest average across a 5-user team and a 200-user one.

What you are actually paying for

A Zoho CRM project has two separate bills, and most budgets go wrong because they only plan for the first one.

1. Licences (recurring). You pay Zoho per user, per month, for the edition you choose. This is predictable and easy to model.

2. Implementation services (mostly one-time). Somebody has to design the pipeline, configure modules and fields, move your data, connect your other tools, and train your team. That is either your own staff’s time, a partner’s fees, or a mix of both.

A third, smaller bill comes after go-live: ongoing admin, change requests and support. Plan for it now, because a CRM that nobody maintains decays within a year.

Already on Salesforce? Our Salesforce to Zoho Migration platform moves your existing Salesforce structure, users and data into Zoho CRM in three guided stages, with a forecast of the Zoho API credits the move will need.

Zoho CRM licence cost in 2026

Zoho lists five Zoho CRM editions. Annual billing is noticeably cheaper than paying month to month.

Some quick arithmetic shows why the edition choice matters more than people expect:

• 10 users on Professional, billed annually: 10 × $23 × 12 = $2,760 a year.
• The same 10 users billed monthly: 10 × $35 × 12 = $4,200 a year.
• 25 users on Enterprise, billed annually: 25 × $40 × 12 = $12,000 a year.

Prices exclude sales tax, and Zoho can change list prices, so confirm the current figure on Zoho’s pricing page before you sign. If you already use several Zoho apps, also price Zoho One or CRM Plus, because a bundle can cost less than separate CRM plus helpdesk plus marketing licences.

Zoho CRM implementation cost by approach

There are three common ways to implement Zoho CRM. The ranges below are drawn from published 2025 and 2026 partner research for US projects.

For small US businesses with 5 to 20 users, published partner pricing puts a standard professional rollout at roughly $3,000 to $7,000. US Zoho consultants commonly bill $150 to $250 an hour, so a fixed-scope quote is usually easier to compare than an hourly estimate.

The do-it-yourself route looks cheapest on paper, but it is not free. The hours come out of a sales manager’s or an operations lead’s week, and a rushed self-build is the most common reason companies pay a partner later to redo the setup.

Zoho CRM implementation timeline, phase by phase

Every serious Zoho rollout goes through the same phases. They overlap, so the total is shorter than the sum of the column.

In practice this gives three realistic timelines:

• Simple, single-app setup with clean data: 3 to 6 weeks.
• Mid-size rollout (roughly 30 to 100 users) with migration and integrations: 2 to 4 months.
• Enterprise or multi-app rollout with custom development: 4 to 6 months, and up to 9 months when several Zoho apps go live together.

The five things that move your budget

1. The state of your data

Migration is where estimates break. Duplicate contacts, free-text fields that should be picklists, and spreadsheets with no consistent owner field all have to be fixed before import, not after. If you are coming from another CRM, read our guide on preparing Salesforce data for a Zoho CRM migration, because the same cleanup rules apply to most source systems.

2. How many systems need to connect

Each integration adds design, build and testing time. Native connectors such as Zoho Books or Google Workspace are quick. A two-way sync with an ERP, an ecommerce store or a custom database is a project in its own right. Our Zoho integration readiness checklist helps you count what you really need before you request quotes.

3. Customisation versus configuration

Configuration (fields, layouts, workflows, blueprints) is fast and cheap to change later. Custom code is slower and has to be maintained. A good rule is to configure first and only write Deluge or build widgets where configuration genuinely cannot do the job.

4. The edition you choose

Some limits, such as the number of custom modules, workflow rules or blueprint transitions, differ by edition. Choosing an edition that is too low forces workarounds that cost more in services than the licence upgrade would have.

5. Adoption and training

A CRM nobody updates is the most expensive outcome of all. Budget time for role-based training and for a named internal owner who keeps the system tidy after the partner leaves.

Worked example: a 15-user US sales team

To make the numbers concrete, here is a planning example built only from the published ranges above. It is an illustration, not a quote.

From year two, the cash cost drops to the licences plus whatever ongoing admin support you choose.

Costs that continue after go-live

Implementation is mostly a one-time cost, but a healthy CRM needs some ongoing spend. Budget for these lines from the start so year two does not come as a surprise:

• Admin time. Someone has to add fields, fix reports, manage users and answer “why can’t I see this record” questions. In a small team this is a few hours a week from an internal owner. In a larger one it is a part-time or full-time admin.
• Change requests. New products, a new sales team or a new approval step all mean configuration work. Many US businesses keep a small monthly support retainer with their partner for this.
• Add-ons and extra apps. Extra storage, telephony, advanced analytics or additional Zoho apps are billed separately. If you expect to use several Zoho apps, compare the cost of Zoho One or CRM Plus against separate licences before you renew.
• Edition upgrades. Teams often outgrow Standard within a year once they want blueprints, more automation or inventory. Price the next edition up now so the jump is planned rather than forced.

Questions to ask before you sign a Zoho implementation quote

Two quotes for the “same” Zoho CRM project can differ by 3 times, usually because they assume different scope. These questions expose the difference quickly:

If a partner cannot answer these in writing, the quote is not comparable to the others yet, however low it looks.

How to keep a Zoho CRM project on budget

• Write down the process before anyone opens Zoho. Stages, handoffs and required fields decided on paper cost nothing to change.
• Clean data before migration, not after. Deduplicate and standardise in the source system or in a spreadsheet first.
• Launch in phases. Get the sales pipeline live first, then add quotes, service or marketing modules.
• Ask for a fixed-scope quote with a change process. It is far easier to compare partners on scope than on hourly rates.
• Name an internal CRM owner. One person accountable for fields, reports and user requests keeps the system usable.

If your project includes a move from another platform, see our Zoho migration guide and how to choose the right Zoho migration partner. For a quick view of what Zoho CRM does well for small teams, read the benefits of Zoho CRM development for US small businesses.

Zoho CRM implementation cost FAQs

How much does Zoho CRM implementation cost?

For most US small and mid-size businesses, implementation services cost $3,000 to $25,000, separate from licences. Small teams with clean data are at the low end. Projects with data migration, several integrations or custom code move toward the high end, and enterprise rollouts can pass $75,000.

How long does it take to implement Zoho CRM?

A simple setup with clean data can be live in 3 to 6 weeks. A mid-size rollout with migration and integrations usually takes 2 to 4 months. Enterprise and multi-app projects take 4 to 6 months or more.

Can I implement Zoho CRM myself?

Yes, if you have fewer than about 10 users, clean data and no integrations. Expect 60 to 100 hours of internal time. Most teams bring in a partner for data migration and integrations even when they do the basic configuration themselves.

Is Zoho CRM cheaper than Salesforce to implement?

Usually, yes. Zoho’s licences are lower and its configuration tools are simpler, so comparable projects tend to need fewer services hours. The gap narrows when either platform needs heavy custom development or complex integrations.

What is the biggest hidden cost in a Zoho CRM project?

Data cleanup and migration. Duplicate and inconsistent records take longer to fix than most teams expect, and importing them unchanged undermines reporting from day one.

Does Zoho charge a setup fee?

Zoho does not charge a separate setup fee for Zoho CRM licences. Implementation costs come from your own staff time or from the partner you hire.

Sources

• Zoho CRM pricing and editions, Zoho
• Zoho CRM pricing explained, 2026, Automation Atlas (USD list prices re-checked June 2026)
• Zoho CRM implementation guide, Elsner (updated 25 September 2026)
• Zoho implementation timeline, CodeStringers (27 June 2026)
• Zoho One implementation cost, India and USA, Codroid IT Labs
• Zoho CRM hidden costs 2026, CostBench

Ashapura Softech is a certified Zoho, Salesforce and Odoo implementation partner working with US businesses. If you want a fixed-scope estimate for your rollout, see our Zoho CRM implementation and development services, or start with a free CRM health check template to see where your current setup stands.

This post covers what Salesforce documents about the conversion, what you should still plan to do by hand, and a cautious way to approach it. Where Salesforce has not published a detail, we say so. Use it as a planning guide for any Einstein Bots to Agentforce project.

Einstein Bots to Agentforce: what Salesforce actually announced

The announcement page says you can click Upgrade Agent on Agentforce Labs to convert an existing Einstein Bot into an Agentforce Service Agent or Help Agent. The Help documentation adds that the current bot keeps running while you review and adjust the new agent.

That last point matters. This is not a switch that flips your live bot off. The documented behavior is that the tool creates a separate agent, so the original bot stays available.

One status detail to watch

The Dreamforce page lists the feature as GA. However, the Salesforce Help article we opened, Create AI Agents From Einstein Bots (Beta), still labels the Upgrade Agent tool as a beta service governed by Beta Services Terms. Documentation often lags announcements, but we could not confirm which label is current for your org. Check the Help article and your release notes before you plan around either one.

Why this is happening: Einstein Bots is in Maintenance Mode

Salesforce Help states: “Starting August 17, 2026, Einstein Bots is in Maintenance Mode. Existing Einstein Bots continue to be supported and can be used after August 17, 2026. However, no new features or enhancements will be added, and we recommend using Agentforce for new AI agent implementations.” You can read it in the Create an Einstein Bot article.

In plain terms: your existing bots are supported and keep working, but they will not get new capabilities. We did not find an official end-of-life date in the pages we opened, so do not assume one exists or does not exist. Salesforce’s direction is clearly toward Agentforce, and that is the real reason to start planning.

What converts when you upgrade a bot to Agentforce

According to the Help documentation, in an Einstein Bots to Agentforce conversion the Upgrade Agent tool analyzes your bot configuration and generates matching Agentforce Service Agent components:

• Dialogs become subagents, based on grouped dialogs with similar intents.
• Action steps become agent actions.
• Intents are carried into the new agent structure.

A second Help article, Upgrade Einstein Bot to Agentforce Service Agent, describes the input more broadly as bot dialogs, intents, dialog steps, variables, entities and training data. Treat that as the scope the tool reads from, not a promise that every element comes across intact.

The first three rows of this Einstein Bots to Agentforce mapping come from Salesforce Help. The last row is our planning advice, not a Salesforce statement.

What does not convert, or is unclear

This is where you need to be careful. The Help article we reviewed does not list what fails to convert or any limitations, so treat the list of exclusions as unknown until you test a conversion yourself. Salesforce tells you to review and configure the new agent while the old bot stays live, so plan to test thoroughly before you switch any traffic.

Some community writers are more specific. The Concret migration guide argues that dialog trees, NLU training data and named conversation variables have no direct Agentforce equivalent, while Flows, Apex classes and external integrations can usually be reused with minor updates. A second community article makes a similar case. These are author opinions, not Salesforce statements, so use them as a prompt for your own review rather than as fact.

The practical lesson for Einstein Bots to Agentforce projects is the same either way: expect the conversion to give you a draft, not a finished agent.

Prerequisites for converting Einstein Bots to Agentforce

For Einstein Bots to Agentforce conversions, the Salesforce Help pages above list:

• Editions: Enterprise, Performance, Unlimited, or Developer Edition with Foundations or Agentforce 1 Editions. Enhanced Messaging channels have their own edition requirements.
• Interface: Lightning Experience.
• An existing Einstein Bot in a connected org, production or sandbox.
• Bot permissions: Customize Application, or Modify Metadata, or Manage Bots.
• Agent permissions: Manage Agentforce Service Agents and Manage AI Agents, plus Agentforce Default Admin or Customize Application.

The Help article describes two ways to run the conversion: the Agentforce Labs web tool, or a Claude Code route that uses Salesforce CLI (version 2.0.0 or later) and Salesforce’s published skills. With the web tool, a production org is added automatically, while a sandbox must be connected manually. You can also upload a bot package.

The pages we opened did not mention Data 360 (formerly Data Cloud) requirements for the conversion itself, so confirm this with your Salesforce account team rather than assuming either way.

What the Agentforce agent may cost

Salesforce does not appear to publish a price for the conversion tool itself. The cost question is about running the agent afterward. On its Agentforce pricing page, Salesforce lists Flex Credits at $500 per 100,000 credits, and also lists a per-conversation option at $2 per conversation. Prices and packaging change, so confirm current terms for your contract.

For any Einstein Bots to Agentforce plan, the key point for ops leaders is that usage-based models behave differently from a bot you have run for years. Model your real monthly conversation volume before you commit. If you are weighing options more broadly, our comparison of Claudeforce vs Agentforce may help frame the trade-offs.

Einstein Bots to Agentforce: a safe migration approach

1. Inventory your Einstein Bots before you convert

List every active bot, its dialogs, the Flows and Apex it calls, the channels it serves and its monthly volume. Find the dialogs that carry most of the traffic.

2. Convert in a sandbox first

Run the tool against a sandbox copy, and treat the first Einstein Bots to Agentforce run as a rehearsal. Because the original bot stays live, you can inspect the generated agent in Agentforce Builder without touching customers.

3. Review the Einstein Bots to Agentforce draft line by line

Check the generated subagents, actions and instructions against what your bot really does. Look for anything that did not carry across, and rebuild it deliberately.

4. Test with real conversation examples

Use anonymized transcripts from your own history. Test edge cases, escalation to a human, and anything involving sensitive data.

5. Consider a hybrid handoff

You do not have to cut over all at once. Salesforce documents how to transfer conversations from an enhanced bot to an Agentforce Service Agent using an Omni-Channel flow with a Route Work action. A Salesforce developer blog describes using the bot as a front-line router that passes complex inquiries to specialized agents. That lets you move one topic at a time.

6. Activate gradually

Turn the new agent on for one channel or one topic first, watch the results, and keep the old bot available until you are confident.

Release timing also matters. If you are lining up changes with your release calendar, see our notes on the Salesforce Winter ’27 release.

Einstein Bots to Agentforce pre-migration checklist

• Confirm your edition includes Foundations or Agentforce 1.
• Confirm the required bot and agent permissions are assigned.
• Document each bot’s dialogs, Flows, Apex and channels.
• Pull monthly conversation volume and escalation rates.
• Check the current status (beta or GA) of the Upgrade Agent tool.
• Ask Salesforce about Data Cloud and pricing for your contract.
• Pick one low-risk, high-volume topic to start with.
• Run the first conversion in a sandbox.
• Define human escalation and test it.
• Decide who signs off before activation.

Einstein Bots to Agentforce: frequently asked questions

Does the conversion replace my live bot?

No. Salesforce says the tool creates the new agent separately, so your existing bot remains available while you review and configure the new agent. Plan to test the new agent before you route any live traffic to it.

Is Einstein Bots being shut down?

Not according to the pages we opened. Salesforce says Einstein Bots entered Maintenance Mode on August 17, 2026: existing bots remain supported, but no new features or enhancements are coming. We found no official end-of-life date.

What do I need before I can convert a bot?

You need an Enterprise, Performance, Unlimited or Developer Edition org with Foundations or Agentforce 1, Lightning Experience, an existing bot, and the bot and agent permissions listed above.

Will everything in my bot carry over?

Do not assume so. Dialogs, action steps and intents are converted, but Salesforce’s Help article does not list what is left out, so we could not confirm exclusions. Plan to review and rebuild some pieces manually.

How much will the new agent cost?

The conversion tool’s cost is not stated in the sources we opened. Running the agent is priced separately; Salesforce lists Flex Credits at $500 per 100,000 credits and a $2 per conversation option. Confirm current pricing for your contract.

Getting help with the move

Einstein Bots to Agentforce conversion is the easy part. Deciding what the agent should do, how it hands off to people, and what it will cost to run takes planning. If you want a second set of eyes, Ashapura Softech can help through our Salesforce Agentforce consulting services, and you can contact us to talk it through. If you are still choosing a partner, our Agentforce implementation partner guide explains what to look for.

This guide lists the 15 Salesforce Winter ’27 release changes we think Salesforce admins, architects and IT leads should actually test, in order of risk. It is written for teams running a live production org who want to know what to check before their instance upgrades, not for people who want to read every line of the release notes. For each item you will find what changed, who it affects and the specific test to run.

We work on Salesforce orgs every week as an implementation partner, so the list leans towards what tends to break in real orgs rather than what looks best in a keynote.

Related: Salesforce also had a major outage on 16 September 2026. See what happened in the Salesforce outage and what admins should check.

Salesforce Winter ’27 release dates at a glance

Running an Einstein Bot? Read our guide to converting Einstein Bots to Agentforce agents, which Salesforce announced at Dreamforce 2026.

Salesforce rolls a major release out in waves, so your production org may upgrade on a different weekend from someone else’s. The dates below are the ones that matter for planning. Always confirm your own maintenance window on the Salesforce Trust status site for your instance.

Planning Agentforce? Start with our free Agentforce readiness checklist, or book a free 30-minute consultation.

How this Salesforce Winter ’27 release list is organised

The 15 Salesforce Winter ’27 release changes fall into three groups: five that can break things, five Flow and admin wins and five Agentforce updates. The first five can break something that works today, so they come first and deserve testing time before your upgrade weekend. The next five are Flow and admin improvements that are worth adopting because they save time or reduce risk. The last five are Agentforce and cloud updates that mostly affect planning and budgets rather than day to day stability.

If you only have one afternoon, test group one. If you have a week, work through all three.

Part 1: Five Salesforce Winter ’27 release changes that can break things

1. SOAP login() needs a new API permission

The Salesforce Winter ’27 release enforces a release update titled “Assign Use Any API Auth Permission for SOAP login()”. Users who authenticate through the SOAP API login() call now need that permission assigned, either through a profile or a permission set.

Who it affects: any integration user, middleware tool or older data loader setup that still logs in through SOAP rather than OAuth. These are often integrations nobody has looked at in years.

What to test: in your preview sandbox, list every integration user and check which ones authenticate through SOAP login(). Assign the permission through a permission set rather than editing profiles, then run each integration once end to end. Also note the bigger deadline behind this change: the SOAP login() call itself retires on June 1, 2027, so this is the moment to plan the move to OAuth rather than patching it twice.

2. Profile Filtering is switched on by default

With Profile Filtering enforced by the Salesforce Winter ’27 release, users without the View All Profiles permission can no longer see the names of profiles they are not assigned to. On its own this is a sensible security change. The problem is anything built on the assumption that profile names are visible.

Who it affects: flows, validation rules, formula fields, Apex and reports that read Profile.Name for users who do not hold View All Profiles, plus any custom user management screens.

What to test: search your metadata for references to Profile.Name, run the affected automation as a standard user in the sandbox and confirm it still behaves. Where logic depends on profile, consider switching it to a custom permission, which is the more durable pattern anyway.

3. The OAuth username-password flow is retired on February 20, 2027

This is the change most likely to cause a silent outage. Salesforce is retiring the OAuth 2.0 username-password flow for connected apps, where an integration sends a username, password and security token to get an access token. Enforcement is set for February 20, 2027. When it lands, those integrations simply stop getting tokens, and there is no warning screen for a user to notice.

Who it affects: existing orgs with server to server integrations still using grant_type=password. New orgs already have the flow blocked by default.

What to test: ask every integration owner which OAuth flow they use. Move nightly jobs and middleware to the client credentials flow running as a dedicated integration user, or to the JWT bearer flow for more sensitive connections. Store secrets in Named Credentials, not in code or config files. The Salesforce Winter ’27 release is the moment to do this, because February leaves little room once year end freezes are taken into account.

4. Standard-volume platform events retire in Summer ’27

You can no longer define new standard-volume custom platform events, and new platform events are high-volume by default. Existing standard-volume events are due to retire in Summer ’27, according to the Salesforce Platform Events Developer Guide.

Who it affects: orgs with older event-driven integrations, especially ones built several years ago when standard volume was the default.

What to test: list your custom platform events and check each one’s publish behaviour. For every standard-volume event, plan the migration to high-volume and retest the subscribers, including any Apex triggers, flows and external CometD clients. The migration is not hard, but it touches every subscriber, so it belongs in a planned release rather than a rushed fix.

5. Accessibility updates change layouts above 200% zoom

Three accessibility updates enforced by the Salesforce Winter ’27 release improve how cards, docked containers, menu lists, panels, date pickers, popovers, utility bars, record headers, page headers and modal windows behave at zoom levels above 200%.

Who it affects: most orgs will simply get a better experience. The risk sits with custom Lightning components and CSS overrides that assume a fixed layout.

What to test: open your most used record pages, custom components and utility bar items at 200% and 400% browser zoom in the sandbox. Look for clipped buttons, overlapping text and modals that cannot be closed. Fix those before users who rely on zoom run into them.

Part 2: Five Flow and admin changes in the Salesforce Winter ’27 release

6. Flow Test Mode (beta) replaces Debug Mode

In the Salesforce Winter ’27 release, Test Mode gives Flow Builder a dedicated place to test a flow, combining what debug and flow tests used to do separately. You can save test scenarios with mock inputs and assertions, rerun them after every change and track coverage.

Why it matters: most flow failures in production come from a change to one branch breaking another branch nobody retested. Saved, repeatable tests are the cheapest protection against that.

What to do: pick your three most important record-triggered flows and build saved tests for them in the sandbox. Because Test Mode is still beta, keep your existing testing process running alongside it for now.

7. Screen flows can run on many records at once

After the Salesforce Winter ’27 release, a screen flow can run as a mass quick action from a list view or a related list, receiving the selected records as a collection of IDs. Screen flow quick actions also get custom modal sizing.

Why it matters: bulk updates that used to need a data loader job, a custom Lightning component or a developer can now be built by an admin.

What to do: look for requests your team handles with spreadsheets and data loader, such as reassigning a batch of cases or updating stages on selected opportunities. Those are good first candidates.

8. Flow Builder catches more mistakes at save time

With the Salesforce Winter ’27 release, Flow Builder warns when a Create Records element is missing required field assignments and catches field length violations when you save, instead of failing at runtime. There is also a new run option that makes a flow respect the running user’s permissions, plus an edit history panel and better version comparison.

Why it matters: fewer broken flows reach production, and you can see who changed which element and restore an older version.

What to do: open your largest flows in the sandbox after the upgrade and fix any new warnings. Then review which flows run in system context by default and decide whether they should run in user context instead. For guidance on getting an org ready for automation at this level, our Agentforce readiness checklist covers the permission and data clean up that makes this safer.

9. Apex heap limits go up

The Salesforce Winter ’27 release raises the Apex heap size limit from 6MB to 10MB for synchronous transactions and from 12MB to 25MB for asynchronous transactions. Developers can also test External Services and HTTP callouts in Apex integration tests (developer preview), and a new Apex Symbol API (beta) exposes Apex type metadata.

Why it matters: heap limit errors are a common cause of failed batch jobs and integrations that process large payloads. Some of those will now simply work.

What to do: check your logs for recent heap limit exceptions. Rerun those jobs in the sandbox, but do not treat the higher limit as permission to skip optimisation. Code that barely fitted in 6MB will not stay comfortable for long.

10. Reports get record preview and a home on LWR sites

The Salesforce Winter ’27 release lets you preview records straight from Lightning reports without leaving the report (beta), and Lightning reports and dashboards can now be embedded in Lightning Web Runtime Experience Cloud sites (beta).

Why it matters: partners and customers on an LWR portal can finally see real reports and charts, and internal users lose fewer clicks moving between a report and the records behind it.

What to do: if you run a partner or customer portal, check which reports your external users currently receive by email or export. Those are candidates for embedding once the feature leaves beta.

Part 3: Five Agentforce updates in the Salesforce Winter ’27 release

11. Agent Skills and Plugins get a unified registry

Salesforce’s Winter ’27 announcement introduces a unified registry for Agent Skills and Plugins with more than 100 prebuilt skills. Developers can create reusable, governed capabilities that work across surfaces instead of rebuilding the same action for each agent.

Why it matters: the cost of an Agentforce rollout is often in building and maintaining actions. A shared, governed library changes that equation, and it follows the same direction as the seven Agentforce named agents announced in September.

What to plan: list the actions your agents use today and check which ones now exist as prebuilt skills. Retiring custom actions you no longer need is also a maintenance saving.

12. Custom Scorers (beta) for agent quality

The Salesforce Winter ’27 release adds Agentforce Custom Scorers in beta, letting you define your own evaluation logic for agent sessions on top of the built-in quality metrics.

Why it matters: a generic quality score cannot tell you whether an agent followed your refund policy or escalated at the right point. Custom scoring lets you measure the rules that matter to your business.

What to plan: write down three or four rules every agent conversation must follow, and turn those into scorers in a sandbox. This is also the evidence a steering committee will ask for before approving wider rollout.

13. Adaptive Experiences and Dynamic Plans in service

Adaptive Experiences and Dynamic Plans listen to service conversations in real time and generate and update a resolution plan as the issue evolves. Salesforce says four customers are live, including PowerSchool with more than 550 users.

Why it matters: this moves AI from summarising after the call to guiding the agent during it, which is where handle time actually drops.

What to plan: this depends heavily on clean case data and well structured knowledge. If your knowledge base is out of date, fix that first. For consumption-based costs, our explainer on Agentforce pricing and Flex Credits shows how usage is billed.

14. Agentforce Contact Center expands, with autonomous scheduling

In the Salesforce Winter ’27 release, Agentforce Contact Center expands to more than 30 countries, bringing voice, digital channels and CRM together. Autonomous scheduling with Agentforce Voice lets an agent check availability and book or dispatch technicians around the clock, turning a booking call that used to take around 15 minutes into seconds.

Why it matters: field service and appointment-heavy businesses get a practical use case with a clear return, rather than a general chatbot.

What to plan: map your current booking calls. If most follow the same pattern of checking availability and confirming a slot, they are good candidates. Check your edition too, because what is included changed with the new Salesforce Core, Advanced and Max editions.

15. Agentforce orchestrates third-party agents

With the Salesforce Winter ’27 release, Agentforce can orchestrate agents running on AWS, Azure and Google through A2A-compliant ecosystems. In other words, a Salesforce agent can hand work to an agent built elsewhere and receive the result back.

Why it matters: few large companies will run every agent on one platform. Orchestration across vendors is what keeps a multi-vendor setup from turning into disconnected bots.

What to plan: if you already run agents outside Salesforce, list them and the data each one needs. Governance, logging and permissions across vendors will need an owner before this goes live. If you are weighing Salesforce’s own agents against Claude inside Salesforce, our comparison of Claudeforce vs Agentforce covers the trade-offs.

Smaller Sales and Service changes in the Salesforce Winter ’27 release

A few smaller Salesforce Winter ’27 release updates will not break anything but are worth showing users. In Sales, Einstein Conversation Insights suggests follow-up actions after meetings, reps can capture voice notes after a meeting in the Salesforce mobile app, and Pipeline Forecasting shows deal risks, methodology scores and contact insights. In Service, agents can view original case attachments inline in case details, delete outdated milestones from the case timeline, and use a revamped Enhanced Case Merge interface (beta).

What was pulled from the Salesforce Winter ’27 release: Flow Tags

Flow Tags, which would have let admins label and group flows by category, was removed from the Winter ’27 release during the week of September 14, 2026. The release notes change log records the removal, and Salesforce said only that the feature is not quite ready yet.

The practical lesson is simple. Plan and budget on what is generally available, not on what appeared in a preview, a keynote or an early version of the release notes. Keep using naming conventions and descriptions to organise flows until Flow Tags returns.

Salesforce Winter ’27 release testing checklist

Every Salesforce Winter ’27 release test needs an owner: integration leads cover authentication, admins cover Flow and profiles, and developers cover Apex and platform events. The table maps each change to its test and usual owner.

How to run the Salesforce Winter ’27 release upgrade in your org

1. Confirm your date. Look up your production instance on Salesforce Trust status and put the maintenance window in the team calendar.
2. Test in a preview sandbox, not a pre-release org. Pre-release orgs have the new features but none of your configuration, so they cannot tell you what breaks.
3. Start with the release updates. Open Setup, then Release Updates, and work through anything marked for enforcement before touching new features.
4. Run your regression tests. Apex tests, key flows, integrations and the top ten record pages your users open every day.
5. Tell users what changes for them. A short note on the few visible changes saves a week of support tickets.
6. Book the follow-up work. The OAuth, SOAP and platform event deadlines fall in 2027, but the migrations need a slot in your plan now.

Teams without the capacity to test every release properly often hand this recurring work to Salesforce managed services.

Frequently asked questions about the Salesforce Winter ’27 release

When is the Salesforce Winter ’27 release date?

Salesforce announced general availability of the Salesforce Winter ’27 release on October 12, 2026. Production orgs upgrade in waves before that date, and the exact weekend depends on your instance, which you can check on Salesforce Trust status.

What breaks in Salesforce Winter ’27?

The Salesforce Winter ’27 release changes most likely to cause problems are the SOAP login() permission requirement, Profile Filtering being on by default and accessibility changes affecting custom components. Two later deadlines matter just as much: the OAuth username-password flow retires on February 20, 2027 and standard-volume platform events retire in Summer ’27.

Is Flow Test Mode generally available in Winter ’27?

No. Flow Test Mode is in beta in the Salesforce Winter ’27 release. It is safe to use in a sandbox for building saved flow tests, but keep your existing testing process alongside it until it reaches general availability.

Did Salesforce remove Flow Tags from Winter ’27?

Yes. Flow Tags was removed from the Salesforce Winter ’27 release in September 2026, with the change recorded in the release notes change log. Salesforce has not given a new date.

What should Salesforce admins test first in Winter ’27?

Test the enforced release updates first: SOAP login() authentication, Profile Filtering and the accessibility changes. Then check which integrations still use the OAuth username-password flow, because those will stop working on February 20, 2027.

Do Winter ’27 Agentforce features cost extra?

It depends on the feature and your edition. Check the availability section of each feature in the Salesforce Winter ’27 release notes before planning a rollout. Many Agentforce capabilities consume Flex Credits, and edition packaging changed in September 2026 with Core, Advanced and Max.

Getting help with the Salesforce Winter ’27 release

Ashapura Softech is a Salesforce implementation partner working with US businesses on Salesforce CRM development, Salesforce cloud services and CRM software development, and builds the custom middleware behind many Salesforce integrations through our enterprise software development team. If you want a second pair of eyes on your release updates, your integration authentication or an Agentforce rollout, we are happy to help, and you can see how we approach delivery in our Agentforce implementation partner guide.

Related: Agentforce Coworker is one of the three AIforce interfaces. If you are planning for the new agent registration and billing rules, read how Salesforce AIforce impacts your implementation.

Agentforce Coworker at a glance

Planning Agentforce? Start with our free Agentforce readiness checklist, or book a free 30-minute consultation.

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.

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.

Source: 21 Things We Announced at Dreamforce 2026 (Salesforce).

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 Sales Cloud, Service Cloud and the industry clouds (briefly branded Agentforce Sales, Agentforce Service and Agentforce 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.

Sources: 21 Things We Announced at Dreamforce 2026 (Salesforce) and Dreamforce 2026 news and media resources (Salesforce).