> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Simulate conversations

> Define representative conversation simulations, expected outcomes, and review criteria before automated execution is released.

A simulation describes an interaction you want to assess against an agent configuration. Save the definition separately from the result: accepting a test case does not mean a conversation ran or passed.

## Prepare a useful case

<Steps>
  <Step title="Choose one scenario">Name a concrete situation, such as a customer asking about an unsupported action. State the expected response and the boundary the agent must preserve.</Step>
  <Step title="Supply representative context">Prepare the chat history, dynamic variables, environment, and channel needed by the case. Use synthetic data and avoid copying private transcripts into fixtures.</Step>
  <Step title="Define the outcome">Specify response conditions, examples, or expected tool behavior supported by the test schema. Include a failure case as well as a normal interaction.</Step>
  <Step title="Save and read back">Use [Create test](/api-reference/tests/create-test), then retrieve the saved definition. Keep the case ID and agent version you intend to assess.</Step>
</Steps>

## Execution boundary

The current implementation stores test definitions and exposes invocation reads, but automated execution and resubmission remain gated. Do not report a success rate from saved definitions or empty invocation results.

When execution is released, require the exact configuration version, input scenario, result status, and review evidence for each run. See [Testing](/agents-platform/monitor/testing).

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does a simulation prove voice quality?" id="faq-simulation-voice">A text scenario cannot establish microphone behavior, speech recognition, audio quality, or channel reliability. Those need separate supported runtime tests.</Accordion>
  <Accordion title="Should a test assert an exact sentence?" id="faq-simulation-exact">Prefer meaningful behavior and constraints when wording can vary. Exact text is appropriate only when that text is itself a requirement.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.