Automate CRM (Elay CRM) Ideas Portal 💡

Your Voice Matters. We value your feedback, feature requests, and ideas — and we take every suggestion seriously to build a better product for you.

"NOT" or "Does Not Contain" filter when building searches

Being able to build searches using a “NOT” or “does not contain” filter would make it much easier to segment people who don’t meet specific criteria.

Customer Priority	2
Customer Challenge Right now, not having a native “NOT” or exclusion filter means we often have to overcomplicate our search queries. In some cases: Searches become harder to build and maintain. Certain criteria - like excluding specific job titles, record ownership, or tags - just aren’t possible to filter out in Elay (unless you select every other option apart from the option you're trying to exclude). Our workaround is to create the search in Vincere (where NOT is a search option), add people to a distribution list or talent pool, and then use that list to filter in Elay. But this approach adds friction: Distribution lists and talent pools are static, so they don’t support “always-on” automations. It takes more time, opens the door to human error, and defeats the purpose of streamlined automation.
Business Case A “NOT” or “Does Not Contain” filter is a standard feature in most search tools and something users expect. Its absence adds unnecessary steps and limits automation. Adding it would align with user expectations, simplify workflows, and improve efficiency with minimal development effort.

Attach files

Enter a subject