> 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/it/archive-content/emergency-services-best-practices/overview.md).
# Panoramica
Sono presenti diverse funzionalità relative alla chiamata di emergenza integrate nel sistema Zoom Phone. Le sezioni seguenti forniscono una panoramica completa e le best practice per l'Instradamento delle chiamate di emergenza, le notifiche di Evento di emergenza e la configurazione di un team interno di risposta alla sicurezza.
I servizi di emergenza nomadi servono a consentire al sistema di rilevare la posizione degli utenti e a fornire un indirizzo fisico nel caso di chiamare i soccorsi per un'emergenza. Questo documento descrive i servizi di emergenza nomadi per i servizi “native” di Zoom Phone negli Stati Uniti e in Canada, le opzioni Bring Your Own Carrier e i mercati e i siti al di fuori degli Stati Uniti e del Canada.
La figura seguente rappresenta i componenti della soluzione E911 di Zoom Phone:
---
# 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/it/archive-content/emergency-services-best-practices/overview.md?ask=&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.
