> 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/seguridad-humana/report-button/common-questions.md).

# Preguntas frecuentes

<details>

<summary>¿Qué pasa si un empleado informa un correo electrónico legítimo por error?</summary>

Nada crítico. El informe aparece en tu tabla de Amenazas reportadas con `pendiente` validez, o `falso positivo` si Email Security lo analiza y confirma que es seguro. Fomentar que los empleados reporten de más es más seguro que fomentar que reporten de menos.

</details>

<details>

<summary>¿Puedo ver cuántos informes ha enviado cada empleado?</summary>

Sí. Filtra la tabla de Amenazas reportadas por **Reportante** para ver todos los informes de un empleado específico.

</details>

<details>

<summary>¿Puedo responder al empleado que reportó el correo electrónico?</summary>

Sí. Activa **Notificar a los empleados el veredicto** para que el reportante reciba automáticamente un correo electrónico con tu veredicto. Consulta [Notificación al reportante](https://docs.stoik.io/help/help-center-en-es/seguridad-humana/report-button/reports.md#notifying-the-reporter). Agradecer a los empleados a través de tus propios canales internos (correo electrónico, Slack) también refuerza el comportamiento.

</details>


---

# 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/seguridad-humana/report-button/common-questions.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.
