Agentforce Max replaces Agentforce 1 on Salesforce's central pricing page
Salesforce's main Agentforce pricing page now presents Agentforce Max Editions—not Agentforce 1—as the $550-per-user/month edition route. Max includes 2.75 million Flex Credits per org/year and is listed for Sales, Service, combined Sales/Service and Industries. Field Service and Operations remain named under the $125 Agentforce add-on but are no longer named under the edition route.
Max starting price
$550/user/monthsame published starting price as Agentforce 1Included pool
2.75m Flex Creditsper org per yearCredit increase
+250k10% above the former 2.5m public Agentforce 1 figureMax scope
Sales · Service · Sales/Service · Industriesproducts named on the central pricing pageEmployee add-on
$125/user/monthSales, Service, Field Service and OperationsIndustries add-on
$150/user/monthindustry-specific employee usageThe central purchasing page now aligns with Salesforce's September Max announcement and resolves the former 2.5-million-credit Agentforce 1 position. Client-facing packaging should use Max as the current public edition route, while Field Service and Operations proposals should not assume Max eligibility without an order-form or account-team confirmation.
Previous position
As verified on 12 September 2026, Salesforce's central Agentforce pricing page still showed Agentforce 1 Editions from $550 per user/month with 2.5 million Flex Credits per org/year and named Sales, Service, Field Service and Operations under that edition route. Separate Sales and Service pricing pages and Salesforce's 3 September announcement already described the successor Max editions with 2.75 million credits, leaving the central Agentforce buying page inconsistent.
New position
The central Agentforce pricing page now labels the route Agentforce Max Editions, keeps the published starting price at $550 per user/month and includes 2.75 million Flex Credits per org/year. It explicitly lists Max for Sales, Service, combined Sales/Service and Industries. Its separate $125 Agentforce add-on continues to list Sales, Service, Field Service and Operations, while the Max block does not name Field Service or Operations. Salesforce's 3 September announcement says existing Agentforce 1 customers can upgrade to Max at no extra cost, but the pricing page does not publish the contractual mechanics or effective date of that transition.
Who is affected
- Existing Agentforce 1 Edition customers preparing for renewal or an in-term move to Max
- New Sales, Service, combined Sales/Service and Industry Cloud proposals using the $550 edition route
- Field Service and Operations programmes that previously referenced Agentforce 1 as a public edition option
- Pricing handbooks, ROI models and architecture decks that still show Agentforce 1 or a 2.5-million-credit annual pool
- Multi-cloud organisations that need to understand whether one or several Max purchases create separate org-level credit allocations
Implications
- Agentforce 1 should now be treated as a legacy or transition label in client materials; Max is the current public edition route on Salesforce's primary Agentforce pricing page.
- The published Max pool is 250,000 credits, or 10%, larger than the former 2.5-million figure. At the public $500-per-100,000-credit rate, that difference has a directional list value of $1,250 before discounts.
- The $550 starting price is unchanged from the former Agentforce 1 route, consistent with Salesforce's statement that eligible existing Agentforce 1 customers can upgrade at no additional cost; this does not establish whether a renewal, SKU swap or amended order form is required.
- Combined Sales/Service is now explicitly named as a Max edition route on the central page, which can simplify a two-cloud packaging conversation but does not publish a separate combined-edition price there.
- Field Service and Operations remain eligible for the $125 Agentforce employee add-on, but their omission from the Max list means teams should not carry the former Agentforce 1 edition assumption into new proposals without confirmation.
- The included allocation is stated per org per year, not per licensed user. Consumption beyond the pool and separately metered Data 360, voice, Headless 360 or third-party services still need distinct modelling.