> 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/shang-wu-fu-wu/zoom-revenue-accelerator/zoom-revenue-accelerator-explainer/zra-requirements.md).

# ZRA 需求

本頁討論 Zoom Revenue Accelerator（ZRA）的需求。

### Zoom Revenue Accelerator 要求客戶在其帳戶中擁有一個關聯網域

Zoom Revenue Accelerator 要求帳戶至少擁有一個 [關聯網域](https://support.zoom.us/hc/en-us/articles/203395207-Getting-started-with-associated-domains) 已在其 Zoom 帳戶中設定。這可讓 Zoom Revenue Accelerator 自動區分包含外部參與者（即銷售會議）的 Zoom 會議與內部會議。

### 使用者必須整合其行事曆，才能自動錄製並擷取會議分析資訊

Zoom Revenue Accelerator 要求使用者在其 Zoom 帳戶中設定一個 [行事曆整合](https://support.zoom.us/hc/en-us/articles/360000488243-Setting-up-calendar-and-contacts-integration) 於其 Zoom 帳戶上，以便自動錄製外部會議供分析。此整合會透過受邀參與者的電子郵件網域辨識包含外部參與者的會議。

{% hint style="info" %}
**附註**

Zoom 的行事曆整合相容於 [Zoom 的郵件與行事曆服務](https://explore.zoom.us/en/products/zoom-mail-calendar-service/)、Google 日曆、Microsoft Office 365 和 Microsoft Exchange。
{% endhint %}

### Zoom Revenue Accelerator 確實 *不* 需要行事曆整合以自動錄製並分析電話通話

Zoom Revenue Accelerator 不需要行事曆整合即可自動錄製並分析電話通話。管理員可以將 Zoom Revenue Accelerator 設定為 [偵測內部分機](https://support.zoom.us/hc/en-us/articles/7977115380749-Managing-Zoom-IQ-recording-access-and-disclaimers-#h_01G923V51DH36RYE7JRQTNGV6G) 與客戶帳戶相關聯。若啟用，與外部電話號碼的對話將視為外部參與者，並會提示 Zoom Revenue Accelerator 自動錄製並分析該通話。


---

# 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/shang-wu-fu-wu/zoom-revenue-accelerator/zoom-revenue-accelerator-explainer/zra-requirements.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.