> 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/admin-corner/third-party-integrations/expert-insights.md).

# Expert Insights

Your step-by-step tutorials to complete a specific technical goal or process within a Zoom application.

Expert Insights are practical, technical guides that help technical decision-makers implement and optimize Zoom products and features. These resources bridge the gap between product capabilities and real-world implementation, offering actionable guidance from our own experts who've solved these challenges for our customers.\
\
Each article offers:

* **Technical depth with practical application**: We don't just explain what features do; we show how to use them to solve specific business problems
* **Best practices and troubleshooting tips**: Real-world insights from Zoom technical experts who regularly interact with these solutions across various environments
* **Business context and outcomes**: How technical decisions impact users, operational efficiency, and strategic goals

## Available Insights

***

{% content-ref url="/pages/cnBqfraVTbLk1TnPGLfn" %}
[Working with Different Languages](/business-services/quality-management-explainer/expert-insights/working-with-different-languages-in-quality-management.md)
{% endcontent-ref %}

{% content-ref url="/pages/gfPA3rmIlzuLClkMsKU3" %}
[Zoom Rooms with Custom AV - Getting Started with NDI and Dante](/admin-corner/third-party-integrations/expert-insights/zoom-rooms-custom-av.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/admin-corner/third-party-integrations/expert-insights.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.