> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/sound-systems/de/soundsysteme.md).

# Soundsysteme

Verkada Sound Systems bietet unternehmensgerechte Musik, sofortige Durchsagen und KI-gestützte Abschreckung an jedem Standort – alles verwaltet über ein einziges intuitives Dashboard.

**Übersicht**\
Verkada Sound Systems ist eine cloudverwaltete Audio-Lösung für Unternehmen mit kommerziell lizenzierter Musik, sofortigen Durchsagen, KI-gestützter Abschreckung und mehr. Die Plattform lässt sich in Alarme und Desk Station integrieren, um Ihr Gebäude weiter über eine einzige Benutzeroberfläche zu vereinheitlichen.&#x20;

Schauen Sie sich diese Links an, um loszulegen:

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/sound-systems/de/erste-schritte/erste-schritte-mit-sound-systems.md">Erste Schritte mit Sound Systems</a></td><td></td></tr><tr><td></td><td><a href="/sound-systems/de/erste-schritte/rollen-and-berechtigungen-fur-sound-systems.md">Rollen &amp; Berechtigungen für Sound Systems</a></td><td></td></tr><tr><td></td><td><a href="/sound-systems/de/erste-schritte/netzwerkeinstellungen-fur-sound-systems.md">Netzwerkeinstellungen für Sound Systems</a></td><td></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

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

```
GET https://help.verkada.com/sound-systems/de/soundsysteme.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 `build a script that syncs our docs to a CMS` 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.
