> 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/admin-portal/campaigns/lead-summary/advance-filters-lead-summary.md).
# Advance Filters - Lead Summary
In the pipeline lead summary or campaign lead summary, you can filter out leads based on the following criteria
1. Lead details
2. Users
3. Status
4. Stages
5. Tags
6. Creation date
7. Assignment date
8. Contact source
9. Follow up
10. Call attempts
You can also save any specific view that you want to use again and again. for a filter that have to be put again and again to see the details, you can save that view by clicking on the "S**ave Filter**" button
After clicking on the button you can save the filter view with the name you want
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.neodove.com/admin-portal/campaigns/lead-summary/advance-filters-lead-summary.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
