> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/contact-center-configuration/building-your-callflow/via-dialogue-studio/ivr-menu.md).

# Configure an IVR menu in Dialogue Studio

Configure native IVR Menu prompts, keypad options, retry limits, actions, and output branches.

Use the native IVR Menu node in Incoming to play prompts and collect one keypad choice: `0`–`9`, `*`, or `#`. A valid choice runs its configured action or continues through a Route output.

{% hint style="warning" %}
Use the controls offered by your installed node version. Action availability also depends on the connect model. The [Connect and Unify comparison](/set-up-dialogue-cloud-neo/connect-vs-unify.md) describes DC2025.02a limits, including actions and SharePoint IVR that were planned for Unify.
{% endhint %}

## Configure the Menu

| Control                          | Configuration                                                                                                               |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Welcome / menu prompt**        | **None**, **Say**, or **Play**. The welcome plays once, not on each retry.                                                  |
| **Timeout (sec)**                | Defaults to **10** seconds. The wait timer starts after the menu prompts finish.                                            |
| **Max retries**                  | Defaults to **3**. Invalid keys and timeouts count toward the same limit. **0** disables the limit.                         |
| **Timeout / Max retries action** | Defaults to **Route (output)**. Choose the exit behavior explicitly.                                                        |
| **Options**                      | Add unique keypad keys. Each option has an optional question prompt, an optional answer/confirmation prompt, and an action. |

The node plays the welcome, then the option prompts in list order. After a valid choice, it plays the optional confirmation before performing the action.

An invalid key or timeout counts toward the retry limit. If the limit has not been reached, the node repeats the option prompts without the welcome. At the limit, it performs the configured Timeout / Max retries action.

With **Max retries = 0**, invalid keys and timeouts do not reach a finite retry exit. Use that setting only when indefinite retries are intentional.

## Configure Prompts

* **None** skips that prompt.
* **Say** uses text-to-speech. Choose **Text**, **SSML** (Speech Synthesis Markup Language), or **Custom**, which uses a configured Voice node. Enter literal text, or use a message property, flow/global context, or a JSONata expression.
* **Play** uses an audio URL or a SharePoint path. Use SharePoint paths only where your deployment supports that IVR configuration.

Use the same prompt choices for each option's question and optional confirmation.

## Choose an Action

Available direct actions include Disconnect, Enqueue, Callback, Forward, Preferred Hunt, Queued Callback, Voicemail, and Merge conversations. Configure the same required inputs described in [Core Nodes](/contact-center-configuration/building-your-callflow/via-dialogue-studio/core-nodes.md), such as Skill, destination, preferred targets, or the two Merge session IDs.

**Route (output)** continues the flow through that option's output rather than executing one of those actions.

An **Empty** or No Action choice, where offered, has phase-specific behavior. It is not equivalent to routing through an output. See [No Action](/contact-center-configuration/building-your-callflow/via-dialogue-studio/core-nodes.md#action-nodes).

Do not assume the native menu offers every standalone action. On **Connect**, use the separate IVR Question action described in [Core Nodes](/contact-center-configuration/building-your-callflow/via-dialogue-studio/core-nodes.md) to run an existing SharePoint IVR question from the same UCC. **IVR Question** reuse is planned, not available, for **Unify** in the documented **DC2025.02a** scope. This restriction is separate from building prompts and keypad branches in the Studio menu.

## Wire and Test Outputs

Only options configured as **Route (output)** create option output ports. Those ports follow the options' list order. If Timeout / Max retries is also Route, its port is last.

Reordering options can change prompt order and Route port order. Check the wires after changing the menu.

Test a valid choice, an invalid key, silence, and retry-limit exit. Confirm both the prompt sequence and the final action or output.

The [Simple IVR Example](/product-reference/dialogue-studio/dialogue-studio-example-flows/simple-ivr.md) uses Ask-and-wait and Switch nodes. Its timeout and looping design are not the native menu's defaults.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/contact-center-configuration/building-your-callflow/via-dialogue-studio/ivr-menu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
