| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions. Required add-on licenses vary by agent type. |
| Use Cases | How Agentforce Can Help |
|---|---|
| Add new capabilities to your agent |
You don't have to be an Agent Script developer to build out an agent. Describe what you want in plain language. For example, ask Optimizer to add a subagent that looks up order details and requires user verification. Agentforce handles the rest. Optimizer searches for relevant actions in your org and asset library, creates any subagents, and updates the Agent Router. If it can't find an existing action that fits your use case, it creates a placeholder with the metadata your agent needs and flags it for you to finish. When it's done, it explains what it plans to change and why, and it simulates the change to confirm that it works as expected. You can accept or decline before anything is applied. |
| Refine or restrict your agent's behavior |
Whether you're fine-tuning after an initial rollout or enforcing compliance guardrails, ask Optimizer to update routing conditions and access rules without rebuilding Agent Script from scratch. For example, restrict a refund subagent to customers with a "delivered" order status, or limit escalation to customers above a certain entitlement tier. Optimizer proposes targeted adjustments and validates them in preview to identify and fix any downstream issues before you apply them. |
| Troubleshoot unexpected agent behavior |
When your agent behaves unexpectedly in testing or production, describe what it's doing instead of what you want, or ask Optimizer to explain a specific error. You can also use it to fix Agent Script validation issues flagged on save or in the console. If you’re testing your agent’s behavior in a preview conversation, click Ask Optimizer in the Interaction Summary panel to add the conversation to Optimizer's context, and then send a message. Optimizer surfaces likely root causes, such as missing instructions, ambiguous subagent routing, or empty variables. It proposes and validates targeted fixes for you to review, so you don’t have to manually review your agent’s full script. |
| Test your agent conversationally, and fix what you find |
Ask Optimizer to run a quick health check on a specific subagent or conversation path. You can ask it to test against different personas (for example, "test this as a frustrated customer"), variations in user inputs, or edge cases. Describe the scenarios that you want to validate, such as whether a returns subagent handles requests correctly or an order lookup routes as expected. Optimizer generates representative test conversations, simulates them concurrently in preview, and summarizes what it finds, including any latency, routing issues, or gaps. Then you can then ask it to fix what it found. Instead of a generic rewrite, it proposes targeted fixes and then re-runs the tests to confirm that the fixes worked. |
| Validate and optimize your agent after upgrading from the legacy builder |
When you migrate or upgrade an existing agent, you can use Agentforce or third-party AI coding tools to do most of the work. But metadata and syntax differences between the legacy and new builder can still cause initial validation errors. Use Optimizer to resolve those errors without memorizing Agent Script syntax. You can also ask Optimizer to optimize your agent's script to improve quality and follow Agent Script best practices, so you get the most from your new agent. It reviews your natural language instructions, suggests improvements, and adds deterministic controls to improve reliability and performance. |