> 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/tr/gelismis-kurumsal-hizmetler/zoom-node/zoom-chat-hybrid.md).

# Zoom sohbet hibrit

#### <mark style="color:mavi;">Zoom Sohbet Hibrit: Sohbet Verilerini ve Altyapıyı Kendi Veri Merkezlerinizde Saklama</mark> <a href="#r2h3pakzuasl" id="r2h3pakzuasl"></a>

Sohbet Hibrit, müşterilerin Zoom Sohbet mesajlarını, meta verilerini ve altyapıyı kendi veri merkezlerinde depolamasına olanak tanır; bu da işletmelerin veri arşivleme, saklama ve düzenleyici gereksinimler için uyumluluk sağlamasına yardımcı olur.

Sohbet Hybrid, şirket içi ekip sohbeti dizinleme, önbelleğe alma ve veritabanı depolama yeteneklerini içerir; kullanıcı mesajlarının yapılandırılmış bölgelere yerelleştirilmesine izin vererek Müşteriler'e veri yerleşimi ve saklama ilkeleri üzerinde ek kontrol sağlar. Ayrıca, Sohbet Hybrid, gibi ilke kontrolleriyle sorunsuz bir şekilde entegre olur [bilgi engelleri](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0066037), yerel depolamayla hassas bilgileri korurken uyumluluğu daha da güçlendirerek.


---

# 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/tr/gelismis-kurumsal-hizmetler/zoom-node/zoom-chat-hybrid.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.