> 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/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>用于与第三方事件 &#x26; 活动 &#x26;直播管理平台集成的 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/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.