Generate prompt preset scenarios
Prompt presets allow you to create more targeted, business-specific scenarios without ever needing to edit your agentâs core description and functionality. This is super useful if you want to move beyond general testing and simulate how your agents handle specific personas and complex business logic.
Prompt presets are a powerful way to ensure your agent is prepared for real-world user situations and personas. They are:
- Fully customizable: Tailored to whatever kind of personas you envision and are important for your departments
- Rule-driven: Move from generic stress testing to rule-driven scenarios
- Higher quality: Get higher quality datasets that are more reliable for evaluations
- Business-focused: Ultimately, an agent that truly understands your business boundaries
By moving from generic stress testing to rule-driven scenarios, you get higher quality datasets that are more reliable for evaluations, and ultimately, an agent that truly understands your business boundaries.
Getting started
Section titled âGetting startedâTo begin, navigate to the Datasets page and click Generate in the upper-right corner of the screen. This opens the Pick your generation type modal with two options: Prompt preset and Knowledge base. Select the Prompt preset option.

Starting from the Datasets page, the modal also asks for a Dataset name: the scenarios land in a new dataset created on the fly. Starting the generation from within an existing dataset skips this and adds the scenarios to that dataset.
Select or create a prompt preset
Section titled âSelect or create a prompt presetâGeneration runs as a two-step flow. In step 1, Choose or create, you pick a prompt preset: a reusable bundle of personas, topics, tone, and rules that shapes the scenarios. Select one of the built-in presets or create your own.

When creating a new prompt preset, itâs always nice to have:
- A descriptive name: This helps identify the preset quickly
- A description: This guides the generation and keeps the scenarios aligned with your intended personas
Define rules
Section titled âDefine rulesâYou can then add specific rules that define behaviors your agent should respect and that are at risk of being broken when interacting with the selected personas. These rules help evaluate different persona situations and will be used to generate scenarios that specifically test whether your agent maintains these behaviors.

For example:
-
Persona: Customer using slang/emojis asking about loans
-
Rules: Enforce professional tone and refusal to do interest calculations
-
Persona: Crypto investor seeking investment advice
-
Rules: Refuse to provide unauthorized financial advice and avoid making specific investment recommendations
After defining a set of rules, click Add to save the prompt preset.
Generate scenarios
Section titled âGenerate scenariosâStep 2, Review, shows the selected preset and its rules. Set:
- Agent: the agent you want to test.
- Target key: the output field the generated checks evaluate. It defaults to the assistant response for a chat agent, or to the first available path in the schema for a structured agent, and you can point it elsewhere. The presetâs rules are turned into a conformity check on this key. See Annotate for how target keys and checks work.
- Number of scenarios: how many scenarios to generate.

Click Generate. It runs relatively quickly, and you end up with a high-quality, evaluated dataset.
Review and evaluate
Section titled âReview and evaluateâYou can see that you have a generated user message that adheres to the persona. You can generate an answer so that you can actually evaluate your agentâs response and see if the rules adhere.
After generating an example response, you can also test the evaluation. If the evaluation passes, you have a meaningful scenario. This specific scenario can then be used for a dedicated evaluation dataset and for evaluation runs where you would need to iterate on a high-quality dataset.
Next steps
Section titled âNext stepsâ- Review scenarios - Make sure to Annotate
- Generate knowledge base scenarios - Try Knowledge base scenarios
- Agentic vulnerability detection - Try Vulnerability Scanner