Conversation Simulator
deepeval's ConversationSimulator allows you to simulate full conversations between a fake user and your chatbot, unlike the synthesizer which generates regular goldens representing single, atomic LLM interactions.
from deepeval.dataset import ConversationalGolden, Persona
from deepeval.simulator import ConversationSimulator
from deepeval.test_case import Turn
# Create ConversationalGolden
conversation_golden = ConversationalGolden(
scenario="Andy Byron wants to purchase a VIP ticket to a cold play concert.",
expected_outcome="Successful purchase of a ticket.",
persona=Persona(characteristics="Andy Byron is the CEO of Astronomer."),
)
# Define chatbot callback
async def chatbot_callback(input):
return Turn(role="assistant", content=f"Chatbot response to: {input}")
# Run Simulation
simulator = ConversationSimulator(model_callback=chatbot_callback)
conversational_test_cases = simulator.simulate(conversational_goldens=[conversation_golden])
print(conversational_test_cases)The ConversationSimulator uses the scenario and persona from a ConversationalGolden to simulate back-and-forth exchanges with your chatbot. The resulting dialogue is used to create ConversationalTestCases for evaluation using deepeval's multi-turn metrics.
How It Works
The ConversationSimulator repeatedly generates a simulated user turn, sends it to your chatbot, and records the assistant response until the simulation ends.
- Each
ConversationalGoldendefines the scenario, persona, and expected outcome for a conversation. - The simulator model role-plays the user and generates each next user message.
- Your
model_callbacksends that message to your chatbot and returns an assistantTurn. - The simulator stops when
max_user_simulationsis reached or thestopping_controllerdecides the conversation should end. - The final conversation is packaged as a
ConversationalTestCasefor multi-turn evaluation.
Create Your First Simulator
To create a ConversationSimulator, you'll need to define a callback that wraps around your LLM chatbot. See Model Callback for supported callback arguments.
from deepeval.test_case import Turn
from deepeval.simulator import ConversationSimulator
async def model_callback(input: str) -> Turn:
return Turn(role="assistant", content=f"I don't know how to answer this: {input}")
simulator = ConversationSimulator(model_callback=model_callback)There are ONE mandatory and SIX optional parameters when creating a ConversationSimulator:
model_callback: a callback that wraps around your conversational agent. Required unless you're simulating a voice agent throughvoice_config.- [Optional]
voice_config: aVoiceConfigthat puts the simulator in voice mode — simulated user turns are spoken to your voice agent over a live connection and replies are transcribed back, with audio and latency captured on every turn. Mutually exclusive withmodel_callback: provide exactly one. - [Optional]
simulator_model: a string specifying which of OpenAI's GPT models to use for generation, OR any custom LLM model of typeDeepEvalBaseLLM. Defaulted togpt-5.4. - [Optional]
async_mode: a boolean which when set toTrue, enables concurrent simulation of conversations. Defaulted toTrue. - [Optional]
max_concurrent: an integer that determines the maximum number of conversations that can be generated in parallel at any point in time. You can decrease this value if you're running into rate limit errors. Defaulted to5. - [Optional]
simulation_graph: the rootSimulationNodeof a simulation graph for the simulated user. When omitted,deepevalfalls back to an LLM-driven default node. Passdefault_simulation_node(template=MyTemplate)here to use a custom prompt template. See Simulation Graph. - [Optional]
stopping_controller: a callback that controls whether the simulation should continue or end. By default,deepevaluses theexpected_outcomein yourConversationalGoldento decide when the conversation is complete. (Previously namedcontroller, which is still accepted as a deprecated alias.)
Simulate A Conversation
To simulate your first conversation, simply pass in a list of ConversationalGoldens to the simulate method:
from deepeval.dataset import ConversationalGolden, Persona
...
conversation_golden = ConversationalGolden(
scenario="Andy Byron wants to purchase a VIP ticket to a cold play concert.",
expected_outcome="Successful purchase of a ticket.",
persona=Persona(characteristics="Andy Byron is the CEO of Astronomer."),
)
conversational_test_cases = simulator.simulate(conversational_goldens=[conversation_golden])The persona describes who is talking; the scenario describes what they want. See Personas for how to write one, and for the voice-only settings — voice, background noise, interruptions — that a persona also carries.
There are ONE mandatory and ONE optional parameter when calling the simulate method:
conversational_goldens: a list ofConversationalGoldens that specify the scenario and persona.- [Optional]
max_user_simulations: an integer that specifies the maximum number of user-assistant message cycles to simulate per conversation. Defaulted to10.
A simulation ends when max_user_simulations has been reached, when the stopping_controller decides the conversation should end, or when the simulation_graph reaches a terminal=True node. By default, the simulator checks whether the conversation has achieved the expected outcome outlined in a ConversationalGolden.
See Stopping Logic to define your own stopping logic.
Incorporate Existing Turns
If your multi-turn chatbot has one or more predefined turns (for example, a hardcoded assistant message at the beginning of a conversation), you would simply include this as part of the simulation by providing a list of preexisting turns to a ConversationalGolden:
from deepeval.test_case import ConversationalTestCase, Turn
golden = ConversationalGolden(turns=[Turn(role="assistant", content="Hi! How can I help you today?")])By including a list of non-empty turns, deepeval will run simulations based on the additional context you've provided.
Evaluate Simulated Turns
The simulate function returns a list of ConversationalTestCases, which can be used to evaluate your LLM chatbot using deepeval's conversational metrics. Use simulated conversations to run end-to-end evaluations:
from deepeval import evaluate
from deepeval.metrics import TurnRelevancyMetric
...
evaluate(test_cases=conversational_test_cases, metrics=[TurnRelevancyMetric()])Advanced Usage
Customize the simulator around your application's conversation state, stopping criteria, and post-processing needs.
- Model Callback: pass conversation history or
thread_idinto your chatbot so simulations exercise the same stateful path as production. - Voice Mode: simulate spoken conversations against voice agents — user turns are synthesized to speech, sent over a live connection, and replies are transcribed with audio and latency captured on every turn. Also covers voice connectors and interruptions.
- Simulation Graph: drive the simulated user with a programmatic state machine instead of a flat LLM prompt — encode trajectories, retry budgets, and terminal success/failure states.
- Stopping Logic: replace expected-outcome stopping with business-specific logic such as tool calls, confirmation messages, or failure states.
- Custom Templates: change the simulated user's style, domain framing, or pressure level by overriding the user-turn prompts.
- Lifecycle Hooks: process each completed conversation immediately instead of waiting for the full simulation batch to finish.
FAQs
When should I use the ConversationSimulator instead of the Synthesizer?
ConversationSimulator when you need full multi-turn conversations between a fake user and your chatbot. The synthesizer generates regular goldens representing single, atomic LLM interactions, not back-and-forth dialogue.What does a ConversationalGolden actually drive in a simulation?
scenario, persona, and expected_outcome tell the simulator model who to role-play, what to attempt, and (by default) when the conversation is complete. The simulator generates each user turn from these fields and sends it to your model_callback.What does simulate() return, and how do I seed an existing conversation?
ConversationalTestCases you can pass straight into evaluate with multi-turn metrics. To seed a conversation, populate the ConversationalGolden with initial turns (such as a hardcoded opening assistant message) and the simulator continues from there.When does a simulation stop?
max_user_simulations is reached, when the stopping_controller returns end() (by default once the expected_outcome is met), or when a simulation_graph hits a terminal=True node — whichever fires first.Can I use any model to power the simulated user?
simulator_model accepts any of OpenAI's GPT models by name, or any custom LLM of type DeepEvalBaseLLM. Note it only powers the role-played user — your actual chatbot still runs through your model_callback.