> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/filter-and-scroll-contacts.md). # Filter & Scroll Contacts December 30, 2022 - Easily filter and scroll through contacts! {% embed url="" %} Have you ever added filters to your contacts, opened a profile and gone back to the list of contacts only to find you’ve lost your filters? We have, too! Rechat is introducing a new feature to help make filters easier to use and navigate! Now, members can apply filters to their contacts, open a contact profile and while in a contact profile, scroll to the next or previous contacts, or close the current profile and return right back to your filtered list. This allows members to prospect, follow-up and communicate with a set of contacts quickly and efficiently. Looking to clear the filter? Easy! Simply click the “X” on the filter you wish to remove, and Rechat will return you to the appropriate audience of contacts. We hope you love this latest improvement to Rechat as much as we do. Remember, support can always be found in the lower left corner of your screen, or by emailing . --- # 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://help.rechat.com/whats-new/filter-and-scroll-contacts.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.