> For the complete documentation index, see [llms.txt](https://docs.neodove.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neodove.com/neodove-web-application/my-reports.md).
# My Reports
{% hint style="success" %}
A report is a **document** that provides information about your **effective work history**.
{% endhint %}
### Let's explore how to check the reports:
***
1. **Log in** to your NeoDove web application.
2. Navigate to the left-hand side of the screen, and at the bottom, you'll find the "**My Report**" option. Click on that to access the **desired report** for the user.
### Two main types of Reports are available :
***
* **Login Reports:** Login reports typically present a comprehensive activity report of a particular user for a specific day.
* **Call Reports:** A call report typically displays the overall productivity report of a specific user, including total talk time, the total number of calls made, and other relevant details.
{% hint style="success" %}
**Note:** On the left-hand side of the screen in the report section, there is a **filter option** for the 'date' or a 'calendar' option. Use this to check your **reports** based on the **specific date** you choose.
{% endhint %}
---
# 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.neodove.com/neodove-web-application/my-reports.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.