--- schema_version: "1" id: 73e5db212db80fe26454d215c6c19a7b76eb4cdd410e2ada098d7e7e788e7e6e title: Identify the Subagents and Actions collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ai/264-0-0/agent_plan_action_identify.md canonical_url: https://help.salesforce.com/s/articleView?id=ai.agent_plan_action_identify.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 20b9d0fbff17767e168e646c87b1fdd4d47826b28f278ae505481e110833054c description: After determining your agent’s use case and the work the agent will do, you can identify the right subagents and actions for the agent. Agents are made up of subagents, which define the different jobs an agent can do. Subagents also contain a set of actions, which are the tools the agent can use to do its job. products: - Agentforce - Cross Cloud release: "264" --- # Identify the Subagents and Actions After determining your agent’s use case and the work the agent will do, you can identify the right subagents and actions for the agent. Agents are made up of subagents, which define the different jobs an agent can do. Subagents also contain a set of actions, which are the tools the agent can use to do its job. ### Required Editions
Available in: Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions. Required add-on licenses vary by agent type.
When identifying the subagents and actions for your agent, there are two possible approaches: top-down and bottom-up. In the top-down approach, first identify the subagents, then define the relevant actions for those subagents. In the bottom-up approach, first list all of the individual actions for your agent, then group them into related subagents. Bottom-up Example: ## List the Actions To come up with ideas for agent actions, review the [business processes](https://help.salesforce.com/s/articleView?id=ai.agent_plan_map.htm&type=5&language=en_US) related to the work your AI agent will do, and then list all the tasks the agent should be able to perform. At this stage, it's better to be too specific rather than too general. Avoid trying to group or simplify actions prematurely. The goal is to create a comprehensive and granular view of what the agent can do. For example, in the case of a customer service agent, the initial list might include: - Answer general FAQs - Find customer orders - Look up items related to an order - Check order status - Check delivery status - Return an order - Exchange an order - Look up return and exchange policies - Check inventory availability - Check promotion availability - Troubleshoot technical problems - Find customer assets and warranties Note that an action like “Resolve customer complaints” is too broad because customers can have different types of complaints: problems with an order, technical issues, or delivery questions. Actions should represent the smallest level of granularity in agent behavior. ## Identify Overlapping or Similar Actions Flag actions that are too similar because they can cause confusion for the reasoning engine. If the actions aren’t different enough semantically, then the [reasoning engine](https://help.salesforce.com/s/articleView?id=ai.agent_reasoning_engine.htm&type=5&language=en_US) won’t know which action to select when a user asks a question or makes a request. For example, “Troubleshoot technical problems” and “Answer general FAQs” might have descriptions that are similar, but their functionality is different. Identifying semantic overlaps can help to determine which actions to separate over multiple subagents. ## Group Actions into Subagents After actions are clearly defined, they can be grouped into preliminary subagents. A subagent is a logical category of functionality—a grouping of actions that together represent a job, capability, or skill of the agent. Follow these guidelines: - Aim to use the minimum number of subagents necessary to avoid semantic overlap. - Make sure that each subagent contains actions that are meaningfully related. - If certain actions must be executed in a chain, include them in the same subagent. Here’s an example of the subagent and action groupings for a customer service agent: Subagent 1: Order Management - Find customer orders - Look up items related to an order - Check order status - Check delivery status - Check inventory availability Subagent 2: Troubleshooting - Troubleshoot technical problems - Find customer assets and warranties Subagent 3: Returns and Exchanges - Look up return and exchange policies - Return an order - Exchange an order Subagent 4: Product Support - Answer general FAQs - Check promotion availability ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-generative_ai-264-0-0-production-enus/f8ef6498-d7b2-44e3-9b34-ffd5a850aae9/images/icon_tip.png) Tip You can build your Agentforce subagents and actions from scratch, but there are also [templates](https://help.salesforce.com/s/articleView?id=ai.agent_setup_create.htm&type=5&language=en_US) you can use to get up and running quickly. Another fast way to build subagents and actions is to [create them using generative AI](https://help.salesforce.com/s/articleView?id=ai.copilot_create_gen_ai_agent.htm&type=5&language=en_US). #### See Also - [The Building Blocks of Agents](https://help.salesforce.com/s/articleView?id=ai.copilot_building_blocks.htm&release=264.0.0&type=5 "Get to know the key components of agents, including subagents and actions, data, connections and channels, and the reasoning engine.")