Audience: Salesforce Partners choosing what to include in a customer estimate.
Learn which products you can estimate in the Flex Credit Pricing Calculator: Agentforce. This article covers how the Solution Categories lead to Agentforce, and how a Solution turns the customer's problem into an estimate during the Solutions step.
Start here. Solutions is the first step, and every figure the later steps produce depends on what you add. This article covers the Solution categories, finding a Solution, the business questions a Solution asks, adding Subagents to an agent Solution, and building your own when nothing fits.
A Solution is a pre-built starting point for a customer need. You begin from the problem the customer wants to solve — improving customer service, unifying customer data — and the Solution arrives with whatever addresses that problem already brought together for you.
Which products it brings depends on the problem it solves, so Solutions differ from one another in what they contain. What they have in common is how you size them: each one asks you a set of business questions about the customer's situation, and your answers are what turn the Solution into an estimate. You describe how the customer operates, and the pricing follows from that.
That is the value of starting from a Solution. Picking the one that matches the customer's problem gives you a working starting point, and you adjust it from there. When a requirement matches no available Solution, you can still build what you need yourself.
Examples include Service Agent, Sales & Deals, and Employee Assistant Agent.
Subagents belong to Solutions that deliver an agent. There, a Subagent is a specific task the agent handles for the customer: the Solution arrives with a set of them in place, and you add or remove them from there. One you build yourself starts empty, so you add the first Subagent before there is anything to configure.
Where a Solution delivers something other than an agent, you size it through its business questions alone, and the card offers no Subagent action.
The product supported in the calculator at launch is Agentforce. You reach it by choosing the Solution Category that matches what the customer is trying to do:
Employee Facing for agents that serve your customer's employees.
Customer Facing for agents that serve your customer's own customers.
The audience is what changes how a solution is configured and priced, and it is the thing you already know about the customer's need at this stage.
Not yet. Sizing a product other than Agentforce is not yet supported in the calculator, so an estimate cannot cover it.
For anything outside that scope, use these two sources:
Product documentation: https://help.salesforce.com
Published pricing: https://www.salesforce.com/pricing/
Where part of the customer's need does fall to Agentforce, estimate that part here and take the rest to those sources.
The Solutions step opens on "Build your Solutions", where each Solution Category appears as a card with a short description of what it covers. Read the card description to decide which one fits.
Select Explore Solutions on the category card that matches the customer's need, or select Browse All Solutions to see every Solution regardless of category.
Search by name, or filter by Solution Category and Line of Business, then select the Solution you want. A badge marks the ones already added.
Configure the Solution's required fields. You must finish configuring the current Solution before adding another.
The categories available to you depend on your access, so you may not see all of them.
A Subagent is a specific task an agent Solution handles. There are two kinds — Standard and Custom — and they are added in different ways.
A Standard Subagent is picked from a list. Select Add Standard Subagents to open "Select Subagents from the List below", search or filter by Line of Business, Employee Facing, or Customer Facing, mark the ones that complement your Solution, and confirm.
Which options you see depends on the Solution. On a customer-facing agent Solution, Add Subagents opens a menu offering both Standard and Custom. On an employee-facing one, a single Add Standard Subagents button appears, because a Custom Subagent is a customer-facing option.
Select Add Custom Subagent on a customer-facing agent Solution. On "Create a Custom Subagent", type a name in "Name of Custom Subagent" and select Add Subagent. The name field enforces a minimum and maximum length, and tells you when the name does not fit.
Naming it is the whole creation step — there is no list of custom types to choose from. The Subagent then appears in the Solution's list like any other, and you configure it there by entering the volumes it will handle, such as how many actions it runs. Those figures are what give it a cost in the estimate.
Deleting a Subagent discards everything you entered on it, so the calculator asks you to confirm first.
Build your own. In the Add Solution screen, select Create your own Solution, then complete the Solution details: name it and choose the category it belongs to. Select Create New Solution to add it to the estimate, then configure it like any other Solution.
Use this for a requirement no pre-built Solution covers — a project role or a specialised technical service specific to that customer. Reach for a pre-built Solution first when one fits, since it arrives already configured. You can add Standard and/or Custom Subagents to Custom Solutions.
In the Add Solution screen you can search Solutions by name, and filter by Solution Category or by Line of Business. Clear the filters to widen the list again.
Yes. Select Exclude from Calculations on a Solution or on a Subagent. It stays in the estimate with everything you entered intact, and stops counting towards the totals. The same menu then offers Enable for Calculations to bring it back.
This is how you show a customer the effect of taking something out, and how you park a Solution the customer is undecided about, without rebuilding it later.
Both, from the menu on the item you want to change.
Clear values empties what you entered on a Subagent and keeps the Subagent in place, so you can re-enter figures from scratch.
Rename changes the name of a Solution, or of a Subagent you created, so the estimate reads in the customer's own wording.
A standard Subagent cannot be renamed or removed, because it comes with the Solution. Exclude it or clear its values instead.
The Solutions step blocks advancing while the current Solution has incomplete required fields. Complete the configuration, then select Next to continue to Consumption.
Example of adding a Solution: A partner is scoping an Agentforce agent that will answer a customer's own customers. They select Explore Solutions on the Customer Facing card and add the Solution. Then they open the Subagent panel and add a FAQ Subagent. After completing the required fields, the Next button enables and they advance to Consumption.
If no Solution seems to fit and you are unsure whether to build your own, open a support case in Partner Community. A pre-built Solution that nearly fits is usually the better starting point, so it is worth asking before building from scratch.
005459665

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.