> 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/zoom-workplace/zoom-phone/expert-insights/emergency-services-best-practices/emergency-notifications.md).

# Emergency Notifications

One or more notification channels should be configured to alert the safety team immediately when an emergency call is placed.

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Channel</th><th>How It Works</th></tr></thead><tbody><tr><td><strong>Email</strong></td><td>Distribution list at account or site level receives alerts with caller details and detected location.</td></tr><tr><td><strong>Internal Safety Response Team</strong></td><td>A Zoom Phone call queue that rings in parallel with the emergency call. Members can monitor, listen in, or barge into the call. Configurable per site.</td></tr><tr><td><strong>Zoom Chat Bot</strong></td><td>"Emergency Call Notifications" app (Zoom App Marketplace) posts alerts to designated chat groups. Can also push messages to Zoom digital signage (e.g., directing responders to the correct floor).</td></tr><tr><td><strong>Webhook</strong></td><td>Zoom API webhook for integration with third-party event management platforms.</td></tr></tbody></table>

#### Custom Emergency Disclaimer

Zoom Phone allows administrators to configure a custom emergency calling disclaimer that is displayed to users when they first start using Zoom Phone. This disclaimer can be used to inform users about emergency calling procedures, limitations, or company-specific safety policies — for example, reminding users to confirm their emergency address or explaining how emergency calls are handled in your organization.

The disclaimer can be configured at the account, site, group, or individual user level, giving administrators flexibility to tailor the message for different locations or user populations. Administrators can customize the display frequency (e.g., shown once, on every login, or periodically), the title (up to 60 characters), and the body text (up to 500 characters). The disclaimer also supports multiple languages, so users in different regions see the message in their preferred language.

For detailed setup instructions, see [Setting up the Zoom Phone custom disclaimer](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/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.
