> For the complete documentation index, see [llms.txt](https://docs.salesmania.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salesmania.id/app-guidebook/daftar-dan-history-customer.md).
# Daftar dan History Customer
## **Melihat Daftar Customer**
* Masuk ke bagian customer → klik tombol 
* Semua data customer akan tampil dan sales bisa melihat detail dari customer tersebut (nomor telepon dan alamat) dengan klik nama customer
## **Melihat Customer Detail**
Pada bagian customer terdapat 2 history yaitu **Visit History** (melihat kunjungan sales kepada customer) dan **Order History** (melihat data orderan dari customer)
Tim dapat mencari history sebelumnya dengan tombol 🔍 sehingga memudahkan mereka menemukan history yang diinginkan dengan cepat
## **Melihat Histori dan Informasi Customer**
Semua modifikasi pada customer akan direkam dalam catatan riwayat (history), sehinga tim sales dengan mudah melacak setiap perubahan yang terjadi pada customer tersebut
Untuk melihat histori produk, Anda dapat klik tombol di ujung kanan detail customer
Kemudian, tombol untuk melihat informasi customer dan pembatasan piutangnya
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.salesmania.id/app-guidebook/daftar-dan-history-customer.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.