> 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/business-services/zoom-revenue-accelerator/zoom-revenue-accelerator-explainer/zra-limitations.md).

# ZRA Limitations

This page discusses Zoom Revenue Accelerator (ZRA) limitations.

### Zoom Revenue Accelerator is not currently available for Zoom for Government

Zoom Revenue Accelerator is currently focused on providing functionality required by most small and medium-sized businesses. Zoom Revenue Accelerator is not available for Zoom for Government customers at this time.

### Zoom Revenue Accelerator is not compatible with End-to-End Encrypted (E2EE) Meetings

[End-to-end encrypted](https://support.zoom.us/hc/en-us/articles/360048660871-End-to-end-E2EE-encryption-for-meetings) (E2EE) meetings do not support cloud recordings or live transcriptions as a part of the service. Consequently, E2EE meetings are not compatible with 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/business-services/zoom-revenue-accelerator/zoom-revenue-accelerator-explainer/zra-limitations.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.