Add a Subagent to Your Agent in the Legacy Builder
You can create a custom subagent from scratch or add a standard subagent from the asset
library. Consider best practices for creating a subagent as you decide. When you add a subagent
to an agent, Salesforce makes a copy of the subagent so that each agent and agent version has
its own independent copy.
When considering whether to create a custom subagent, a good rule of thumb is to start as
simply as possible. It’s easier to iteratively build, test, and repeat than it is to
troubleshoot many changes at once.
We recommend starting with a standard subagent for common use cases and editing it to meet the needs of your
business.
Before creating a subagent, review your existing subagents to avoid overlap. Ensure that
an existing subagent doesn’t already cover the same job or task. Consider whether it’s
possible to edit or expand an existing subagent to handle your use case.
If you determine that you need to create a subagent from scratch, focus on your most
common customer needs. The best candidates for your first custom subagent are high-volume
and relatively straightforward use cases.
Start with the fewest subagents necessary for the agent to perform as expected. Add
subagents one by one as you simulate user conversations for different use cases, and then
carefully test for regressions between each change.
If you find that you need two or more sets of instructions in a single subagent to handle
different jobs, consider splitting the subagent into multiple subagents.
If you find that two or more subagents frequently hand off to each other in a single
conversation or the subagents share nearly identical actions and instructions, consider
combining your subagents into a single subagent.
Add a Subagent from the Asset Library in the Legacy Builder With standard subagents, your agents can start handling common business use cases quickly. You can create subagents and actions that are tailored to your business needs. When you add these subagents and actions to an agent, the agent gets its own, independent copy. Changes to template subagents and actions within the Asset Library aren't automatically sync'd to subagents and actions within your agent. Changes made to one agent's subagents or actions don't affect another agent's subagents or actions.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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
Always Active
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
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
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.