Salesforce’s November 4, 2026 Agentforce Coworker announcement introduces a $50-per-user, per-month option. Its billing documentation adds a distinction worth checking before assigning seats: access to Coworker, work delegated to another agent, and data indexing can follow different billing rules. A seat subtotal is a starting point for a budget, not the complete calculation.

Three separate stacks represent user seats, indexed files and delegated tasks.
Three separate stacks represent user seats, indexed files and delegated tasks.

Identify which license each person uses

Salesforce says seat-based and usage-based pricing can coexist in one organization, with billing following the user’s license and setup. Its guide describes Coworker for Enterprise or Unlimited Edition licenses as unmetered Coworker access, with 30 MB per user per month of pooled unstructured-data ingestion and indexing. Confirm the exact license and edition before applying those terms to your users.

Separate a draft from a delegated action

The guide gives an email example: drafting is included with a seat-based license, while sending through a delegated Agentforce agent bills under that other agent’s terms. The same request can therefore involve more than one billing path. During an evaluation, record what the user asked, which agent performed each step, and which license or credit rule applied.

Build a seat-and-indexing subtotal

For a fictional team buying 20 eligible seats at the announced $50 rate, the monthly seat subtotal is $1,000. At 30 MB per user, the pooled monthly indexing allowance would be 600 MB. If the team ingests and indexes 720 MB under the applicable rule, 120 MB falls beyond that allowance and can consume credits.

If the next month uses 400 MB, 200 MB of that month’s allowance remains unused. Salesforce says unused allowance does not roll over. These invented volumes illustrate the documented allowance; they are not a customer bill or a quote for the excess usage. The $1,000 subtotal also excludes other licenses, delegated-agent charges and any additional consumption.

Check a small workload before expanding

Choose a representative task and trace its billing categories with your administrator. Include a simple query, a task that delegates an action, and a controlled indexing batch. Reconcile the recorded consumption with the contract terms before estimating a larger rollout. Seat pricing and per-action pricing measure different things, so dividing one headline price by another does not establish that the offerings are interchangeable.

When checking actual AI charges, use the provider-bill reconciliation guide to keep billed amounts, usage records and unexplained differences separate.

Keep the seat count, license mix, indexing volume and delegated work in separate budget lines. No Salesforce environment, billing dashboard or agent workflow was tested for this article.

Check the budget

Sources

Salesforce’s November 4 Coworker announcement

Agentforce Coworker billing considerations

Salesforce Agentforce pricing