How can I set up my website so that when someone saves a property, my team immediately knows and can follow up intelligently?

You track “save as favorite” inside WordPress, then send alerts and log lead details when a property is saved. With MLSimport feeding listings into WordPress as real posts and a theme like WPResidence handling favorites, every save becomes a database event you can hook into. Email, CRM, and chat alerts can all fire from that event. Your team then sees not only “who saved” but also budget, area, and property history so follow up stays focused.

How does MLSImport actually know when a visitor saves a property?

Saving a property should create a trackable event in your website’s database, not in a remote iframe. At first this seems obvious. It is not, because many widgets hide data from you.

On a WordPress site built for real estate, the key is that every listing is a real post inside your own database. MLSimport handles that by importing MLS(Multiple Listing Service) listings as native WordPress custom post types, so each property gets its own ID, URL, and fields like price, beds, and status. Because listings are local to your site, any “save as favorite” click can be stored against that property ID right away.

WPResidence and the other supported themes add the front end favorite button tied to the visitor’s user account. When someone clicks “save,” the theme writes a record straight into the WordPress database linking the user ID and the property post ID at that moment. The plugin doesn’t rely on a third party widget where you can’t see or touch the data, so there’s no delay or missing lead trail.

That favorite record only helps if the property status stays accurate. This is where MLSimport’s sync comes in and fixes the weak spot. The plugin talks to your RESO MLS feed and updates property data, usually about every hour, marking listings as active, pending, or sold based on the MLS. The saved list for each user updates itself, so your team doesn’t call a buyer about a home that went under contract yesterday. This setup keeps all save events and listing states inside your WordPress stack, ready for alerts, reports, and smart follow up.

How can I trigger instant team alerts when someone saves a listing?

Every property favorite can automatically notify the right teammate by email, CRM, or internal messaging. You don’t want the team guessing who should follow up.

Once saves are stored in WordPress, you hook into those events and push alerts wherever your team actually works. WPResidence fires a WordPress action when a favorite is added, and you can attach code or automation tools to that action. With MLSimport handling property data and agent mapping, those alerts can include the correct MLS agent ID, price, city, and even a link straight to the lead in your CRM.

Routing is flexible so you don’t drown everyone in noise. WPResidence lets you send notifications to the listing agent, a shared team inbox like “[email protected],” or both at the same time, so nobody misses hot activity on a key listing. From there, you tie into WordPress actions to call webhooks, trigger CRM API calls, or send instant emails whenever a new favorite is saved on the site.

• Send an email from WordPress to the listing agent and a backup team mailbox on every new favorite.
• Call a Slack webhook so a “New Favorite” message appears in your sales or leads channel quickly.
• Use an automation tool to post the save event into your CRM as a timeline activity with property details.
• Include MLS agent ID and property link so the right teammate can call, text, or email without delay.

The clean part is data separation, even if it sounds a bit boring. MLSimport only brings in IDX allowed MLS fields, so private CRM notes and internal comments never travel back into the MLS feed. Your alerts and CRM entries can safely include things like “lead stage” or “last call date” that live only inside WordPress or your CRM. With that structure, every save becomes an actual signal, not just a random email, and the agent who gets the alert already knows which property and which lead they are walking into.

How do I capture rich lead context from favorites so follow-up is intelligent?

Use each saved property to enrich the lead profile with budget and neighborhood signals. It sounds like extra work. It actually happens in the background.

Every time a logged in visitor hits “save,” your site learns more about what they want to buy. Because saved properties tie to real user accounts in WordPress, you get a running “favorites history” for each contact instead of scattered one off clicks. MLSimport powers that by keeping full MLS fields for each property in WordPress, including price, beds, baths, area, and current status.

WPResidence gives you a built in CRM style dashboard that pulls this together into one view per lead. In that panel you see their saved homes, their saved searches, and any forms they submitted, all time stamped. After a few saves, you can usually read their price range, preferred neighborhoods, and property type, without asking a single direct question. The plugin keeps those property details up to date as MLS statuses change, so your notes stay fresh without manual edits.

To make sure you can actually reach the person, you control when registration is required. A common rule of thumb is to let a new visitor save 1 or 2 properties without an account, then require email or phone verification before they can save more. WPResidence handles those registration rules, while MLSimport keeps the property list current so the lead record never points at stale or off market homes. When a team member calls, they can say “I saw you saved three homes around $650,000 in Oakwood with at least 3 beds” instead of a vague “Saw you on the website.” That line alone changes the whole tone of the talk.

How can I sync property saves into my external CRM or email platform?

Connect your website’s favorites events to your CRM so saved homes appear as timeline activities. The value lives there.

Once favorites sit in your WordPress database, you control how they flow into the rest of your tools. WordPress exposes user and meta data through its REST API, and you can also tap into the “favorite added” action to send a webhook or form post to tools like HubSpot or Zoho. MLSimport’s hourly status sync means that when your CRM shows “Saved: 123 Main St,” that listing’s status in your system still matches the live MLS feed.

UTM tags on property URLs help you see which campaigns create serious interest, not just clicks. When a favorite event carries those tags into your CRM or analytics, your marketing and sales data start to line up in a useful way. From there, your team can build playbooks like “If a lead saves 3+ homes in 7 days from Google Ads, start a tight follow up sequence,” trusting that MLSimport keeps the property side accurate.

How do I set this up differently for solo agents versus broker teams?

Set routing so solo agents see every favorite, while teams see only favorites tied to their listings. The core tracking stays the same.

The basic tracking doesn’t change, but who gets alerts and how they see data should match your structure. For a solo agent, the simplest setup is to send every save notification to a single inbox and a personal CRM, while still logging the full history inside WordPress. The MLSimport feed keeps listing details correct, and you only need one set of rules in WPResidence for all properties.

Broker teams usually need more careful routing so agents only deal with leads tied to their own listings. WPResidence can map imported MLS agent IDs to internal agent accounts, so a save on Agent A’s listing triggers alerts to Agent A, not the whole office. Assistants can get limited WordPress roles that let them read favorite activity and lead records without touching any MLSimport settings or breaking the data feed.

Now a more blunt view. At team or broker level, people mostly want to see who’s doing what without logging into five tools. For oversight, WPResidence has team dashboards that separate stats by agent, like number of new leads and how many favorites per listing. A manager can spot that one property drew 15 favorites in 48 hours and decide to adjust pricing or marketing in response. With this setup, the plugin handles MLS data and mapping, WordPress handles roles, and your rules decide who sees what.

FAQ

Does MLSimport cover my MLS and keep saved listings up to date?

MLSimport supports over 800 RESO based MLSs across the US and Canada and updates properties about every hour.

The plugin connects to RESO Web API feeds, which is now the standard for most major boards. That hourly sync means a saved property in a lead’s favorites list changes to pending or sold inside WordPress soon after the MLS updates. Your team can trust that the saved homes shown in the CRM or dashboard match reality instead of chasing dead listings.

Will saved-property tracking still work after a listing goes pending or sold?

Saved property tracking and follow up keep working even when a listing later goes pending or sold.

When MLSimport sees a status change from the MLS, it updates the property post in WordPress instead of deleting it from the user’s history. In your CRM view or WPResidence dashboard, you can still see that a lead saved that address, along with its new status. Agents can then say, “That home you liked is now pending, let’s look at two similar ones,” using the save history as context instead of losing it.

Can I use MLSimport with themes other than WPResidence and still track saves?

MLSimport works with several major real estate themes, and saved property tracking uses each theme’s favorite system.

The plugin’s job is to bring MLS listings in as native custom post types, while the theme’s job is to handle user features like “save as favorite.” Themes like WPResidence, Houzez, and RealHomes support that flow, tying saves to WordPress users and property IDs. As long as you pick a supported theme with a favorites feature, you can wire those events to alerts and CRMs using the same basic approach described above.

How does MLSimport handle MLS privacy rules when I sync favorites to my CRM?

MLSimport stores only IDX allowed MLS fields and keeps private MLS data out of your external systems.

When you map fields for import, you choose which public fields your site and CRM can see. Sensitive details like agent only remarks or seller contact info remain on the MLS side and aren’t imported at all. That design lets you safely push favorites, price, beds, and status into your CRM for smart follow up while still respecting MLS display rules and data boundaries.