Audience: Salesforce Partners configuring Flex Credit usage in a customer estimate.
Learn how to define a customer's first twelve-month Flex Credit burn rate in the Consumption step, including Production and Sandbox usage and the global Build and Launch Window.
Read this when you need to turn a customer's rollout plan into monthly credit figures. It covers Year 1 usage, shared versus per-Solution timing, editing individual months by hand, and Solutions that consume no credits at all.
The Consumption step defines the customer's initial twelve-month Flex Credit burn rate. Flex Credits are consumed as the customer uses Agentforce actions across environments, so this step sets the Year 1 baseline that later steps build on.
Each Solution's usage is split into two modes. Production is live usage after launch. Sandbox is usage during the build and trial period before launch. The calculator estimates monthly credits for both.
Global Solution Settings let you set one Build and Launch Window for every Solution at once. You define the Development Start and the Production Launch dates, and the calculator derives each month's usage from them. Months before launch count as Sandbox usage. Months after it ramp up to steady Production usage.
The window opens on a default position, so you only change it when the customer's timeline differs.
Yes. You can turn off Global Solution Settings for a single Solution and configure its own build and launch timing. Switching a Solution back to global settings discards its custom timeline and restores the shared window.
The consumption table shows both:
Estimated is the theoretical figure derived from how you configured the Solution.
Allocated is what the customer is expected to actually consume in Year 1.
Estimated tells you what the configuration implies. Allocated is the number the estimate is built on, and it is the one you adjust when the customer's real expectation differs from the theoretical figure.
Yes. Each month in the table is expressed as a percentage of a full steady month, where 100 percent means one full month of steady usage. Editing a month lets you model a slower start, a seasonal peak, or a phased rollout that the global window does not capture.
They are lost, and the calculator warns you first. Two prompts protect manual work:
Applying Solution settings over manual edits overwrites every value you entered by hand for that Solution.
Resetting a Solution, or resetting all Solutions, restores default values.
Both actions cannot be undone, so confirm only when you intend to discard the manual figures.
Some fields hold a value the system recommends based on the Solution configuration. When you change one, the calculator asks you to confirm and warns that you are overriding its recommended estimate. Keep the new value within a sensible range so you can meet customer expectations.
The Consumption step edits one Solution at a time. Select a Solution in the summary card to edit its consumption; until you do, the editor shows no selection.
That Solution is billed per seat only and does not consume Flex Credits. No Consumption setup is required; its seats are secured in the Solutions step.
The "Consumption Over Time" chart shows the monthly credit usage that results from your settings. Select legend items to view exact credit amounts by Solution and credit type.
Example of a build window: A partner sets a Development Start in January and a Production Launch in April. The calculator treats January through March as Sandbox usage and April onward as Production usage, then shows the monthly credits on the Consumption Over Time chart.
If the monthly figures do not behave the way this article describes, open a support case in Partner Community. What the customer's real usage will be is a question for the customer and your Partner Account Manager, not for support.
005459667

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.