While working with teams building voice agents in SIMULATE, we kept seeing the same pattern:
PMs and engineers would run large batches of tests, then immediately jump into the workflow graph to replay calls and figure out one thing:
Where exactly did the agent’s path diverge from the intended flow?
The only way to answer that was manual flow tracing — stepping through nodes, comparing expected vs actual paths, and trying to spot the turn where behavior shifted. It was slow but necessary work.
We turned that repeated behavior into a feature called Flow Analysis.
For each test run, Flow Analysis computes and surfaces:
- The exact path the agent took through the workflow
- The node where it diverged from the expected path
- How the rest of the conversation evolved after that point
This makes debugging more of an engineering task (fix the specific node/logic/prompt) instead of an investigation across the whole graph.
If you’re working with voice agents or complex conversational flows and still manually scanning graphs to debug failures, would be interested in your thoughts on this approach.
PMs and engineers would run large batches of tests, then immediately jump into the workflow graph to replay calls and figure out one thing:
Where exactly did the agent’s path diverge from the intended flow?
The only way to answer that was manual flow tracing — stepping through nodes, comparing expected vs actual paths, and trying to spot the turn where behavior shifted. It was slow but necessary work.
We turned that repeated behavior into a feature called Flow Analysis.
For each test run, Flow Analysis computes and surfaces:
- The exact path the agent took through the workflow - The node where it diverged from the expected path - How the rest of the conversation evolved after that point
This makes debugging more of an engineering task (fix the specific node/logic/prompt) instead of an investigation across the whole graph.
If you’re working with voice agents or complex conversational flows and still manually scanning graphs to debug failures, would be interested in your thoughts on this approach.
More details: https://app.futureagi.com/dashboard/simulate/agent-definitio...