> 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-calling-number-capability.md).

# Emergency Calling Number Capability

Not all phone numbers support emergency calling in every country. Before configuring emergency services, verify that the numbers in use — or numbers being purchased — are capable of placing emergency calls.

#### Numbers Not Yet Purchased

Before purchasing phone numbers, verify that they support emergency calling in the target country. Number capabilities vary by country and number type. Review the capabilities of numbers by country at <https://www.zoom.com/en/phone-number-requirements/>.

#### Numbers Already Purchased

For numbers that have already been purchased, the administrator can verify emergency calling support in the Zoom admin portal. Navigate to **Number Management > Phone Numbers** and locate the number in question. Numbers that support emergency calling display an **SOS icon** next to the number under the **Capability** column. If the SOS icon is not present, the number does not support emergency calling and should not be relied upon for emergency services.

#### When Emergency Calls May Fail to Route

The following configurations or conditions can prevent an emergency call from routing to the PSAP. Administrators should review these scenarios during deployment to ensure that all users who require emergency calling capability have it properly configured.

<table data-header-hidden="false" data-header-sticky><thead><tr><th>#</th><th>Scenario</th><th>Why the Call Fails</th></tr></thead><tbody><tr><td>1</td><td>Administrator sets "Do not route emergency calls to PSAP" for extensions without a local phone number, and no Internal Safety Response Team (ISRT) fallback is configured</td><td>Policy explicitly blocks extension only users from reaching the PSAP, and no Internal Safety Response Team is available as an alternative destination</td></tr><tr><td>2</td><td>User-level policy "Emergency calls to PSAP" is disabled</td><td>The extension-level emergency calling policy is turned off, preventing the user from placing emergency calls to the PSAP</td></tr><tr><td>3</td><td>Route to PSAP option disabled and no Call queue members for Internal Safety Response Team (ISRT)</td><td>Administrator has disabled route to PSAP option and no call queue members are configured for the ISRT.</td></tr><tr><td>3</td><td>Site has no dedicated emergency number AND the site emergency pool is empty</td><td>No caller ID is available to present to the PSAP — the system cannot place the call without a valid outbound number</td></tr><tr><td>4</td><td>Caller ID method is not configured in site or account settings</td><td>No caller ID method is defined for emergency calls, so the system does not know which number to use as the outbound caller ID</td></tr><tr><td>5</td><td>Account-level emergency number pool feature is disabled AND the site-level pool is empty</td><td>No global fallback path exists — the account-level pool cannot be used, and the site has no local pool numbers available</td></tr><tr><td>6</td><td>Non-U.S./Canada site with no ELIN configured in the emergency pool</td><td>Outside the U.S./Canada, an ELIN is mandatory for emergency calls — without one, the system has no caller ID to present to the PSAP</td></tr></tbody></table>

**Recommendation:** After completing emergency services configuration, review each site and user policy to confirm that no extension falls into one of the scenarios above. Pay particular attention to extension-only users and sites outside the U.S./Canada, as these are the most common cases where emergency call routing may be inadvertently blocked.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://library.zoom.com/zoom-workplace/zoom-phone/expert-insights/emergency-services-best-practices/emergency-calling-number-capability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.