Saved homes
The BrokerFold Team — Product + Engineering
Last reviewed
Saved homes are the quiet workhorse of a buyer’s search: the heart icon that turns browsing into a shortlist. On a BrokerFold site every listing card and detail page carries one, a tap files the property under the visitor’s account, and the list follows them across devices, sessions and weeks. Simple for the client — and quietly one of the most useful intent signals your website can hand you.
Hearting works everywhere listings render
Consistency is what makes a favourites feature get used. The save control rides every surface a listing appears on: the search grid, map results, listing detail pages, and the curated listing bands your template shows on the home page. Each template themes the heart to its own palette, but the behaviour is identical everywhere — one tap saves, a second removes, and the state stays in sync across surfaces because it is one list behind them all.
For a visitor who is not signed in, the heart is the invitation: the account prompt opens in place and the save completes the moment registration finishes, without losing their spot. That moment-of-intent gating is the same pattern the whole visitor account layer uses — friction spent exactly where the visitor wants something.
The saved-homes page is a working shortlist
Inside the account hub, saved homes render as full listing cards — photos, price, beds and baths, status — not a bare list of addresses. That matters because a shortlist is a working document: buyers revisit it to compare, cull, and share the survivors with a partner. When a saved listing’s status changes on the board feed, the card reflects it on the next sync, so the list stays honest about what is still available rather than fossilizing into a museum of gone homes.
The list also feeds action. The viewing-request dialog can draw directly from saved homes, letting a client bundle several favourites into a single tour request with exact preferred times — the Saturday-afternoon shortlist trip, arranged in one step inside their client portal.
What a heart tells you
On your side of the glass, every save lands on the person’s record in the CRM. Hearts appear on the contact timeline alongside listing views and saved searches, and the behaviour profiler reads them as high-grade intent: a saved search describes what a buyer says they want, while saved homes show what they actually stop for. The gap between the two is often the interesting part — the client whose search says “detached under $1.4M” but whose hearts are all semis near a subway line has told you something worth knowing before the next showing day.
Saves also sharpen follow-up timing. A burst of hearts in one evening reads very differently from one save a month, and the profiler folds that cadence into lead scoring, so your call list surfaces the buyer who just shortlisted four properties tonight rather than sorting alphabetically.
Nothing to configure
Saved homes ship on every plan and every template, wired into the same account layer as listing alerts and saved searches — one registration unlocks the lot. There is no setting to enable and no add-on to buy; if your site serves listings, your visitors can start building shortlists on it today.
Frequently asked questions
Do visitors need an account to save homes?
Yes, and the prompt appears at the exact moment they tap a heart — the save completes right after they finish registering, so the friction lands where motivation is highest. That trade is the point: the visitor gets a persistent list, you gain a CRM contact with demonstrated taste.
Can a client book viewings from their saved homes?
Yes. The viewing-request flow can pull from their saved list, so a weekend shortlist of several homes goes out as one request with their preferred times instead of separate forms per property.
Keep reading
- Visitor accounts Free consumer accounts on your own domain — favourites, saved searches, sold data and chat, with every registration becoming a consented CRM contact.
- CRM timeline One stream per person: notes, calls, emails, forms, and live website behaviour — the BrokerFold CRM timeline that briefs you before every call.
- Client portal What a client portal includes on a BrokerFold site: saved homes, saved searches, sold data, messages, and tour requests — all on your own domain.
- Listing alerts How BrokerFold listing alerts work: daily new-match emails from a visitor's saved search, on your domain, feeding your CRM instead of a portal's.