> 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/bootstrap-mode.md).

# Bootstrap Mode

When complete network data is not available for all locations, bootstrap mode enables test users to assist with data collection.

1. Enable Bootstrap Mode for test users
2. As users roam, their Zoom Workplace app prompts them to confirm or select a company location when unknown network data is detected
3. The app captures the network data (IPs, BSSIDs) and submits it
4. Admins receive an email alert and approve or reject the data in the admin portal

There is a setting called "Email Recipients for Emergency Services Data Maintenance" under the Emergency Services Management for each site that controls who receives these alerts.

Bootstrap mode should be used during initial deployment with a test team to validate locations. It can remain enabled as an ongoing maintenance tool — if users report new data for an existing company location, this typically indicates a network change that requires corresponding updates to Zoom Phone locations.


---

# 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/zoom-workplace/zoom-phone/expert-insights/emergency-services-best-practices/bootstrap-mode.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.