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

# Zoom Scheduler

本節提供技術實作細節、組態工作流程，以及專為部署 Zoom 解決方案的管理員所設計的策略性做法。

您將找到可簡化複雜設定的逐步程序、可加快解決時間的疑難排解資源，以及展示實際應用情境的實用範例。

本節中的主題將技術規格與可衡量的商業成果連結起來，使您能夠設計解決方案、支援客戶實作，並找出功能擴充的機會。無論您是在進行初始部署、最佳化現有環境，還是評估組織的進階功能，本文件都將成為您成功運用 Zoom 產品的權威資源。

{% content-ref url="/pages/36815679b32780a09347f78a0c762086dfbbafc5" %}
[Zoom Scheduler 說明](/technical-library/zh-tw/zoom-workplace/zoom-scheduler/zoom-scheduler-explainer.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://library.zoom.com/technical-library/zh-tw/zoom-workplace/zoom-scheduler.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.