> 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/workforce-management-integration.md).

# Workforce Management (WFM) Integraciones

{% hint style="info" %}
Esta sección es relevante para las cuentas que actualmente usan Zoom Workforce Management (WFM).
{% endhint %}

Con las Reglas de Ocupado, los agentes pueden Mostrar como "Ready" incluso mientras trabajan activamente en las interacciones; simplemente aún no han alcanzado su umbral de ocupado. Esto al principio puede preocupar a los equipos de WFM que esperan que los agentes ocupados se muestren como "Ocupado."

### <mark style="color:azul;">Zoom Workforce Management (WFM) Configuración de conformidad</mark>

**Requisito crítico de configuración**: En sus Preferencias de Workforce Management (WFM) de Zoom, navegue hasta la pestaña de tab de Asignación del estado del agente. La actividad "phone" (y otras actividades similares) debe asignarse para que corresponda tanto con los estados de agente "Ready" como con "Occupied".

**Por qué funciona:**

* Los agentes mantienen la adherencia al Programar ya sea que estén Listos o Ocupados
* WFM rastrea el cumplimiento en función del mapeo de actividades, no solo del estado
* Esta configuración tiene en cuenta el modelo de capacidad matizado que Habilitar las Reglas Ocupadas


---

# 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/workforce-management-integration.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.