> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/voicemails-und-ivr/wie-richte-ich-ein-mehrstufiges-sprachmenue-ivr-ein.md).

# How do I set up a multi-level voice menu (IVR)?

Set up a multi-level voice menu (IVR) in sipgate – guide callers through multiple selection levels.

You can link multiple phone menus so callers are automatically routed through different selection levels—for example, by location or reason for calling.

**Example**

* **Key 1:** connects to **Frankfurt branch**\
  → there: **1 = Opening hours**, **2 = Customer support**
* **Key 2:** connects to **Hamburg branch**\
  → there: **1 = Opening hours**, **2 = Customer support**

**Step-by-step guide**

**1. Create the main phone menu**

* Create a new phone menu, e.g. **“Main IVR”**.
* Assign a **phone number** .
* Example greeting:\
  “For Frankfurt, press 1. For Hamburg, press 2.”

**2. Create a phone menu for Frankfurt**

* Create a new phone menu **“Frankfurt IVR”** .
* Example greeting:\
  “Press 1 for our opening hours. Press 2 for customer support.”
* Key 1 → Add a greeting (opening hours).
* Key 2 → Forward the call to the group **Frankfurt Customer Support**.

**3. Create a phone menu for Hamburg**

* Create a new phone menu **“Hamburg IVR”** .
* Use the same structure as in Frankfurt (1 = opening hours, 2 = customer support).

**4. Link the menus**

* Open the main phone menu **(Main IVR)**.
* Link:
  * **Key 1 → Frankfurt IVR**
  * **Key 2 → Hamburg IVR**

{% hint style="info" %}
**Tip:** Test all menu paths with a call to make sure each key routes callers correctly and the greetings play.
{% endhint %}


---

# 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://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/voicemails-und-ivr/wie-richte-ich-ein-mehrstufiges-sprachmenue-ivr-ein.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.
