> 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/quick-start/about-service-providers.md).

# Tentang penyedia layanan

Penyedia layanan menangani penyediaan, pemasangan, dan dukungan perangkat keras GPS untuk Navixy. Hubungi mereka dari bagian Bantuan bawaan di aplikasi web atau seluler.

Penyedia layanan adalah mitra langsung Anda untuk layanan telematika GPS. Mereka menangani pasokan perangkat keras, instalasi, dan konektivitas, serta menyediakan dukungan lokal untuk penyiapan, pemecahan masalah, dan pertanyaan apa pun terkait platform Navixy.

Penyedia layanan juga dapat menyesuaikan platform Navixy dengan kebutuhan regional Anda. Kehadiran lokal mereka memungkinkan waktu respons yang lebih cepat dan dukungan khusus wilayah.

## Mendapatkan bantuan

Di **Bantuan** di bagian antarmuka Web dan aplikasi X-GPS Mobile, Anda dapat langsung menghubungi tim dukungan penyedia layanan Anda untuk mendapatkan bantuan. Selain itu, bagian ini menyediakan dokumentasi bawaan tempat Anda dapat menemukan jawaban atas pertanyaan Anda dan petunjuk penggunaan perangkat GPS.


---

# 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/quick-start/about-service-providers.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.
