Which Agentforce SKU Are We On: Flex Credits Only, or Einstein Requests Plus Flex Credits?

Ask the AE which meter your prompts hit before you build the forecast. Salesforce's own usage post says it plainly: A1E/A4X customers consume only Flex Credits for all AI usage, while E1E/E4X customers on the split model have prompts consuming Einstein Requests instead of Flex Credits. If you are unsure which model applies to your org, check with your AE. Source: salesforce.com/blog/agentforce-usage-data-model.

That one sentence decides whether your RevOps model has one consumption line or two, whether Digital Wallet alone can close the month, and whether a Flex Credit forecast page is enough or you also need an Einstein Request true-up.

This is not the wait-or-buy question. It is not the Flex Credit overage forecast. It is not Digital Wallet's missing kill switch. It is the SKU identity question that sits underneath all three.

The two meter shapes, in buyer language

Shape A, Flex Credits only (A1E/A4X path). Prompts and actions that are metered land on Flex Credits. Salesforce's Agentforce usage data model post states A1E/A4X customers consume only Flex Credits for all AI usage. After the October 24, 2025 rate-card cutover, Agentforce 1 Edition and Agentforce for Sales, Service, or Industries add-ons no longer require Einstein Requests for those services and instead require Flex Credits outside unmetered employee AI usage. Source: Salesforce Help FAQ 005197697, publish date Sep 27, 2025: help.salesforce.com.

Shape B, split meters (E1E/E4X or legacy Foundations). Prompts still burn Einstein Requests. Actions burn Flex Credits. The same Help FAQ says customers on the pre-October 24, 2025 Salesforce Foundations entitlements Flex Credits version still consume both: Einstein Requests for generative AI usage, Flex Credits for Actions, and they do not consume Flex Credits for Prompts. Agentforce services that consume Conversations also still consume Einstein Requests for generative AI usage alongside Conversations. Same FAQ URL.

If your board slide shows one "AI spend" line and you are on Shape B, the slide is lying by omission.

What October 24, 2025 changed, and what it did not

Salesforce published the Einstein Request and Flex Credit rate card updates FAQ for changes effective October 24, 2025. For Agentforce 1 Edition and Agentforce Sales/Service/Industries add-ons, Einstein Request usage for those services discontinues and Flex Credits become the unified currency outside unmetered employee AI. Unused Einstein Requests can be swapped for Flex Credits through the AE. Data Cloud / Data Services credits remain a separate requirement. Source: Help FAQ 005197697.

What did not go away:

1. You still need to know which SKU you bought. A migration date is not a substitute for a contract line.
2. Conversations and some Einstein / Foundations paths still keep Einstein Requests in the stack.
3. Digital Wallet shows balances. It does not tell you which SKU path you are on if the AE never wrote it down.
4. Data 360 credits remain a third consumption surface Salesforce itself keeps calling out.

How this changes the RevOps forecast

Our Flex Credits forecast decoder covers overages that bill in arrears and Digital Wallet alerts that do not hard-stop: Flex Credits forecast.

Use that page for Shape A close. For Shape B, add a second close:

1. Name the prompt meter. Einstein Requests or Flex Credits Prompts. Get it in writing from the AE against the order form SKU codes (A1E, A4X, E1E, E4X, Foundations pre/post cutover, Conversations).
2. Name the action meter. Flex Credits Actions, with the published action rate on the Flex Credits rate card.
3. Name the Data 360 meter. Separate line. Salesforce's FAQ still requires Customer Data Cloud / Data Services credits.
4. Close each meter on its own owner. One person owns Digital Wallet Flex Credits. One person owns Einstein Request balance if Shape B. One person owns Data 360. Shared ownership is how the invoice surprises the forecast call.
5. Use Digital Wallet for billing verification. Salesforce says the usage DMO token counts are directional only, and Digital Wallet is the source of truth for exact Flex Credit consumption: usage data model.
6. Remember alerts are not a stop. The same Salesforce post: Digital Wallet does not block execution when credits run out. Overages bill at contracted rates. Tie that to the kill-switch decoder: Digital Wallet.

If you cannot answer "which meter do prompts hit" in one sentence with a SKU code, you do not have a forecast. You have a hope.

What to put in writing before the next AE call

1. Exact SKU codes on the order form (A1E, A4X, E1E, E4X, Foundations version date, Conversations, add-ons).
2. Which usage types burn which meter: Prompts, Actions, Conversations, Data 360.
3. Whether the org already migrated off Einstein Requests for Agentforce on or after October 24, 2025.
4. Whether unused Einstein Requests were swapped, and at what rate.
5. Named owners for each meter at month-end close.
6. Audit and parallel-count rights (sibling decoder): Who audits the meter.

Flex Credits vs Conversations is a different fork

Salesforce's public pricing page still frames Flex Credits versus Conversations as a buying-model choice: Flex Credits for flexibility across use cases, Conversations as flat pricing optimized for external customer agents, and the models do not mix in one org the way buyers expect a blended SKU. Source: salesforce.com/agentforce/pricing.

Do not collapse that fork into the A1E/E1E prompt-meter question. Conversations can still sit on top of Einstein Requests for generative usage per the Help FAQ. Two decisions. Two slides.

Related: Flex Credits forecast · Digital Wallet · Who audits the meter · Claudeforce two contracts