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

# Vue d’ensemble

Plusieurs fonctionnalités liées à l'appel d'urgence sont intégrées à votre système de téléphonie Zoom Phone. Les sections suivantes fournissent une vue d’ensemble complète et les bonnes pratiques concernant le routage des urgences, les notifications d'événement d'urgence et la configuration d’une équipe interne d’intervention en matière de sécurité.

Les services d’urgence nomades permettent au système de détecter l’emplacement des utilisateurs et de fournir une adresse physique en cas d'appel d'urgence. Ce document décrit les services d’urgence nomades pour les services « natifs » de Zoom Phone aux États-Unis et au Canada, les options Apportez votre propre opérateur, ainsi que les marchés et sites situés en dehors des États-Unis et du Canada.

La figure ci-dessous représente les composants de la solution E911 de Zoom Phone :

<figure><img src="https://4108585137-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/fr/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.
