> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/technical-library/zh-tw/zoom-workplace/zoom-phone/expert-insights/emergency-services-best-practices/emergency-notifications.md).

# 緊急通知

應配置一個或多個通知管道，以便在撥打緊急電話時立即向安全團隊發出警示。

<table data-header-hidden="false" data-header-sticky><thead><tr><th>通道</th><th>運作方式</th></tr></thead><tbody><tr><td><strong>電子郵件</strong></td><td>帳戶或站點層級的通訊清單會接收含來電者詳細資料與偵測到的位置的警示。</td></tr><tr><td><strong>內部安全應變團隊</strong></td><td>一個會與緊急通話並行響鈴的 Zoom Phone 通話佇列。成員可監控、偷聽或插入通話。可依站點設定。</td></tr><tr><td><strong>Zoom 聊天機器人</strong></td><td>「緊急通話通知」應用程式（Zoom App Marketplace）會將警示發布到指定的聊天群組。也可以將訊息推送到 Zoom 數位看板（例如，指引應變人員前往正確樓層）。</td></tr><tr><td><strong>Webhook</strong></td><td>用於與第三方事件管理平台整合的 Zoom API webhook。</td></tr></tbody></table>

#### 自訂緊急通話免責聲明

Zoom Phone 可讓管理員設定自訂的緊急通話免責聲明，當使用者首次開始使用 Zoom Phone 時會顯示給他們。此免責聲明可用來告知使用者緊急通話流程、限制，或公司特定的安全政策——例如，提醒使用者確認其緊急地址，或說明貴組織如何處理緊急通話。

可在帳戶、站點、群組或個別使用者層級進行設定，讓管理員能依不同地點或使用者族群彈性調整訊息。管理員可自訂顯示頻率（例如僅顯示一次、每次登入時顯示，或定期顯示）、標題（最多 60 個字元）以及內文（最多 500 個字元）。此聲明也支援多種語言，因此不同地區的使用者會以其偏好的語言看到訊息。

如需詳細的設定說明，請參閱 [設定 Zoom Phone 自訂免責聲明](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0076990).


---

# 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://library.zoom.com/technical-library/zh-tw/zoom-workplace/zoom-phone/expert-insights/emergency-services-best-practices/emergency-notifications.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.