> 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/es/servicios-empresarial-avanzados/zoom-node/zoom-chat-hybrid.md).

# Zoom Chat Híbrido

#### <mark style="color:azul;">Zoom Chat Hybrid: Almacenamiento de datos de chat e infraestructura en tus centros de datos</mark> <a href="#r2h3pakzuasl" id="r2h3pakzuasl"></a>

Chat Hybrid permite a los clientes almacenar mensajes de Zoom Chat, metadatos e infraestructura dentro de sus propios centros de datos, ayudando a las empresas a respaldar el cumplimiento de los requisitos regulatorios, de archivo de datos y de retención.

Chat Hybrid incluye capacidades locales de indexación, almacenamiento en caché y almacenamiento en bases de datos para chat en equipo, otorgando a los clientes un control adicional sobre la residencia de datos y las políticas de retención al permitir que los mensajes del usuario se localicen en regiones configuradas. Además, Chat Hybrid se integra perfectamente con controles de políticas, como [barreras de información](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0066037), reforzando aún más el cumplimiento mientras protege la información sensible con almacenamiento local.


---

# 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/es/servicios-empresarial-avanzados/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.