> For the complete documentation index, see [llms.txt](https://help.quickappflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.quickappflow.com/product-guides/field-sales/my-visits.md).
# My Visits
To check all the visit details, click on **My Visit**
To review all the details of the scheduled site visits for that date, click on **My Visits**
In the **My Visit** list, check the start time, end time, and total time spent on the site visit
On the My Visit page you can check the **customer name**, **customer route**, **address**, and total **order amount**
## Location
To view the customer location, click on the **location** icon
You can check the customer's **Location**
## Visit Details
To check the site visit, click on the right **Arrow** icon
Check all the details for the visited customer site.
## Visit history
Click on the **View** icon to check the visit history
On the Visit history page, in the **Visit** tab, you can view all the details for visited **customer**.
On the **Visit history** page, in a **direct** tab, you can view all the details for the direct order of the customer
---
# 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://help.quickappflow.com/product-guides/field-sales/my-visits.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.