> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/analyze/custom-reports-and-dashboards/reports-common-questions/reports-leads/reports-leads-with-scheduled-meetings.md).

# Reports - Leads with Scheduled Meetings

#### With SprintHub, you can filter and customize your Leads and Opportunities reports based on scheduled meetings—whether past, future, or even meetings that were canceled. This way, you can get a complete and organized view of the history of interactions with your leads.

{% hint style="info" %}
This filter is available as a condition in the automations of the **SAC 360º**, **CRM**, **Automation Flows** and **Chatbot**, allowing you to direct specific actions based on custom criteria during the lead or service journey.
{% endhint %}

To do this, follow the steps below: 

1. Access the Reports feature through the **“Find Services”**. Or just type the name, and the function appears.

Start creating: Click on "+ New".

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdKgFdtZGdFRjiuW-jmLlxLG1vybYZPHvFydNgh3t0icQwy3ZSD9cIlHCx3FKobT0HNB2-A1xn_3VzZKZMDCB-CExLEQ0Wvk9vlKvuDDTEPm7LNCErqpt3fWZCPLqTKdGkYOL9GMg?key=V5heKEuPm1b2w75CYXOzPg" alt=""><figcaption></figcaption></figure>

2. Creation of the Custom Report.

{% embed url="<https://youtu.be/Kc_AAfAUh8E>" %}

**CONCLUSION**

Using meeting filters in reports allows for more strategic and efficient tracking of interactions with your leads and opportunities. In this way, you ensure precise control over the scheduling history and can make more assertive decisions to optimize your sales results.


---

# 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.sprinthub.com/en/topics/analyze/custom-reports-and-dashboards/reports-common-questions/reports-leads/reports-leads-with-scheduled-meetings.md?ask=<question>&goal=<endgoal>
```

`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.