> 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/zh-tw/archive-content/emergency-services-best-practices/overview.md).
# 概覽
您的 Zoom Phone 系統內建了多項與緊急撥號相關的功能。以下各節將全面概述緊急路由、緊急事件通知，以及內部安全應變團隊的設定最佳實務。
流動式緊急服務可讓系統偵測使用者的位置，並在發生緊急來電時提供實體地址。本文件說明 Zoom Phone 在美國與加拿大的「原生」服務、使用自有電信業者（Bring Your Own Carrier）選項，以及美國與加拿大以外市場和站點的流動式緊急服務。
下圖表示 Zoom Phone E911 解決方案的組成元件：
---
# 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/zh-tw/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.
