> 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-lege-ich-eine-gruppen-voicemail-an.md).

# How do I create a group voicemail?

Set up group voicemail in sipgate so teams can receive and manage messages together.

{% hint style="info" %}
**Note:** The *Groups* feature **is only available to sipgate classic customers**  . On sipgate neo, it is integrated in a different form.
{% endhint %}

As an administrator, you can set up a **answering machine** for each of your groups. Calls to the group's phone number or extension will then be sent—if desired—to the group's so-called **voicemail**  . To set up group voicemail, go to the relevant [**group routing**](https://app.sipgate.com/groups). Set up a **forwarding** to voicemail there, and specify the conditions under which voicemail should be active.

Once voicemail is set up, you can **upload or record a custom greeting**  . Alternatively, you can use sipgate's **default greetings**  . All members of the group can view **transcripts** in the event list and listen to the recorded **messages** .


---

# 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-lege-ich-eine-gruppen-voicemail-an.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.
