Saved Search Surface

Retrieve and manage real saved searches without the legacy HTML fragment loader.

This surface replaces the old `ajax_SavedSearch.php` branch with a typed contract, direct database reads, and the same save endpoint already used by listing-search and building-detail.

Library

Sign in to view saved searches

The saved-search library is tied to account state, so guests enter through the shared auth overlay first.

Go To Listing Search

Saved searches require account context.

Use the shared overlay to sign in, then reload this page to retrieve the latest saved-search records from `bhb_savedsearch`.

Current flow

Direct sign in opens the shared account panel without a follow-up action.

Email Password

By continuing, you agree to our Terms of Service and Privacy Policy.

First name Last name Email Password

When the user is a guest, this save flow should hand off to sign in and then return here automatically.

Pending Search

Name this search

Search locations will appear here from listing and building surfaces.

Filter summary will appear here.

Search name Alert frequency

Guests should authenticate first, then come back to the same listing-save intent.

Pending Listing

Choose a home to save

Listing context from cards and detail pages will appear here.

Price on request

Save this listing

Add the home to your saved list and keep it available for future comparisons across web and mobile.

The listing-detail flow currently requires sign in before it can resume the tour request and collect any missing phone information.

Pending Tour

Choose a tour time

The listing-detail surface will pass the selected tour type, date, and time here before auth.

Request a tour

This intent stands in for the legacy `LD_showingrequest` flow. After auth, the page should resume the selected date, time, and appointment request state.