> 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-mobile-application/call-logs.md).
# Call Logs
Monitoring the call logs of a campaign is crucial for **tracking** user activities and interactions in a campaign.
{% hint style="success" %}
It **helps** in analyzing call histories, assessing user performance, and ensuring effective communication with leads.
{% endhint %}
By **reviewing logs**, administrators can gain insights into the overall effectiveness of a campaign, identify areas for improvement, and maintain a comprehensive record of communication for **future reference.**
### Steps:
***
1. **Log in** to your NeoDove mobile application.
2. Select on the **'Call logs'** option from the screen beside the **'Walk-In Leads'** option.
3. Afterward, all incoming and outgoing calls of your agent will **appear**.
{% hint style="success" %}
**Note:** Only for **IVR calls**, incoming logs are generated. For normal GSM calls (**sim-based calling**), only outgoing logs are created.
In the case of **IVR incoming calls**, the log is automatically generated once the call is **answered**, capturing details such as lead information and the corresponding time.
{% 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-mobile-application/call-logs.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.