> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryhamsa.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Conversation step

> Use a Conversation step to speak to the caller and listen: its message, interruption setting, variables, transitions and what happens on a call.

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](https://docs.tryhamsa.com/agents/variables/extracted-variables.md).
* 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 2](https://mintcdn.com/hamsa-452fa79a/Rl78D_qJIpinmg19/images/agents/flow/steps/conversation-step-light.webp?fit=max\&auto=format\&n=Rl78D_qJIpinmg19\&q=85\&s=173b85444d3513faf19cae051dbe06d6)

## Fields

| Field | What it does | Default |
| - | - | - |
| **Message** | "The message your agent will speak to the user. Use `{{variable_name}}` to include variables." Required: "Message is required". | Empty |
| **Static** / **Prompt** | **Static** speaks your text word for word. **Prompt** treats your text as instructions, and the agent writes what to say. | **Prompt** |
| **Interruption** | "Control whether the user can interrupt the agent while speaking on this node". | **Inherit** |

**Interruption** options:

| Option | What it does |
| - | - |
| **Inherit** | "Use the global agent interruption setting": the **Interrupt** setting in the agent's [call behavior settings](https://docs.tryhamsa.com/agents/settings/call-behavior.md). Flow agents start with it off. |
| **Enable** | "Allow the user to interrupt the agent on this node". |
| **Disable** | "Prevent the user from interrupting the agent on this node". Use it for messages the caller must hear in full, such as terms or a disclaimer. |

![The Interruption section with Inherit selected, and the Enable and Disable options](https://mintcdn.com/hamsa-452fa79a/Rl78D_qJIpinmg19/images/agents/flow/steps/conversation-interruption-light.webp?fit=max\&auto=format\&n=Rl78D_qJIpinmg19\&q=85\&s=6f2113af3f210629cf623d55ce8bd847)

Messages support [Jinja](https://docs.tryhamsa.com/agents/variables/jinja.md) as well as `{{variable_name}}`.

## Transitions

A new Conversation step has no transitions. You can add these:

| Type | Moves on when |
| - | - |
| **Prompt** | The conversation matches a condition you describe in words. The agent decides, based on what the caller said. |
| **When a live variable matches** | A [live variable](https://docs.tryhamsa.com/agents/variables/live-variables.md) meets your rules. Checked when the call arrives and again each time the variable changes. |
| **DTMF input** | The caller presses a key. See [Keypad input](https://docs.tryhamsa.com/agents/flow/keypad-input.md). |
| **Skip if** | Your conditions already hold when the call arrives. The step is skipped entirely: nothing is spoken and its variables aren't set. Conditions use the same operators as the [Router step](https://docs.tryhamsa.com/agents/flow/steps/router.md#conditions). |
| **Auto** | The message has finished playing. The step doesn't wait for the caller. |
| **After user replies** | The caller finishes a reply, whatever they say. No model call decides it. |
| **Return to source** | The caller's reply matches its condition. The call goes back to the step that led here. See [Return to source](https://docs.tryhamsa.com/agents/flow/transitions.md#return-to-source). |

**Auto** and **After user replies** can't be on the same step; adding one asks to replace the other. See [Transitions](https://docs.tryhamsa.com/agents/flow/transitions.md) 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 offered](https://mintcdn.com/hamsa-452fa79a/Rl78D_qJIpinmg19/images/agents/flow/steps/conversation-transitions-light.webp?fit=max\&auto=format\&n=Rl78D_qJIpinmg19\&q=85\&s=95cf6550c457f8ef37a2b21139c501d8)

## Variables

In **Variables**, click **Add variable** and choose:

| Option | What it captures |
| - | - |
| **Live variable** | A value extracted in the background after every caller turn. See [Live variables](https://docs.tryhamsa.com/agents/variables/live-variables.md). |
| **Variable on node exit** | A value extracted once, when the call leaves this step. |
| **Local variable** | A value you set, when the call reaches this step. |
| **DTMF capture** | Digits the caller types on the keypad. |

![The Variables section with the Add variable menu open: DTMF capture, Live variable, Variable on node exit and Local variable](https://mintcdn.com/hamsa-452fa79a/Rl78D_qJIpinmg19/images/agents/flow/steps/conversation-add-variable-light.webp?fit=max\&auto=format\&n=Rl78D_qJIpinmg19\&q=85\&s=2d4f50d13addc5078b2ef587690de366)

The section groups them as **Live variables**, **On node exit**, **Local** and **Keypad**. See [Extract values from the conversation](https://docs.tryhamsa.com/agents/variables/extracted-variables.md) and [Static and local variables](https://docs.tryhamsa.com/agents/variables/local-variables.md).

## 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](https://docs.tryhamsa.com/agents/flow/global-steps.md). 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](https://docs.tryhamsa.com/agents/flow/keypad-input.md).
* **Confirm before proceeding**, in the **Global** section, makes the agent check with the caller before the call enters this step. See [Step types](https://docs.tryhamsa.com/agents/flow/steps/overview.md#confirm-before-proceeding).

## Related

> [card] [Transitions](https://docs.tryhamsa.com/agents/flow/transitions.md)
>
> Every transition type and how the agent picks the next step.

> [card] [Extract values from the conversation](https://docs.tryhamsa.com/agents/variables/extracted-variables.md)
>
> Live variables and variables on node exit.

> [card] [Write a prompt that works on calls](https://docs.tryhamsa.com/agents/build/write-a-prompt.md)
>
> Write step instructions the agent follows on a call.

> [card] [Router step](https://docs.tryhamsa.com/agents/flow/steps/router.md)
>
> Branch on the values you collected.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.