> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/es/guide/devices-and-settings/device-specific-controls/buttons-and-keys/sos-button-action.md).

# Acción del botón SOS

Configure la acción del botón SOS en Navixy para que una pulsación de SOS envíe una alerta o haga una llamada a un número de teléfono y envíe una alerta.

Define qué sucede cuando se presiona el botón SOS del dispositivo.

## Configuración

* **Modo**:
  * **Enviar solo alerta**: el dispositivo envía un evento SOS a la plataforma Navixy. El evento aparece en el historial del dispositivo y puede activar reglas de alerta de la plataforma (como una notificación push o un correo electrónico a un despachador).
  * **Realizar una llamada al número de teléfono y enviar una alerta**: el dispositivo realiza una llamada de voz al número configurado y envía el evento SOS a la plataforma.
* **Número de teléfono**: el número al que llamar en el segundo modo. Use el formato internacional (por ejemplo, `+12025550100`).

## Disponibilidad

Aparece en modelos de dispositivos que tienen un botón SOS.

## Ver también

* [Botones de llamada](/docs/user/es/guide/devices-and-settings/device-specific-controls/buttons-and-keys/call-buttons.md): asigne otros botones del dispositivo a números de teléfono.
* [Pulsar el botón SOS](/docs/user/es/guide/events-and-notifications/safety/pressing-sos-button.md): la regla de la plataforma para eventos SOS.


---

# 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://navixy.com/docs/user/es/guide/devices-and-settings/device-specific-controls/buttons-and-keys/sos-button-action.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.
