Skip to main content
A Conversation step is where your agent talks with the caller. It speaks a message, then keeps the conversation going until one of its transitions fires. Most of a flow is Conversation steps; the other step types do the work in between.

When to use it

  • To ask a question and wait for the answer, for example “What’s your order number?”
  • To give information and let the caller react.
  • To collect values from what the caller says, as variables.
  • To say something and move straight on, with an Auto transition.

Add a Conversation step

1

Add the step

On the canvas, click Add node and choose Conversation (“Interactive dialog with the user”). The step’s panel opens.
2

Write the message

Choose Static or Prompt and write the Message.
3

Add transitions

Open Transitions and add at least one, so the call can move on. Connect each one to the next step on the canvas.
4

Add variables (optional)

Open Variables to capture values from the conversation or set local values.
The Verify the order Conversation step panel with a Prompt message, and the Transitions section showing 2The Verify the order Conversation step panel with a Prompt message, and the Transitions section showing 2

Fields

Interruption options:
The Interruption section with Inherit selected, and the Enable and Disable optionsThe Interruption section with Inherit selected, and the Enable and Disable options
Messages support Jinja as well as {{variable_name}}.

Transitions

A new Conversation step has no transitions. You can add these: Auto and After user replies can’t be on the same step; adding one asks to replace the other. See Transitions for conditions, the “offer it only when” rules, and how the agent picks between several transitions.
The Transitions section of a Conversation step, listing two Prompt transitions, each Always offeredThe Transitions section of a Conversation step, listing two Prompt transitions, each Always offered

Variables

In Variables, click Add variable and choose:
The Variables section with the Add variable menu open: DTMF capture, Live variable, Variable on node exit and Local variableThe Variables section with the Add variable menu open: DTMF capture, Live variable, Variable on node exit and Local variable
The section groups them as Live variables, On node exit, Local and Keypad. See Extract values from the conversation and Static and local variables.

How it works on a call

1

The interruption setting is applied

The step’s Interruption setting takes effect for as long as the call stays on this step.
2

Skip if and live variable rules are checked

If a Skip if matches, the call goes straight to its target. If a When a live variable matches rule already holds, the call moves on without speaking.
3

Local variables are set

Any Local variable on the step gets its value.
4

The agent speaks

A Static message is spoken as written. A Prompt message becomes instructions for the agent’s reply. If the caller said something while earlier steps were working, the same reply answers it.
5

The step waits or moves on

The step waits for the caller if it has a Prompt, DTMF input, After user replies or When a live variable matches transition, or if the flow has any global step. With only Auto, it moves on as soon as the message ends.
While the step waits, each Prompt transition and each global step is offered to the agent as a possible next move. The agent keeps talking with the caller, following your message, until it decides one of them fits. Required Variable on node exit values must be collected first: if one is missing or fails its value check, the agent asks the caller again instead of moving on. If a variable used in the message changes while the call is on the step (a live variable, or a local variable with Keep in sync), the agent uses the new value in its next reply.

Good to know

  • A Conversation step with no transitions, in a flow without global steps, speaks its message and then has nowhere to go. Give every Conversation step a way out.
  • Keypad digits captured with DTMF capture are saved only when the caller presses a key that has a DTMF input transition (# or *). See Keypad input.
  • Confirm before proceeding, in the Global section, makes the agent check with the caller before the call enters this step. See Step types.

Transitions

Every transition type and how the agent picks the next step.

Extract values from the conversation

Live variables and variables on node exit.

Write a prompt that works on calls

Write step instructions the agent follows on a call.

Router step

Branch on the values you collected.