Summary: Salesforce lists Flex Credits at $500 per 100,000 credits beside $2 conversations, with no rollover and no shared org. Microsoft sells Copilot Studio as 25,000-credit packs at $200.00 per pack per month and disables custom agents at 125 percent of prepaid capacity. When the billable unit changes mid contract, a 2027 volume forecast no longer matches the purchase order. Finance teams that budget for agent workflows have to lock the unit, the rollover rule, and the disable cliff before the next SKU swap.
Two Salesforce meters cannot share an org
On 15 May 2025, Salesforce introduced Flex Credits beside the conversation meter. The official pricing page still lists both units: Flex Credits at $500 per 100,000 credits, and Conversations at $2 per conversation. The same FAQ states that Flex Credits and Conversations will not be supported in the same org.
Unused Flex Credits do not roll over into subsequent subscription terms. A 2027 forecast that carries leftover credits into a later term is already off the list rule. A buyer on conversation pricing can move to Flex Credits, but only by swapping all existing Agentforce Conversation SKUs. The credit pack does not land as a silent overlay on a conversation-unit order. The page also prints an Agentforce User License at $5 USD per user per month that requires Flex Credits, a second unit on top of the credit meter.
An action is twenty credits until the next rate card
The official page meters Agentforce actions at 20 Flex Credits. The 15 May 2025 release and the worked examples price that action at $0.10. Voice actions are 30 Flex Credits. A two-action order-status path is already 40 credits, or $0.20 at the published action price.
The forecast breaks when procurement modeled conversations and production burns actions. It breaks again if the next rate card changes what counts as one action. After a Conversation SKU swap, that path is no longer one $2 conversation. It is 40 Flex Credits at the published action rate. Until the contract names the unit production consumes, the 2027 conversation count is attached to the wrong meter.
Microsoft’s prepaid cliff turns overage into downtime
Microsoft sells Copilot Studio as a tenant-wide license with Copilot Credit capacity packs of 25,000 Copilot Credits at $200.00 per pack per month. Those credits are pooled across the entire tenant. A departmental forecast cannot treat one pack as a private envelope.
Microsoft Learn states that enforcement is triggered when a tenant reaches 125 percent of prepaid capacity. Custom agents are disabled. An in-flight conversation can finish. Later invokes are rejected until capacity is increased or reset. End users can see “There is a billing issue.” or “This agent is currently unavailable. It has reached its usage limit.” Agent flow enforcement on that page targets flow execution only.
Pay-as-you-go is the documented interrupt-avoidance path when prepaid credits run out. A prepaid-only 2027 line that assumes the agent stays up through overage does not match the official cliff. The Copilot Studio pricing page does not state that unused monthly pack credits roll forward.
A stacked turn already costs more than one credit
Microsoft Learn bills a classic answer at 1 Copilot Credit, a generative answer at 2, an agent action at 5, and tenant graph grounding at 10. The same page says one interaction can use more than one feature at once. An agent grounded in a tenant graph can consume 12 Copilot Credits on a single prompt: 10 for tenant graph grounding and 2 for a generative answer. A finance model that multiplies monthly conversations by one credit, or that treats the $200.00 pack sticker as the unit cost of a turn, understates the first production month. That is why token economics for AI agents belong next to the purchase order.
Lock the unit, the rollover rule, the org rule, and the cliff before the next swap
Write the billable unit on the order form in the words the invoice will use. Write whether unused units roll into the next subscription term. Write whether two meters can share an org. Write the overage threshold and whether the agent disables or bills through. Write the SKU-swap process if the vendor adds another unit during the term, because Salesforce’s FAQ treats the move from Conversations to Flex Credits as a full Conversation SKU swap.
Vendor-side meter changes break forecasts the same way a mid-contract unit swap does. If the org is on Flex Credits, the 2027 number cannot still say conversations. If the tenant is on Copilot Credits, it cannot still say one credit per turn.
