How to Best Utilize Propertybase and Salesforce for Real Estate Success
Most brokerages pay for far more of Propertybase than their agents use. This guide sets out the Propertybase best practices that close that gap: clean data, routing that runs itself, follow-up the system owns, offers and closings with an audit trail, reports people trust, and the governance that keeps it working as the firm grows.
Key Takeaways
- Propertybase is a real estate CRM built on Salesforce. Getting full value from it means using what the package already ships before building anything new.
- The biggest gains come from eight areas: data quality, lead routing, listing matching, follow-up, offers and closings, reporting, org governance and agent adoption.
- Salesforce ended support for Process Builder and Workflow Rules on December 31, 2025. Any Propertybase drip or routing automation still built on them should be rebuilt in Flow.
- Lone Wolf says Propertybase is updated every three to six weeks. Test each release in a sandbox, and keep a written owner for every flow, trigger and integration.
- Turn on field history tracking and historical trending now: neither can be backdated, and both are what audits and trend reports depend on later.
Propertybase best practices come down to one idea: use the real estate tools the package already gives you, keep the data clean enough that agents trust it, and let Salesforce run the routine work. Most brokerages we meet are not short of features. They are short of the configuration, data discipline and habits that make those features pay.
This guide is for broker-owners, operations leaders and Salesforce admins at growing and mid-market companies in real estate, from single-office teams to multi-office brokerages. It replaces our 2025 version of this article. Every product detail now links to the vendor's own documentation, the unsourced statistics are gone, and the proof comes from a published Twopir case study.
What Are the Propertybase Best Practices That Matter Most?
Eight habits separate a Propertybase org that pays for itself from one agents work around. Keep one clean record per person and property, route every lead automatically, match listings from the inquiry, let the system own follow-up, run deals through offers and closings, report from the CRM, test every change in a sandbox, and design for how agents actually work.
Use the table as a scorecard. If you recognise the warning sign in the middle column, that row is where your brokerage is leaving value on the table.
| Area | Sign it is under-used | Best practice |
|---|---|---|
| Data | The same buyer exists three times; listing picklists don't match the MLS | Duplicate rules, MLS picklist import, one owner for data quality |
| Lead routing | A coordinator forwards leads by email | Front Desk capture, Lead Router, an escalation flow |
| Listings | Agents search portals in another window | Inquiry matching, Quicksend, saved searches with a frequency set |
| Follow-up | Reminders live in agents' phones | Action Plans, drip campaigns rebuilt in Flow |
| Transactions | Deal status lives in email threads | Offers, Closings, Path, validation rules, e-signature |
| Reporting | Someone rebuilds a spreadsheet every week | Role-based dashboards, subscriptions, historical trending |
| Governance | Nobody knows what a flow does or who built it | Sandbox testing, an automation inventory, audit trails |
| Adoption | Agents keep their own notes and lists | Mobile layouts, in-app guidance, measuring real usage |
What Is Propertybase on Salesforce Today?
Propertybase is a real estate CRM that runs natively inside Salesforce, now owned by Lone Wolf Technologies. It adds real estate records such as inquiries, listings, offers and closings, plus routing, matching and email tools. Because it is native, everything Salesforce offers (Flow, reports, the mobile app, AppExchange apps) works on Propertybase data too.
Lone Wolf acquired Propertybase in 2021 and now offers two products: Propertybase, the Salesforce edition this guide covers, and Front Office, formerly Propertybase GO. On its product page, Lone Wolf says Propertybase is updated every three to six weeks, that its Authentisign e-signature is built in, that workflow automation is "built on Salesforce Flow", and that pricing starts at $89 per user per month with the Salesforce (Force.com) licence included. Confirm current pricing and inclusions with Lone Wolf.
What the 2025 version of this guide got wrong
Several points in our earlier article were inaccurate or out of date. They matter, because each one leads to a configuration mistake.
| The old claim | What is actually true |
|---|---|
| MLS listings sync "every 3–6 weeks" | Three to six weeks is Lone Wolf's package release cadence, not an MLS sync interval. Propertybase documents MLS search and matching through its Propertybase Website integration and publishes no sync frequency. |
| Process Builder powers complex workflows | Salesforce support for Process Builder and Workflow Rules ended on December 31, 2025. Build new automation in Flow and migrate the old. |
| A "Propertybase REST API" for any integration | The documented lead-capture interface is the WebToProspect REST API in Front Desk. Other integrations use standard Salesforce APIs. |
| A custom "Transaction" object for deals | Propertybase already ships Offers and Closings. Extend them rather than building a parallel object. |
| Response and conversion statistics | The old figures had no source, so they are removed. The results quoted in this guide come from one published Twopir case study. |
For the full object model, see our guide to Propertybase Salesforce CRM architecture.
How Do You Keep Propertybase Data Clean Enough to Trust?
Use the packaged records the way they were designed, stop duplicates at the door, and make one person accountable for data quality. When agents find two versions of a buyer or a listing with the wrong status, they stop correcting the data and start working around it. Every other best practice in this guide depends on getting this one right first.
- Use the packaged objects. A contact is a person or company, an inquiry holds what a buyer wants, and every listing creates a matching property record that stays in sync. Keep buyer criteria in inquiry fields rather than free-text notes, or matching has nothing to work with.
- Block duplicates, don't just clean them. Salesforce duplicate management pairs matching rules with duplicate rules that warn or block a user who is about to create a duplicate, and duplicate jobs find the ones already there. Propertybase's Lead Router also sends a returning contact back to its previous owner.
- Match your picklists to the MLS. Propertybase's Importing MLS Field Values tool brings property values from the MLS so your picklists use the same terms. Mismatched values are a common reason matching misses good listings.
- Make required fields required. Website Listings Sync, for example, will not publish a listing without address, city, country, state, price, property type, status and postal code. Enforce those at entry, not at publishing time.
- Migrate history, not just records. If you are moving to Propertybase, load with stable external IDs, agree which duplicate survives before the load, and key listings on the identifier your MLS feed will use afterwards. Our Propertybase data migration page explains why each of those decisions is cheaper made early.
How Do You Get the Most From Propertybase Lead Capture and Routing?
Capture every source as a record, let Lead Router assign it, and add the escalation Propertybase doesn't ship. Leads that arrive by email depend on someone reading them. Leads that arrive as records can be routed in seconds, tracked to the closing they produce, and escalated automatically when nobody picks them up.
Capture: one route in for every source
Front Desk accepts leads through Propertybase webforms, the WebToProspect REST API, and JSON or XML email formats. Connect each portal and website form to one of these, and stamp a consistent lead source on every record. Without a consistent source, you can't answer which portal produces closings.
Route: pick the right distributor per team
Lead Router sets a routing source on the contact, which sends it to a team. Each team's distributor then picks the agent:
| Distributor | How it works | Use it when |
|---|---|---|
| Click to Claim | Every team member is emailed; the first to claim gets the lead | Speed matters more than even distribution |
| Round Robin | Leads rotate through the team in turn | You want a fair share across agents |
| Auto-Assign | Every lead goes to one user | A specialist or an inside sales agent qualifies first |
Agents can opt out while on leave, so routing skips them without an admin change. Alerts reach agents through Chatter in the mobile app, or by text message in North America and Australia when agents opt in.
Escalate: add a clock
Lead Router assigns leads but doesn't chase the ones nobody contacts. A record-triggered flow with a scheduled path can check, a set time after assignment, whether any contact has been logged, then reassign the lead or alert the team lead. Our guide to Propertybase workflows from lead to close walks through that build.
How Should Agents Use Matching, Quicksend and Saved Searches?
Match from the inquiry, send from the same screen, and record what was sent. Propertybase compares an inquiry's criteria with your inventory, lets the agent email a selection with Quicksend, and logs each sent property as a linked listing. That record of what a buyer has seen, and what they thought of it, is what makes the next conversation better.
- Matching both ways. The inquiry's matching screen lists suitable listings; a new listing's matching tab shows which inquiries it fits. Train agents to run the second one every time a listing goes live.
- Linked listings. A linked listing holds a contact's status and feedback on a property, and one action emails everyone linked to it, which is useful when a price drops or a deal falls through.
- Saved searches. Where you have the Propertybase Website integration, MLS Matching creates a saved search with an email frequency of "Never" by default. Add "set the alert frequency" to the inquiry checklist, or clients receive nothing.
- Quicksend. Quicksend sends templated email with inline listings and PDFs to up to 20 recipients. Maintain a small, approved template library rather than letting every agent write their own.
Our article on how real estate firms use Salesforce and Propertybase to boost agent productivity covers these tools from the agent's side.
How Do You Automate Follow-Up in Propertybase Without Losing Control?
Use Action Plans for repeatable tasks, drip campaigns for long-cycle nurture, and Salesforce Flow for everything conditional. Then document each automation with an owner and a test. Automation nobody understands is the most common reason a working Propertybase org becomes risky to change.
Action Plans
Task templates with day offsets, dependencies and assignees. Start from the default buyer, seller, listing and closing plans, then edit them to match how your best agents work.
Drip campaigns
Scheduled email series started from a contact, with an "Automated Email Opt Out" field. Keep opt-outs in one place if you also run a separate marketing platform.
Salesforce Flow
Escalations, reminders before key dates, field updates and notifications. Flow is where all new automation belongs now that Process Builder support has ended.
Fault handling
Add fault paths so a failed flow tells a named admin what broke, instead of emailing whoever last edited it.
Our Propertybase automation service covers routing, follow-up and transaction workflows, including Process Builder migrations.
How Should a Brokerage Run Offers, Closings and Commissions in Propertybase?
Run every deal through the packaged Offer and Closing records, gate each stage with required fields, and keep an audit trail you can show a regulator. An accepted offer creates a closing that copies its data and carries a checklist and commission overview. Path, validation rules and field history tracking turn that into a controlled process.
- Offers and Closings. Offers link a listing with buyer and seller, and hold counter-offers and addenda. Closings carry target and actual closing dates, a closing checklist and a commission overview. Propertybase suggests adding custom fields to closings to calculate commissions and desk-fee deductions; keep split rules in one documented place, not in individual formulas agents can't see.
- Stage gates. Salesforce Path shows the key fields and guidance at each stage. A validation rule can stop a closing moving on until required documents are confirmed.
- E-signature. Lone Wolf states that Authentisign is built into Propertybase. Brokerages on Docusign should check which app their org runs: Docusign says October 16, 2026 was the last day the legacy eSignature for Salesforce app could be used. Our guide to Docusign with Salesforce for real estate covers the current setup.
The audit trail is something you switch on
Our 2025 article said Propertybase "stores a full audit trail". In practice, Salesforce records what you tell it to. Field history tracking logs who changed a tracked field and when, but only from the moment it is turned on, and Salesforce keeps that history for up to 18 months unless you add Field Audit Trail. Turn it on now for offer amounts, closing dates, statuses and commission fields.
Which Propertybase Reports and Dashboards Should Every Brokerage Have?
One dashboard per audience, built from reports that answer a decision someone makes every week. Agents need their own pipeline and tasks, team leads need their office, and the broker-owner needs source-to-closing performance. Deliver them by subscription so nobody has to remember to look, and start historical trending now.
Propertybase's reporting guide frames reports around questions such as "Who should I call today?" and "How quickly do I respond to new leads?". That is the right test for every report you build.
| Audience | Questions the dashboard answers | Built from |
|---|---|---|
| Agent | Who should I call today? Which buyers have gone quiet? | Inquiries, tasks, linked listings |
| Team lead | How fast is first contact? Who has capacity? Which deals are stuck? | Inquiries, activities, offers |
| Broker-owner | Which lead sources produce closings? What will commission look like this quarter? | Contacts, closings, commission fields |
| Listings team | What is active, under offer or stale? What is missing required data? | Listings by status, properties |
| Compliance | Which closings are missing documents or past their target date? | Closings, checklist, field history |
- Subscriptions. Salesforce report subscriptions email refreshed results on a schedule to users, groups or roles.
- Historical trending. Historical trend reports compare up to five snapshot dates across the previous three months plus the current one. They can't look back before data was captured, so switch them on before you need them.
- One component, one report. Propertybase's dashboard guide builds each chart from a single report, so keep report names and folders tidy.
When the numbers exist but nobody trusts them, the cause is usually the data or the sharing model, not the chart. Our page on Propertybase reporting problems explains how we fix the layer underneath.
How Do You Keep a Propertybase Org Healthy as the Brokerage Grows?
Treat the org as a product with an owner, a test environment and a change log. Propertybase releases arrive every few weeks, offices and lead rules change, and admins come and go. Without a sandbox, an automation inventory and regular security checks, every change becomes a risk and upgrades get deferred until they turn into projects.
Test every change in a sandbox
ReleasesBest for: Propertybase package updates, new flows and integration changes.
Salesforce sandboxes are isolated copies of production. Developer sandboxes carry configuration only; a Partial Copy adds a sample of data for user acceptance testing and training; a Full sandbox is a complete replica for staging and load tests. Install each Propertybase update in a sandbox first and run a short script: create an inquiry, route it, match listings, accept an offer, create a closing.
Keep an automation inventory
OwnershipBest for: Orgs that have had more than one admin or partner.
List every flow, legacy Process Builder process, Apex trigger, Lead Router rule and integration on each Propertybase object, with what it does and who owns it. Review it each quarter, and retire automation nobody can explain. Follow Salesforce's Flow best practices: clear descriptions, no hard-coded record IDs, and changes built in a sandbox.
Watch who changes what
Audit & securityBest for: Brokerages with compliance reviews or several people in Setup.
Setup Audit Trail records configuration changes and lets you download the last 180 days, so export it on a schedule if you need a longer record. Security Health Check scores your settings against Salesforce's baseline and can email admins weekly if the score drops.
How Do You Get Agents to Use Propertybase?
Make the system the fastest way for an agent to do their job, on the device they use, and measure the work rather than the logins. Agents adopt tools that save them time in the first week. They abandon tools that add clicks, hide what they need on a phone, or ask them to enter data they never get back.
- Design for the phone. Propertybase runs in the Salesforce mobile app, and its mobile article lists the Admin and Setup menu, the Listing and Contact Manager, the Control Center and inline editing as desktop-only. Build mobile layouts and quick actions for the handful of field tasks: open today's showings, log a call, record feedback, send a listing.
- Teach inside the app. Salesforce In-App Guidance adds prompts and step-by-step walkthroughs to Lightning pages. Most editions include a limited number of active walkthroughs; more need the Enablement add-on.
- Give agents something back. A personal dashboard, matched listings and a task list that runs their day are the return on the data they enter.
- Retire the side spreadsheets. If a manager still keeps a spreadsheet next to the CRM, it shows exactly which number nobody trusts. Fix that number, then retire the sheet.
When Should a Brokerage Add Agentforce to Propertybase?
After the data is clean and the basic automation is reliable. AI drafts follow-up, summarises a client's history and can handle first contact with inbound leads, but it reads the same inquiry and listing data your agents do. On duplicated or stale records, it produces confident answers that are wrong. Routing and stage changes are better left to rules.
Lone Wolf's product page lists "Salesforce Agentforce AI for lead scoring and deal predictions"; ask Lone Wolf what your licence includes. Salesforce's own AI sales agents (Lead Generation, Qualification and Engagement) need Enterprise, Performance or Unlimited Edition with Einstein for Sales. Keep a person approving anything a client reads. Our Agentforce for Propertybase page explains how we prepare the data and guardrails first.
How Do You Run a 30-Day Propertybase Utilization Audit?
Spend one week on each of four questions: what agents actually do, whether the data is true, what the automation does, and what to fix first. The output is a short, prioritised list, not a rebuild plan. Most orgs need a handful of corrections in the right order far more than they need new features.
Our Propertybase optimization team runs this audit as a fixed-scope engagement with written findings in five business days.
What Does Better Propertybase Utilization Look Like in Practice?
A multi-office residential brokerage with more than 120 agents shows the pattern. It had been through two failed CRM implementations. Leads were triaged by hand, MLS data was exported and re-uploaded twice a day, deal progress lived in email, and reports were built weekly in Excel. Twopir Consulting implemented Propertybase on Salesforce in five phases over twelve weeks, each tested in a sandbox.
Discovery found 14 handoff points where data was duplicated, dropped or re-entered. The build then followed the same order as this guide: a clean data model, Flow routing by geography, property type and agent capacity, a listing feed with health checks that alert admins when it fails, stage-gated transactions with a timestamped audit trail, and role-based dashboards and training. According to the published case study:
- Lead response time went from 4–6 hours to under 15 minutes.
- Per-agent admin fell by about four hours a week.
- Lead-to-appointment conversion rose 35% within 90 days of go-live.
- New-agent onboarding dropped from 14 days to 3.
- Compliance audit preparation fell from two days to under two hours.
These are one brokerage's results against its own starting point. Yours depend on where your gaps are, which is why the audit above starts with a baseline.
Should You Optimize, Rebuild or Replace Your Propertybase Org?
Optimize in most cases. An org that agents work around has usually drifted: the brokerage changed and the configuration didn't. Correcting data, routing and automation in place is faster and cheaper than starting again. A rebuild is justified only when the data model itself is wrong, and replacing a single feature can be enough when one workflow has outgrown the package.
Optimize when the problems are duplicates, stale picklists, routing rules from an old office structure, legacy Process Builder, reports nobody trusts or low adoption. Each is fixable in the org you already have, in sandbox-tested steps.
Rebuild or replace when deals are modelled outside Offers and Closings, custom objects duplicate the package, or a core workflow the package doesn't cover drives your revenue. Change the part that doesn't fit, not necessarily the whole system.
For one UAE brokerage, the right answer was narrow: Twopir Consulting replaced Propertybase's listing publishing with a direct Salesforce integration to Zoopla and Rightmove, with Publish, Check Status and Unpublish actions on the record. One workflow changed; the Salesforce org stayed.
The Bottom Line
Getting the most from Propertybase and Salesforce is less about adding features and more about using the ones you already pay for, on data agents trust, with automation someone owns. Start with an honest audit, fix data and routing first, and test every change before agents see it.
- 1
Use the packaged objects and block duplicates at entry.
- 2
Route every lead automatically, and escalate the ones nobody contacts.
- 3
Rebuild Process Builder automation in Flow, with an owner for each flow.
- 4
Switch on field history and historical trending before you need them.
- 5
Test every Propertybase release in a sandbox, and measure real usage.
Find What Your Propertybase Org Is Leaving Unused
On a 30-minute discovery call, a Twopir Salesforce architect will walk through your Propertybase org with you, show where data, routing or automation is holding agents back, and tell you which fix will pay back first.
Schedule a Discovery CallFrequently Asked Questions
Keep one clean record per person and property, capture every lead source into Front Desk and route it with Lead Router, match listings from the inquiry, automate follow-up with Action Plans and Flow, run deals through Offers and Closings, report from role-based dashboards, and test every change in a sandbox.
Yes. Propertybase is a real estate CRM that runs natively inside Salesforce, adding records such as inquiries, listings, offers and closings. Lone Wolf Technologies acquired Propertybase in 2021 and also sells Front Office, formerly Propertybase GO, as a separate product.
Some of Propertybase's older help instructions, such as starting drip campaigns automatically, use Process Builder. Salesforce ended support for Process Builder and Workflow Rules on December 31, 2025. Existing processes still run but get no fixes, so rebuild them as record-triggered flows.
Lone Wolf says Propertybase is updated every three to six weeks through AgentExchange releases. Install each update in a sandbox first and run a short test script covering routing, matching, offers and closings before it reaches agents.
Only for what you track. Salesforce field history tracking records who changed a tracked field and when, starting from the day you switch it on, and keeps it for up to 18 months unless you add Field Audit Trail. Setup Audit Trail separately records configuration changes for 180 days.
Look for workarounds: leads forwarded by email, listings searched in another window, follow-up reminders on phones, deal status in email threads, and spreadsheets kept beside the CRM. Each one points to a Propertybase or Salesforce feature that is either switched off or not trusted.
Usually fix it. Duplicates, outdated routing, legacy automation and untrusted reports can all be corrected in place. Rebuild only when deals are modelled outside Offers and Closings or custom objects duplicate the package, and consider replacing a single workflow before replacing the whole system.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Propertybase implementations, optimization and integrations for real estate brokerages.