> 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/guide/devices-and-settings/device-specific-controls/buttons-and-keys/sos-button-action.md).

# SOS button action

Configure the SOS button action in Navixy so an SOS press sends an alert, or makes a call to a phone number and sends an alert.

Sets what happens when the device's SOS button is pressed.

## Settings

* **Mode**:
  * **Send alert only**: the device sends an SOS event to the Navixy platform. The event appears in the device's history and can trigger platform alert rules (such as a push notification or email to a dispatcher).
  * **Make call to phone number and send alert**: the device both places a voice call to the configured number and sends the SOS event to the platform.
* **Phone number**: the number to call in the second mode. Use international format (for example, `+12025550100`).

## Availability

Appears on device models that have an SOS button.

## See also

* [Call buttons](/docs/user/guide/devices-and-settings/device-specific-controls/buttons-and-keys/call-buttons.md): map other device buttons to phone numbers.
* [Pressing SOS button](/docs/user/guide/events-and-notifications/safety/pressing-sos-button.md): the platform rule for SOS events.


---

# 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/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.