Advanced Search Operators: How to Ask Your CRM a Precise Question

Everyone can use a search box. You type a name, you get the name. The trouble starts the moment your question is bigger than one name: show me every deal worth over 50,000 that no one has touched this month, owned by the north team. A search box shrugs at that. Operators answer it. In ERPnBox, a filter is just three parts — a field, an operator, and a value — and the operator is where the real thinking happens.

You don't write code for any of this. You pick the field from a list, pick the operator, type the value, and the record list updates. This article walks through the operators that matter, with concrete examples, and stays honest to what actually exists in the filter panel.

What is the difference between search and filter operators?

Search scans across records for text you type and hands back matches. A filter operator is a rule applied to one specific field: it decides how the field's value is compared to yours. Search finds a needle; operators describe the needle — its size, its owner, its age — so you can pull out an exact set instead of a lucky hit.

The practical difference is repeatability. A quick search is a one-off. A filter is a question you can save, name, and reopen tomorrow as a view — the same query, refreshed with today's data. That is the whole point: you build the question once and stop rebuilding it every Monday.

How do the text operators — contains, is, and is empty — work?

These three carry most of the daily load. Contains matches any record where the field holds your text somewhere inside it. Is demands an exact match. Is empty finds records where the field was never filled in — the quietest and most useful operator of the three, because gaps are where revenue leaks.

• Contains — Company name *contains* "logistics" returns "Nile Logistics", "Logistics Plus", and "Global Logistics Co" in one pass. Use it when you remember a fragment, not the whole.
• Is — Stage *is* "Negotiation" returns only that stage, nothing adjacent. Use it for clean categories where near-enough is wrong.
• Is empty — Phone *is empty* surfaces every contact you can't call. Pair it with an owner filter and you have a clean-up task list, not a complaint.

How do range and in-list operators handle numbers, dates, and choices?

Numbers and dates rarely want an exact match — they want a boundary. Range operators (greater than, less than, between) let you say "deals above 50,000" or "closing between the 1st and the 15th." For pick-from-a-set fields, in-list matches a record if its value is any one of the several you choose — a tidy way to select three stages or four sources without three separate filters.

Ranges and in-list are where a vague ask becomes a countable list. "Big deals closing soon" is an opinion; "amount over 50,000 and close date within the next 14 days" is a filter you can act on — and hand to a rep without a meeting.

How do owner, team, and date filters scope by people and time?

Some questions are about *who* and *when*, not *what*. ERPnBox gives you filters that resolve to people and periods directly: filter by owner (the record's assigned user), by team, or by who a person reports to — and by date windows like created, modified, or a custom date field. You pick the person or period from a list; the CRM expands it into the right set of records for you.

• Owner filters answer accountability questions: "my open deals," "everything owned by a rep who just left."
• Team filters roll several people into one query so a manager sees the whole desk at once.
• Date filters answer freshness questions: "created this week," "not modified in 30 days" — the classic sign of a stalled pipeline.

A pipeline doesn't rot all at once. It rots one untouched record at a time — and a date filter is the only honest way to see it.

How do you stack filters and save the result as a view?

One filter narrows; several stacked together corner an answer. Add conditions one at a time and each new line tightens the set — field, operator, value, repeat. When the list finally shows exactly what you meant, save it. The saved view remembers every condition and re-runs it on demand with fresh data, so you never rebuild the question.

1. Open a module's list and click into the filter panel.
2. Add your first condition: choose a field, an operator, and a value.
3. Stack more conditions until the list matches your question.
4. Switch view modes — the same filtered set can show as a board, chart, or calendar.
5. Save it as a named view, then reopen it any day for a live answer.

Because a filtered set is just a list of records, you can flip it into a Kanban board to work it as a pipeline, or a chart to count it — the same question, seen a different way. And once your data is this searchable, keeping it clean matters: the duplicate manager makes sure your "count" isn't quietly inflated by the same lead entered twice.

Which teams get the most out of precise filters?

Anyone who works a list. Sales reps save "my deals closing this month" and open it every morning. Sales managers stack owner and date filters to spot stalled pipeline before it dies. Operations use is-empty to find records missing a key field. Support and success filter by status and date to catch what's aging. The operators are the same for everyone — only the question changes.