Skip to main content
Use this type when your agent must follow a fixed flow, for example a compliance script or an identity check.

​
Build a scenario

Draw the flow as a scenario on the Scenario Builder page, and select the agents that it applies to. If you have a JSON scenario definition, import it instead.
  • Each path from the start to an end becomes one Digital Human, so each branch you add adds a test.
  • Each Digital Human follows its path turn by turn, so you can see where your agent leaves the flow.
Scenario Builder canvas with the toolbox, a start node, agent and user turns, and a three-way branch that rejoins at a final user turn Scenario Builder canvas with the toolbox, a start node, agent and user turns, and a three-way branch that rejoins at a final user turn

​
Run it

1

Select the card

Create a simulation and select the Scenario Adherence card.Scenario Adherence card in the Create Simulation type pickerScenario Adherence card in the Create Simulation type picker
2

Pick the scenarios

A scenario with no path from the start cannot be selected, so fix its graph first.
With the API, pass workflow_adherence_v2, a map of scenario ID to the number of Digital Humans, to Generate Digital Humans.

​
Limits

  • Voice agents only.
  • Bluejay makes a maximum of 200 Digital Humans for each generate request. Paths beyond that are left out.
Last modified on October 22, 2026