> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/help/help-center-en-es/mdr/management/priority-contacts.md).

# Contactos prioritarios

Configure sus contactos prioritarios para que nuestro equipo pueda comunicarse con usted rápidamente cuando una alerta MDR requiera su intervención directa.

## Cuando se requiera su acción

Stoïk se encarga del análisis y del procesamiento de las alertas de seguridad, pero algunas situaciones requieren su intervención directa. Por ejemplo:

* Reformatear una estación de trabajo tras una infección confirmada
* Verificación por el SOC: por ejemplo, si el usuario X está usando una herramienta Y no listada, le pediremos que confirme su legitimidad
* Alerta de Active Directory: si se detecta una cuenta comprometida, debe activarse un plan de respuesta a incidentes siguiendo nuestras recomendaciones (apagado de la red, deshabilitación de cuentas VPN, etc.)

## Configuración de contactos prioritarios

Introduzca sus contactos prioritarios en `Configuración` > `Usuarios`. Para la configuración completa, consulte [Derechos de usuario y notificaciones](/help/help-center-en-es/incorporacion/account/users.md#user-rights-and-notifications).


---

# 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://docs.stoik.io/help/help-center-en-es/mdr/management/priority-contacts.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.