Section 4 · AI Agents · 35% of exam
4.6 Standard and Custom Topics
Exam objective
Given a use case, select and configure standard or custom topics or subagents to route requests to focused agent capabilities.
Topics define the agent’s jobs
A topic groups a job the agent can handle with related instructions and actions. It helps the reasoning engine identify which area of the agent should respond to a user’s request. A topic should have a focused purpose and a clear boundary. If it covers too many unrelated jobs, routing and instructions can become difficult to understand. If the scope is too narrow, the agent may need unnecessary transitions. Topic classification details are important because the router compares the request and conversation context with the available topic or subagent descriptions. Standard and custom choices
Standard topics or subagents are Salesforce-provided starting points for common use cases. They can save setup time and include a known structure, but they may still need review and tailoring for a specific organization. A custom topic or subagent is designed around the organization’s unique process, language, or policy. In the current Asset Library, Salesforce explains that adding a standard or library-based subagent adds a copy to the agent. A custom subagent created in the Asset Library can be available to multiple agents and versions; one created inside an agent is limited to that agent. Use standard assets when they fit; build custom ones when the requirement differs. Write descriptions and scope for routing
A classification description should make it clear what kinds of user requests belong to the topic. Include meaningful signals and distinguish it from neighboring topics. Scope identifies the task boundaries or responsibilities. Instructions then explain how to perform the task, including information to gather, actions to use, constraints, and the expected response. Avoid vague descriptions such as ‘help with orders’ if the agent has separate order-status, cancellation, and return capabilities. Also avoid contradictory or duplicated instructions across topics. Test paraphrases, related requests, and out-of-scope prompts to ensure the router selects the intended topic. Current terminology and maintenance
Salesforce documentation states that, beginning in April 2026, topics are called subagents in the new Agentforce Builder, with no change in underlying functionality; legacy material may still use topic. The AI-201 exam guide continues to express this objective using standard and custom topics. Students should recognize both terms and use the surrounding UI context to understand the resource being discussed. Review an agent’s topic list periodically. Remove unused assets, clarify overlapping descriptions, and update instructions when business policies change. Make sure every subagent has only the actions needed for its job, and test routing again after a description or scope change.
TIP: If the agent selects the wrong topic, improve the classification description and clarify overlapping scopes before adding more actions.
The newer Builder uses ‘subagent’ terminology; the exam guide uses ‘topic’ in its objective. Learn the concept and recognize both labels.
Extra concept: A small number of focused topics with distinct responsibilities is easier to route and maintain than one broad catch-all topic.
Official references:
- Salesforce Certified Agentforce Specialist Exam Guide https://help.salesforce.com/s/articleView?id=005298924&language=en_US&type=1
- Subagent Classification and Routing https://help.salesforce.com/s/articleView?id=ai.agent_topics_routing.htm&language=en_US&type=5
- Manage Subagents https://help.salesforce.com/s/articleView?id=ai.agent_topics_manage.htm&language=en_US&type=5
Key takeaways
- Topics or subagents group related jobs and help route user requests.
- Use standard assets when they fit; create a focused custom topic when the business need is distinct.
- Descriptions, scope, instructions, and asset availability all affect routing quality.
