> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/managers-handbook/dive-into-reports.md).
# Dive into Reports
Analyzing reports is a crucial step in optimizing your customer service and improving the performance of your team. The Analytics section provides valuable insights and data points to help you fine-tune your digital tools.
Do more than count calls and make smarter marketing decisions using the real-time analytics page. LimeCall tracks all metrics, so you can see for certain which of your campaigns are performing well
Your Analytics page keeps track of all your performance metrics, helping your sales team get a holistic picture of how their strategy is playing out.
View the Type of Leads you are getting including:
* Calls
* Forms
* Chats
* Callback
* Webhook
* Messages
* Emails
View Leads By Type and filter the view by date range.
Track the type of lead and view a comparison between channels.
Instantly view Leads by Status, allow your teams to plan and execute sales activity with clear objectives based on real-time data.
View your businesses Conversion Rate, Quote Values and Total Sales, ensuring performance targets are met.
---
# 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.limecall.com/managers-handbook/dive-into-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.