Saved searches

A saved search stores a visitor’s exact filter set — city or drawn neighbourhood zone, price range, beds, property types, days on market, open-house-only, all of it — under their account on your site, ready to re-run in one tap and wired to daily email alerts. For the visitor it means never rebuilding their search. For you it means knowing, in the CRM, precisely what every registered lead is looking for.

Saving is one tap, everywhere search happens

The save-search button sits in the toolbar of both the listings grid and the map view. A tap stores the current filters with a human-readable name derived automatically — “Oakville · For sale · 3+ bed · under $1,200,000” — so the visitor’s list of searches reads like plain English, not a filter dump. Visitors who aren’t signed in get the account prompt in place; the save completes the moment they finish registering, without losing the filters they built.

Behind the tap, the platform sanitizes what it stores. Only known filter keys persist, junk values are dropped server-side, and neighbourhood-zone searches store the zone reference rather than raw coordinates. That rigour is what lets alert emails re-run the search safely for months.

Managing and re-running searches

Each visitor gets a searches page in their account hub listing every saved search with its creation date, last-alerted date, and an alerts-on badge. “Run search” rebuilds the original URL exactly — zone-scoped searches reopen on the map with the boundary restored, everything else lands on the filtered grid. Alerts are on by default and controlled per search; turning one off stops the emails without deleting the search. The daily alert leg itself — what gets sent, when, and the compliance rules around sold-mode matches — is documented on the listing alerts page.

The CRM side of a saved search

This is where the feature earns its place in a lead-generation stack rather than a convenience list. Saving a search fires an event into the platform’s behavioural plane, and the search itself appears on the person’s record in the CRM — a dedicated saved-searches card on the right rail of every contact, next to their property activity. Your agents see the buyer’s actual criteria, stated by the buyer’s own fingers, alongside which listings they’ve viewed and hearted on the contact timeline.

That combination changes follow-up quality. Instead of “just checking in,” the call opens with the two new listings inside their zone and budget that published this week. The behaviour profiler also reads saved-search filters as intent signals, so search criteria flow into lead scoring rather than sitting in a silo.

Why it belongs on your site, not a portal

Every saved search a buyer creates on a portal is a retention asset for that portal. On your BrokerFold site the same behaviour builds your database: a registered contact, an explicit search intent, a daily email reason to return to your domain, and a behavioural record your CRM can act on. Saved searches ship on every plan as part of the core listing search stack — there is nothing to enable and nothing extra to pay for.