Simulator
Last updated: May 14, 2026
Use the Simulator to test how Aissist responds before you go live.
It shows the reply, the context behind it, and any actions or sub agents involved.
Open the Simulator
Go to Simulator from the left navigation.
Set input context, such as email or order number, if needed.
Enter a test message.
Review the result and supporting details.
Use input context when the workflow depends on customer identity, order data, or other platform attributes.
What to test
Use realistic examples from your live workflows.
Test things like:
common customer questions
edge cases and sensitive requests
scenarios that should trigger sub agents
scenarios that should call actions
If your workflow depends on customer identity or order context, use the simulator settings to mirror a real case.
What to inspect
The Simulator helps you inspect:
Response — the reply Aissist generated
Output Context — the instructions, assets, and sub agents that influenced it
Sub Agents Triggered — which sub agent matched and why
Actions Called — which actions ran and with what parameters
Action Response — what the action returned
Escalation and Summary — whether the workflow escalated and escalation summary
Fix common issues
If the result is wrong:
search Output Context with keywords
update Instructions or Sub Agents if behavior or workflow logic is off
update Assets if knowledge is missing, outdated, or conflicting
update Actions if parameters, lookup inputs, or returned data are incorrect
Recommended workflow
Use the Simulator whenever you:
add or change instructions
add or change assets
create or edit sub agents
connect or update actions
Use the Simulator to validate reply logic before live traffic.
Use Deploy Gateway when you are ready to deploy Aissist in the real platform.
For action-specific troubleshooting, use Action Debugger.
For asset retrieval checks, use Asset Debugger.
Best practice
Test one workflow at a time.
Fix issues at the source, then re-run the same scenario until the result is stable.
Last updated