Pik-a-Search is the structured filter tool inside BNTouch that turns the CRM from a list of records into a queryable database. Every database (mortgages, partnerships, recruiting) exposes the same Pik-a-Search interface. Each filter is one criterion (borrower first name, property state, loan purpose, status, custom fields). Combine multiple filters and the system narrows results to records matching every criterion. The most powerful operational features are saved reports, scheduled email reports, and bulk actions you can perform on result sets without leaving the search screen.
“These databases can be easily opened using the tabs at the top of the page” [lTg9k07fVgg m1]. Pik-a-Search exposes itself on every database tab (mortgages, partnerships, recruiting). Open any tab, find the Pik-a-Search icon at the top, and the structured filter screen opens against that database.
How a filter works
“Each of these lines is a filter that you can use to search for records in the selected database” [lTg9k07fVgg m2]. So a filter is one row on the search screen with a field selector, an operator (where applicable), and a value input.
“For example, the borrower first name filter allows you to search records by the name of the client. Whatever you enter in the text box will be looked for in the corresponding field of your records” [lTg9k07fVgg m2]. So a borrower first name filter with “John” returns every record where the first name field contains “John.”
Combining multiple filters
The power is in stacking filters. “As long as you have at least one filter with text to look for in the text box, you can click the search records button above or below to start the search” [lTg9k07fVgg m3]. So you can run a single-filter search (any borrower named John) or stack as many filters as needed (borrowers in Texas with a purchase loan purpose and active status).
One operational detail. “Click the search records button even if they aren’t on the screen anymore. For example, if you use the property state field to look for properties in Texas, then use the loan purpose equals purchase filter, you can click [search and the system applies all set filters]” [lTg9k07fVgg m4]. So filters stay applied across the session even if you scroll them off-screen. The state filter you set five minutes ago is still in effect when you add a sixth filter.
The criteria persistence behavior
One under-named feature most teams discover by accident. “Whenever you open the Pik-a-Search tool, you will see the same criteria and results from the last search you made” [lTg9k07fVgg m5]. So the search remembers your last query. When you come back later in the day to refine the same search, you do not start from a blank state.
For repeating searches, this is convenience. For complex searches you intend to keep using, the better workflow is saving the search as a named report.
Saving searches as reports
“Once saved, you can quickly bring up the same search filters by clicking load report” [lTg9k07fVgg m6]. So a search you build today (e.g., “past borrowers, 18-36 months from funding, rate above 6.5%”) can be saved with a name and reloaded later. The next time you want that exact list, you click load report and the filters populate automatically.
Scheduled email reports: the magic feature
The single most useful operational pattern with Pik-a-Search. “Alternatively, if you want the results of a search to be sent to you regularly, you can click the save as menu and choose create scheduled email report” [lTg9k07fVgg m6]. So you can convert any saved search into a recurring email that lands in your inbox on a schedule (daily, weekly, monthly).
Real example. A branch manager sets up a scheduled report: “Every Monday at 7am, send me a list of every borrower currently in the preapproved status who has been there more than 90 days.” The Monday email arrives with the borrower list. The branch manager triages immediately. No manual search every week.
Bulk actions on result sets
The other operational power of Pik-a-Search. Once you have a result set, you can take bulk actions without leaving the search screen. From the demo:
Tracker report: “Tracker report will let you see all tracker events that have been created for the selected records” [lTg9k07fVgg m7]. Click a checkbox on each result, hit tracker report, see the aggregate activity log.
Bulk reassignment: “The assign records button will show a list of your crm users who you can then assign the selected records to” [lTg9k07fVgg m8]. Reassign 50 borrowers to a different LO in one action.
Move records / change marketing stage: “Move records can be used to change the marketing sequence stage for the selected records or to change the groups assigned to the records” [lTg9k07fVgg m8]. Bulk-change stage for a cohort.
Combine duplicates: “Combine them into a single record, copy the information to both records, or simply import the selected information into either of the records and leave the other untouched” [lTg9k07fVgg m9]. Merge duplicates surfaced by the search.
CSV export: “Backup purposes, you can use the download page in CSV or download full search in CSV buttons to save them in a spreadsheet file” [lTg9k07fVgg m10]. Pull the result set out of BNTouch for external analysis.
Customizing result columns
The result screen is customizable. “You can add more columns using the add fields button below, change the data for a column using the drop-down menu, or decrease the number of columns shown” [lTg9k07fVgg m11]. So the default columns the system shows are not the only ones available. If you need to see custom fields, rate locks, or co-borrower info in the result list, add the columns directly.
A specific scenario: weekly refi opportunity audit
A loan officer sets up a Monday morning routine using Pik-a-Search:
Open mortgages tab, Pik-a-Search. Build the filter set: status equals past borrower, rate is greater than 6.75%, LTV is less than 80%, last contact date is more than 90 days ago.
Click DB check via the trigger interface (or just search records) to see the result count. 47 borrowers.
Click save as menu, choose create scheduled email report. Configure: send every Monday at 7am, deliver to the LO’s email address, format with the company branding and a brief summary.
Every Monday morning thereafter, the LO opens email and sees the 47 (or whatever the current number is) borrowers fitting the refi opportunity profile. Triage immediately.
Time invested once: 12 minutes to build the search and configure the scheduled report. Time saved each week: roughly an hour that would otherwise go to manually pulling the list.
Saved-search-as-trigger crossover
Worth knowing for power users. A saved Pik-a-Search query can effectively serve the same function as a campaign trigger if you build the trigger combination correctly. The Pik-a-Search version is for manual periodic review; the campaign trigger version is for automatic enrollment. Use both for the same logical cohort: triggers to auto-add borrowers to a campaign as they become eligible, scheduled reports to surface the cohort for human review weekly.
Honest limits
Pik-a-Search uses field values at search time. If a borrower’s status field has not been updated since their last activity, the search returns them based on the stale field value. Field hygiene matters.
Showing more records per page slows the page load. “Showing more records per page may take longer for your browser to load the [results]” [lTg9k07fVgg m10]. For result sets over 500 records, expect a noticeable wait; export to CSV instead of paginating through hundreds of pages.
Scheduled reports send what the search returns at run time. If a borrower newly meets the criteria between scheduled sends, they appear in the next email. If they leave the criteria, they drop off. The report is a snapshot, not a running list.
Bulk actions can be destructive. The merge and delete actions are powerful and not undoable. Double-check the selected record set before confirming.
Set up your first Pik-a-Search scheduled report
To walk through building a multi-filter search and converting it to a scheduled email report on a sandbox account, request a demo. The mortgage CRM page covers the underlying database engine.
