> 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-comerciales/zoom-contact-center/expert-insights/configuring-agent-occupied-rules/channel-load-monitoring.md).
# Monitoreo de carga del canal
Los supervisores pueden acceder al Panel de control y a los informes de análisis de CX para ver información completa sobre la carga del canal, ya que estos datos detallados no se muestran en las vistas de estado estándar.
**Lo que los supervisores deben supervisar**:
* Conteo actual de interacción por tipo de canal
* Capacidad restante antes del estado ocupado
* Patrones de utilización específicos por canal
* Eficacia de la regla de Ocupado y oportunidades de optimización
**Mejores prácticas de análisis**:
En lugar de contar simplemente a los agentes "Ready", los supervisores deben:
1. Comprender las reglas de Ocupado configuradas para sus equipos
2. Supervisar la Configuración de capacidad de interacción en distintos perfiles de agente
3. Analizar la distribución de la carga del canal y los patrones
4. Usar análisis exhaustivos para tomar decisiones de dotación de personal y Enrutamiento
---
# 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-comerciales/zoom-contact-center/expert-insights/configuring-agent-occupied-rules/channel-load-monitoring.md?ask=&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.
