> 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/zoom-workplace/zoom-workspace-reservation.md).

# Zoom 工作区预约

欢迎阅读 Zoom 工作区预约文档

本文档提供技术实施细节、配置工作流以及专为部署 Zoom 解决方案的管理员设计的战略实践。

您将找到可简化复杂配置的逐步流程、可加快解决时间的故障排查资源，以及展示真实世界应用程序场景的实用示例。

其中的主题将技术规格与可衡量的商业成果联系起来，使您能够架构解决方案、支持客户实施，并识别功能/特性扩展的机会。无论您是在进行初始部署、优化现有环境，还是为您的组织评估高级功能/特性，这份文档都是您成功利用 Zoom 产品的权威资源。

{% content-ref url="/pages/3f8355aacafbe2014b2a1c6419381a0b544fcc50" %}
[Zoom 工作区预约实用指南](/technical-library/zh/zoom-workplace/zoom-workspace-reservation/zoom-workspace-reservation-field-guide.md)
{% endcontent-ref %}


---

# 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/zoom-workplace/zoom-workspace-reservation.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.