Excessive number of Agentforce topics
Why is this an issue?
Having too many or overlapping topics increases the probability that the agent will be inconsistent or inaccurate:
Routing confusion: The agent may struggle to select the correct topic
Overlapping scope: Similar topics compete for the same queries
Performance impact: More topics require more processing
Maintenance burden: Many topics are harder to keep updated
Examples
Example of incorrect design:
Agent with many topics with overlapping scope:
- Order Status
- Order Tracking
- Order History
- Order Modification
- Order Cancellation
- Returns
- Refunds
...
Example of correct design:
Agent with distinct topics with non-overlapping scope:
- Order Management (Actions for status, tracking, history, modification, and cancellation)
- Returns & Refunds
...
How can I fix violations?
Merge topics with overlapping scope.
Ensure each topic has distinct responsibilities.
Use actions to handle variations within a topic
Remove unneeded topics
When should I disable this rule?
You may dismiss specific violations for agents serving genuinely distinct use cases that require many specialized topics.
Resources