> 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/other/sms-channel-usage.md).

# Penggunaan saluran SMS

Konfigurasikan cara perangkat GPS menggunakan saluran SMS-nya di Navixy dengan blok penggunaan saluran SMS, termasuk mode peringatan baterai lemah.

Memilih Pesan mana yang hanya dikirim perangkat melalui saluran SMS, bukan melalui koneksi data seluler (GPRS). Ini berguna saat data seluler tidak tersedia atau tidak andal, misalnya di area dengan cakupan lemah.

{% hint style="info" %}
Mengaktifkan pengiriman SMS untuk suatu jenis Pesan meningkatkan jumlah pesan SMS yang dikirim perangkat, yang dapat menimbulkan biaya tambahan bergantung pada paket SIM.
{% endhint %}

## Pengaturan

Blok ini menampilkan daftar jenis Pesan yang dapat dikirim melalui saluran SMS. Opsi yang tersedia bergantung pada model perangkat. Opsi yang paling umum adalah:

* **Baterai rendah**: kirimkan peringatan baterai lemah melalui SMS.

## Ketersediaan

Muncul pada model perangkat yang menampilkan opsi saluran SMS.


---

# 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/other/sms-channel-usage.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.