> 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-5-use-filters-to-spot-high-intent-leads.md).

# Step 5: Use filters to spot high-intent leads

{% embed url="<https://youtu.be/_RDMRIzn_Y8?si=PcLtnPUwS-K9h1q0>" %}

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'** in the accounts page

<figure><img src="/files/QB8EZRGkEvjr9Yqt7AvF" alt=""><figcaption></figcaption></figure>

**Step 2:** Choose the filters to find accounts that match your specific criteria

<figure><img src="/files/JX7DVPFlhiIAPCA4fnsA" alt=""><figcaption></figcaption></figure>

For example - you can select the **'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.

<figure><img src="/files/YzVQgviLpc8CYRnbvKCf" alt=""><figcaption></figcaption></figure>

Similarly, you can use filters to identify relevant developers.

**Step 1:** Go to the developers tab and click on 'add filter'

<figure><img src="/files/agcpCrYcO4AhrdO7TjJ7" alt=""><figcaption></figcaption></figure>

**Step 2:** Choose from multiple filters like designation, location, developer tag and many more.

<figure><img src="/files/XabZXQzNrtulGVLZxiBq" alt=""><figcaption></figcaption></figure>

As an example - you can filter developers based on their designation. This helps you identify potential buyers.

<figure><img src="/files/fvd70oSmzs0luDxrpbfi" alt=""><figcaption></figcaption></figure>

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 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.reo.dev/getting-started/for-users/step-5-use-filters-to-spot-high-intent-leads.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.