Idea Transcript
(http://close.io/) support center (/)
Have a Question? Ask here.
SUPPORT HOME (/) > SEARCH, FIELDS, AND STATUSES (/CUSTOMER/EN/PORTAL/TOPICS/373404-SEARCH-FIELDS-ANDSTATUSES/ARTICLES)
RELATED ARTICLES
> SEARCH SYNTAX: COMBINED Search overview (/customer/en/portal/articles/965940search-overview)
QUERIES
Search syntax: combined queries
Smart Views (/customer/en/portal/articles/965941smart-views)
This is an in depth look at searching using multiple terms; make sure you’ve brushed up on your single query (https://help.close.io/customer/en/portal/articles/1564202-search-syntax-single-queries-) search knowledge beforehand. If you are just getting started, go here (https://help.close.io/customer/en/portal/articles/965940-searchoverview).
Calling workflows (/customer/en/portal/articles/1832250calling-workflows) Search syntax: single queries (/customer/en/portal/articles/1564202search-syntax-single-queries-)
Operators (and, or, not)
Finding contacted leads (/customer/en/portal/articles/1174020finding-contacted-leads)
When searching for leads that match multiple conditions, we can simply specify them one after another, in any order:
Sort doesn't work for certain fields (/customer/en/portal/articles/1751980sort-doesn-t-work-for-certain-fields)
city:"New York" calls > 0 calls > 0 city:"New York"
Renaming custom field choices (/customer/en/portal/articles/1831956renaming-custom-field-choices)
These two queries are equivalent and will find leads with at least one call and where the city field matches New York.
Custom fields (/customer/en/portal/articles/1104820custom-fields)
For more advanced queries, use the operators and, or, and not.
Organization settings, statuses, & customizations (/customer/en/portal/articles/964828organization-settings-statusescustomizations)
The operator and matches if all conditions are true. This operator is always implied (and therefore optional). We can make the search from above more readable by making the implied and more explicit: city:"New York" and calls > 0 The or operator matches if at least one of the conditions is true:
Lead assignment (/customer/en/portal/articles/1116648lead-assignment)
city:"New York" or city:"San Francisco"
Lead Status mistakes to avoid (/customer/en/portal/articles/2437166lead-status-mistakes-to-avoid)
This finds leads that are either in New York or in San Francisco. The not operator negates the query that follows immediately after it:
The Best Smart Views for High Volume Calling Teams (/customer/en/portal/articles/2728072the-best-smart-views-for-high-volumecalling-teams)
not city:"San Francisco" and state:CA state:CA and not city:"San Francisco” Both queries match leads where the state is California, but the city is not San Francisco.
The Best Ways to Use and Customize Opportunities (/customer/en/portal/articles/2732381the-best-ways-to-use-and-customizeopportunities)
Another way to say 'or' A lot of ors in a search can slow things down:
How do I reduce the number of smartviews I have? (/customer/en/portal/articles/2759446how-do-i-reduce-the-number-ofsmartviews-i-have-)
state:ME or state:NH or state:MA or state:RI or state:CT or state:NY or state:NJ or state:DE or state:MD or state:VA or state:NC or state:SC or state:GA or state:FL If you want to find leads that match a variety of different values for a single field, you can ditch the ors and format them like this:
Time zones and local time (/customer/en/portal/articles/2770056time-zones-and-local-time)
state in (ME, NH, MA, RI, CT, NY, NJ, DE, MD, VA, NC, SC, GA, FL)
Search query examples (/customer/en/portal/articles/2895597search-query-examples)
Now your search will process faster (and it's easier to read too).
Grouping using parentheses When using different operators, parentheses can be used to group the query: not city:"San Francisco" and not city:"New York" not (city:"San Francisco" or city:"New York") These two queries are equivalent and show all leads that are not from San Francisco and not from New York. When mixing and and or operators, parentheses should always be used to clarify the meaning of the query: contact_name:john and (city:"San Francisco" or city:"New York") (contact_name:john and city:"San Francisco") or city:"New York" The first search will match leads with a contact named John and are in San Francisco or New York. The second search will match leads from San Francisco with a contact named John…and any lead from New York.
Nested object grouping You can create searches that match objects that are nested in the lead (emails, calls, opportunities, contacts, etc). Let's say we want to find leads with won opportunities that are worth more than $100: opportunity_status:won and opportunity_value > $100 This seems like it should work. However, this query is actually looking for leads with any won opportunity and any opportunity where the value is greater than $100. In addition to pulling in leads with won opportunities that are worth more than $100, you’ll get some other results. A lead with a $200 lost opportunity and a $50 won opportunity would match too. To create more targeted searches, you’ll need to use nested grouping. Nested grouping allows you to limit multiple search conditions to a specific nested object. Put another way, nested grouping allows you to combine multiple search questions (“Does the lead have a won opportunity? Does the lead have an opportunity worth more than $100?”) into one more specific question (“Does the lead have a won opportunity that’s worth more than $100?”).
Building a nested object search Provide the name of the object type (contact, task, opportunity, call, note, email, etc.) followed by parentheses: opportunity( ) Inside the parentheses put the object-specific query: opportunity(opportunity_status:won and opportunity_value > $100) You can remove the object type prefix (opportunity) inside the parentheses to make the query more compact and readable: opportunity( status:won and value > $100 ) Now we get what we originally wanted: leads where both conditions match on a specific opportunity.
Examples We want to see all leads that have calls made by John which were longer than 30 seconds and contained the text “happy” in the call note: call( note:happy by:John duration > 30s ) Since happy is in the parentheses following call, happy will only be searched for in call activities. Leads that only have happy appear in other object types (like a note or an email) won’t match. Since happy won't trigger a match outside of a call activity, we can just use full text search inside the query: call( happy by:John duration > 30s ) Let's try another one. This query matches leads who have replied to our template "Initial Outreach" sent by John during the first week of April: email(direction:sent template:"Initial Outreach" user:John sent >= 2014-04-01 sent