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

# Tindakan tombol SOS

Konfigurasikan tindakan tombol SOS di Navixy agar penekanan SOS mengirimkan peringatan, atau melakukan panggilan ke nomor telepon dan mengirimkan peringatan.

Menetapkan apa yang terjadi saat tombol SOS pada perangkat ditekan.

## Pengaturan

* **Mode**:
  * **Kirim peringatan saja**: perangkat mengirim peristiwa SOS ke platform Navixy. Peristiwa tersebut muncul di riwayat perangkat dan dapat memicu aturan peringatan platform (seperti notifikasi push atau email ke petugas dispatcher).
  * **Lakukan panggilan ke nomor telepon dan kirim peringatan**: perangkat sekaligus melakukan panggilan suara ke nomor yang dikonfigurasi dan mengirim peristiwa SOS ke platform.
* **Nomor telepon**: nomor yang akan dihubungi pada mode kedua. Gunakan format internasional (misalnya, `+12025550100`).

## Ketersediaan

Muncul pada model perangkat yang memiliki tombol SOS.

## Lihat juga

* [Tombol panggilan](/docs/user/id/guide/devices-and-settings/device-specific-controls/buttons-and-keys/call-buttons.md): petakan tombol perangkat lainnya ke nomor telepon.
* [Menekan tombol SOS](/docs/user/id/guide/events-and-notifications/safety/pressing-sos-button.md): aturan platform untuk peristiwa 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/id/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.