7 Salesforce Features You Didn't Know Propertybase Could Use
Propertybase runs inside Salesforce, so every brokerage on it already owns a full automation, integration and interface platform. Here are seven native Salesforce features that close the gaps Propertybase leaves open, what each one does in a real estate org, and the mistakes to avoid when you switch them on.
Key Takeaways
- Propertybase Salesforce Edition is a real estate application that runs inside Salesforce, so the whole Salesforce platform is available to the brokerage, not only the screens Propertybase ships.
- Seven native features close the most common gaps: before-save flows, scheduled paths, Omni-Channel Flow routing, sObject Collections and Bulk API 2.0 upserts, Platform Events and Change Data Capture, duplicate and matching rules, and Dynamic Forms with Lightning Web Components.
- Use them to extend Propertybase, not to rebuild what it already does well, such as lead capture, inquiry-to-listing matching and portal syndication.
- The biggest wins usually come from speed-to-lead (routing plus an SLA clock) and from clean, idempotent MLS and portal data loads.
- Build and test every change in a sandbox first, and retest after each Propertybase package upgrade.
Most brokerages buy Propertybase for its real estate objects: listings, inquiries, offers and closings. Far fewer use the Propertybase Salesforce features they already pay for underneath it. Because Propertybase Salesforce Edition is built on Salesforce, every org also contains Salesforce Flow, the Salesforce APIs, an event bus, duplicate management and the Lightning page builder. Those tools solve problems that brokerages often try to fix with extra apps, spreadsheets or manual coordinators.
This guide is written for operations leaders, Salesforce admins and broker-owners at growing and mid-market companies in real estate who run Propertybase and want more from it. It names the seven Salesforce features worth knowing, explains what each one does in a Propertybase org, and lists the mistakes we see when they are switched on without a plan.
Which Salesforce Features Can a Propertybase Org Use?
Any Salesforce platform feature your edition and licences include. Propertybase adds real estate objects and tools to a Salesforce org; it does not replace the platform. The seven features below matter most for brokerages because they fix slow lead response, stale listing data, duplicate contacts and cluttered agent screens without another subscription.
| # | Salesforce feature | Brokerage problem it solves | Usually built by |
|---|---|---|---|
| 1 | Before-save record-triggered flows | Messy inquiry and contact data at the moment it is created | Admin |
| 2 | Scheduled paths in Flow | Leads that nobody follows up, missed listing and closing dates | Admin |
| 3 | Omni-Channel Flow routing | Inquiries assigned to agents who are busy, away or the wrong fit | Admin + architect |
| 4 | sObject Collections upsert and Bulk API 2.0 | MLS and portal feeds that create duplicates or fail halfway | Developer |
| 5 | Platform Events and Change Data Capture | Websites, chat tools and back-office systems that lag behind the CRM | Developer |
| 6 | Duplicate and matching rules | The same buyer entered three times by three portals | Admin |
| 7 | Dynamic Forms, Dynamic Actions and Lightning Web Components | Record pages built for nobody in particular | Admin + developer |
What Propertybase Already Does, So You Don't Rebuild It
Propertybase already covers lead capture, inquiry-to-listing matching, portal syndication and the offer-to-closing record trail. Start every Salesforce extension from that baseline. Rebuilding a feature the package already ships creates two versions of the truth, and the package version is the one that keeps getting updated.
Some context first. Lone Wolf Technologies acquired Propertybase in August 2021. Today Lone Wolf offers two products: Propertybase, the CRM built on Salesforce, and Front Office, the web presence product formerly called Propertybase GO. This article is about the Salesforce-based product, Propertybase Salesforce Edition.
Lead capture
Website forms, emails and portals flow in through Front Desk, using Propertybase webforms, the WebToProspect REST API or JSON and XML email formats.
Inquiry-to-listing matching
Search criteria on Inquiry records (the pba__Request__c object) match against listings, and custom fields can extend the matching.
Portal syndication
Listings publish to supported portals through Portal Mapping in the Control Center.
Offers and closings
The Offers object tracks offers, counter-offers and addenda, and creates a Closing from the offer data.
Lone Wolf also states that Propertybase includes lead routing, workflow automation built on Salesforce Flow and Agentforce AI for lead scoring. The features below are how a brokerage shapes that automation around its own territories, teams and systems.
The 7 Salesforce Features Propertybase Brokerages Underuse
Each feature below follows the same pattern: what it is, how a Propertybase org uses it, and the catch to plan for.
1. Before-save record-triggered flows
Data qualityBest for: cleaning and enriching inquiry, contact and listing fields the moment a record is saved.
A before-save record-triggered flow updates the triggering record before it is written to the database. Salesforce says it can update a record 10 times faster than a record-change process, because the record is not saved twice. In a Propertybase org, use it to standardise phone formats, fill a region or territory field from a postcode, copy a lead source into a reporting field, or set a priority flag from the budget on an inquiry.
The catch: before-save flows support only the Assignment, Decision, Get Records and Loop elements. They cannot send an email, create a task or publish an event. Those jobs belong in an after-save flow. Many automation problems we inherit come from one flow trying to do both.
2. Scheduled paths
Speed to leadBest for: SLA clocks, follow-up reminders and date-driven listing and closing alerts.
Scheduled paths let a record-triggered flow run part of its logic later, timed from the triggering event or from a date field on the record. That turns a routing rule into a service level. If an inquiry is still uncontacted 15 minutes after assignment, reassign it or alert the team lead. If a listing's expiry date is 30 days away, create a task for the listing agent. If a closing date is a week out, check that the compliance documents are in.
The catch: scheduled paths run in system context, and the running user is the person who changed the record. Set the Default Workflow User in Process Automation Settings before you build, so paths still run when that person's user is deactivated.
3. Omni-Channel Flow routing
RoutingBest for: sending each inquiry to an available agent with the right skills, such as language, area or property type.
Lead assignment rules work only for leads and cases, and they ignore whether the agent is free. Omni-Channel Flow routes leads and custom objects too, so it can route Propertybase inquiries directly. You define the routing logic in an Omni-Channel flow and call it as a subflow from a record-triggered flow. Agents set their presence, and work goes to people who have capacity.
The catch: Omni-Channel was designed for service teams, so plan presence statuses and capacity so they suit agents who spend the day out at showings. Salesforce retired Standard Omni-Channel with the Summer '26 release and upgraded orgs to Enhanced Omni-Channel, so design for Enhanced. Confirm which licences your users need with Salesforce before you commit to this design.
4. sObject Collections upsert and Bulk API 2.0
IntegrationBest for: MLS, portal and back-office feeds that must update existing records instead of creating duplicates.
An upsert creates a record if it is new and updates it if it already exists, matched on an external ID such as the MLS number. The REST API's sObject Collections upsert handles up to 200 records of one object per request. With allOrNone left at its default of false, one bad record does not roll back the other 199. For larger jobs, Salesforce recommends Bulk API 2.0 for any operation over 2,000 records, which processes them asynchronously.
The catch: an upsert is only as reliable as its external ID. Mark the field as unique and as an external ID, decide which system owns each field, and log the per-record errors the API returns. Silent partial failures are the most common reason a listing feed "mostly works".
5. Platform Events and Change Data Capture
Real-time syncBest for: telling websites, chat tools, transaction systems and data warehouses that something changed, as it happens.
Platform Events are messages your org defines, such as "inquiry assigned" or "offer accepted". Flows, Apex or external apps publish them, and flows, Apex triggers and external Pub/Sub API clients receive them in real time. Change Data Capture does the same for record changes automatically: it publishes an event when a record is created, updated, deleted or undeleted. Use it to keep an external website or reporting database current without nightly exports.
The catch: publish only the changes someone acts on. A price change or status change is worth an event; every edit to a description field usually is not. Both features are available in Enterprise, Performance, Unlimited and Developer editions.
6. Duplicate and matching rules
Data qualityBest for: buyers and sellers who arrive from several portals, open houses and referrals.
Salesforce duplicate management combines matching rules, which define what counts as a duplicate, with duplicate rules, which decide what happens: warn the user or block the save. You can add custom fields to matching rules, run different rules for different profiles, and run duplicate jobs to find and merge duplicates that already exist across the org.
The catch: integrations and webforms need a decision too. Blocking a duplicate created by a portal feed can drop the inquiry entirely. A common pattern is to allow the record, flag it, and let a flow or a person merge it, so no lead is lost.
7. Dynamic Forms, Dynamic Actions and Lightning Web Components
Agent experienceBest for: record pages that show each role what it needs, on desktop and on the phone.
Dynamic Forms break a page layout into fields and sections you place in the Lightning App Builder and show or hide based on record data, user details and device type. A listing page can show marketing fields to the marketing team, commission fields to finance and a short mobile view to agents, from one page. Dynamic Actions do the same for buttons. When a screen needs logic that configuration cannot provide, Lightning Web Components add custom interface pieces, such as a portal publishing panel or a match summary.
The catch: Dynamic Forms works only on objects that support it. Check each Propertybase object in the Lightning App Builder: if there is no Fields tab, the object is not supported. Also, the fields users see when they create or edit a record come from the page, not the layout, so test the edit experience as well as the view.
How the Seven Features Fit Together in One Org
Think of them as four layers around Propertybase: get clean data in, route it fast, tell other systems about it, and give agents a screen that fits. Each layer depends on the one before it. Routing on dirty data sends leads to the wrong agent, and events fired from duplicate records confuse every system downstream.
Feeds, Webforms and Clean-Up
Propertybase lead capture, plus upserts on an external ID (feature 4), before-save clean-up (feature 1) and duplicate rules (feature 6).
The Right Agent, Within Minutes
Omni-Channel Flow routing (feature 3) with a scheduled-path SLA clock and escalation (feature 2).
Websites, Chat and Back Office in Step
Platform Events and Change Data Capture (feature 5) notify subscribers, so nothing waits for a nightly export.
Role-Based Pages, Desktop and Mobile
Dynamic Forms, Dynamic Actions and Lightning Web Components (feature 7) on Propertybase's listing, inquiry and offer pages.
For a deeper look at the object model these layers sit on, see our guide to Propertybase Salesforce CRM architecture.
What Mistakes Should You Avoid When Extending Propertybase?
Most problems come from building against the package instead of around it, and from letting automation pile up with no owner. These are the five patterns we see most often when we audit Propertybase orgs.
What Does This Look Like in a Real Brokerage?
In our own projects, the same features show up again and again: Flow-based routing for speed to lead, Apex and APIs for listing feeds, and Lightning Web Components for agent actions. Three published Twopir case studies show the pattern.
- Routing and SLAs. For a multi-office residential brokerage with more than 120 agents, we built three-tier Flow routing by geography, property type and agent capacity, plus escalation of high-intent leads. The case study reports that lead response went from 4–6 hours to under 15 minutes. Read the Propertybase case study.
- Listing feeds. For a luxury brokerage in the UAE, we built an Apex REST endpoint that serves live listing data as XML to external property websites, replacing manual uploads. Read the XML feed case study.
- Agent actions. For a luxury brokerage in the UAE, we connected Salesforce directly to the Zoopla and Rightmove APIs, with a Lightning Web Component that gives agents Publish, Check Status and Unpublish actions on each listing. Read the portal publishing case study.
Results depend on each brokerage's data, team and process, so treat these as examples of the pattern, not as benchmarks.
Where Should a Brokerage Start?
Start with the data layer, then routing, then integrations, then screens. That order means each step builds on clean records, and the first visible win, faster lead response, arrives early. Each step should be measured before the next one starts.
Our Propertybase automation services cover steps 2 and 3, and our Propertybase API integration services cover step 4.
Is Your Propertybase Org Ready for Agentforce and Data 360?
Only if the seven features above are in place first. AI agents and unified data depend on clean records, clear routing and reliable events. An agent that drafts follow-ups or qualifies inquiries is only as good as the data and the automation it can call.
Salesforce's AI layer is Agentforce, and agents and add-ons are now listed on AgentExchange. Salesforce's data platform was renamed from Data Cloud to Data 360 on October 14, 2025. It connects data from other sources, such as a transaction or marketing system, to the CRM. Lone Wolf already markets Agentforce-based lead scoring for Propertybase. For brokerages that want to go further, our Propertybase AI and Agentforce services start with a readiness check of exactly these foundations.
The Bottom Line
Propertybase gives a brokerage the real estate objects and workflows. Salesforce gives it the platform to fit them to its own territories, teams and systems. The seven features in this guide are already in most Propertybase orgs, and they solve the problems brokerages most often pay extra to fix: slow lead response, duplicate contacts, unreliable feeds and screens nobody likes using.
- 1
Extend Propertybase; don't rebuild lead capture, matching or syndication that the package already ships.
- 2
Clean data at the door with before-save flows and duplicate and matching rules.
- 3
Pair routing with an SLA clock: Omni-Channel Flow or assignment rules, plus scheduled paths.
- 4
Make every feed an upsert on an external ID, and use events only for changes someone acts on.
- 5
Design record pages by role and device, and build in a sandbox before anything reaches production.
Get More From the Propertybase Org You Already Have
On a 30-minute discovery call, a Twopir Salesforce architect will review how leads, listings and feeds move through your Propertybase org, and tell you which of these seven features would make the biggest difference first.
Schedule a Discovery CallFrequently Asked Questions
Yes. Propertybase Salesforce Edition is a real estate CRM built on Salesforce and owned by Lone Wolf Technologies since August 2021. It adds real estate objects such as listings, inquiries, offers and closings to a Salesforce org, so the brokerage can also use Salesforce platform features like Flow, the APIs, duplicate management and Lightning pages.
Yes. Record-triggered flows run on Propertybase objects such as inquiries and listings, just as they do on standard objects. Use before-save flows for fast field updates and after-save flows for tasks, emails, routing and events, and check what the package already automates so two automations don't conflict.
Use a record-triggered flow on the inquiry to apply your routing rules, or call an Omni-Channel flow to route it to an available agent with the right skills, such as language or area. Add a scheduled path that reassigns or escalates the inquiry if nobody contacts the lead within your service-level time.
Upsert records on an external ID, such as the MLS number, so updates change existing records instead of creating duplicates. The REST API's sObject Collections upsert handles up to 200 records per request; Salesforce recommends Bulk API 2.0 for jobs over 2,000 records. Log the per-record errors the API returns.
They can, if they modify the package or depend on behaviour that changes. Build around the managed package rather than inside it, keep automation documented with a set run order, and retest flows, integrations and pages in a sandbox after every Propertybase upgrade before it reaches production.
Lone Wolf markets Agentforce AI for lead scoring and deal predictions as part of Propertybase. Because Propertybase runs on Salesforce, a brokerage can also build its own Agentforce agents, but they work best once data quality, routing and events are already in place.
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, automation and integrations for real estate brokerages in the US, UK, UAE, Australia and Canada.