> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/getting-started/for-users/step-3-use-filters-to-spot-high-intent-leads.md).
# Step 3: Use filters to spot high-intent leads
Filters are a powerful feature that help you narrow your searches by including or excluding specific data related to accounts and developers.
In this article, we will give you a quick overview of the different filters and how to apply them.
**Step 1:** Click on **'Add filter'** on the accounts page
**Step 2:** Choose the filters to find accounts that match your specific criteria
For example - you can select the **'Activity Surge'** filter to identify accounts where there has been a surge in developer activity.
You can also combine multiple filters to easily find high-intent accounts and prioritize outreach.
Similarly, you can use filters to identify relevant developers.
**Step 1:** Go to the developers tab and click on 'add filter'
**Step 2:** Choose from multiple filters like designation, location, developer tag and many more.
As an example - you can filter developers based on their designation. This helps you identify potential buyers.
Once you've identified relevant accounts and developers, you can start reaching out to them.
---
# 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.reo.dev/getting-started/for-users/step-3-use-filters-to-spot-high-intent-leads.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.
