> 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/website-guidebook/visit-per-periode.md).
# Visit per Periode
Monitoring aktivitas tim sales dalam satu periode
Visit per Periode sangat berguna untuk hal-hal berikut:
1. Performance review mingguan atau bulanan
2. Planning kunjungan tim sales dalam satu periode
3. Overview perkembangan kunjungan ke satu customer
Visit per Periode
* Gunakan drop down di kiri atas untuk memilih **tim** yang ditampilkan.
* Gunakan drop down di kanan atas untuk memilih **periode** yang ditampilkan (1 minggu, 2 minggu, 1 bulan, atau custom)
* Gunakan panah kiri-kanan di tengah atas untuk pindah ke periode sebelum/sesudahnya.
* Gunakan fitur drag and drop untuk memindahkan kunjungan yang belum dilakukan ke hari lain
* Gunakan button 'Salin' untuk menyalin seluruh jadwal dalam periode tersebut ke periode selanjutnya. Tentukan tim sales (bisa tim sales yang sama, tim sales lain, atau beberapa tim sales sekaligus) dan periodenya.
---
# 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://docs.salesmania.id/website-guidebook/visit-per-periode.md?ask=&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.
