> 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/ko/sound-systems.md).
# 사운드 시스템
Verkada 사운드 시스템은 모든 사이트에서 엔터프라이즈급 음악, 즉시 공지, AI 기반 억제를 제공하며, 모두 하나의 직관적인 대시보드에서 관리됩니다.
**개요**\
Verkada Sound Systems는 클라우드로 관리되는 엔터프라이즈급 오디오 솔루션으로, 상업용 라이선스 음악, 즉시 방송, AI 기반 억제 기능 등을 제공합니다. 이 플랫폼은 Alarms 및 Desk Station과 통합되어 단일 화면에서 건물을 더욱 통합적으로 관리할 수 있게 해줍니다.
시작하려면 다음 링크를 확인하세요:
---
# 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/ko/sound-systems.md?ask=&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.