> 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/pt/archive-content/emergency-services-best-practices/overview.md).

# Visão geral

Existem vários recursos relacionados à chamada de emergência incorporados ao seu sistema Zoom Phone. As seções a seguir fornecem uma visão geral abrangente e as melhores práticas para Roteamento de emergência, notificações de Evento de emergência e configuração de uma equipe interna de resposta à segurança.

Os serviços de emergência nomádicos Permitir que o sistema detecte as localizações dos usuários e forneça um endereço físico no caso de uma chamada de emergência. Este documento descreve os serviços de emergência nomádicos para os serviços “nativos” do Zoom Phone nos EUA e Canadá, opções de Traga sua própria operadora (BYOC) e mercados e locais fora dos EUA e Canadá.

A figura abaixo representa os componentes da solução E911 do Zoom Phone:

<figure><img src="https://1821044411-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-d596dc5112a7a3b1fc50ac6fa3a69946df175c28%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/pt/archive-content/emergency-services-best-practices/overview.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.
