Advanced Salesforce Workflows for Propertybase: From Lead to Close
Propertybase already gives a brokerage the records for every step of a deal: contacts, inquiries, showings, offers and closings. This guide shows how to connect them with Salesforce Flow, stage by stage, so leads reach an agent fast, showings get confirmed, offers clear compliance and closings run to a checklist.
Key Takeaways
- Propertybase models the deal as a chain of records: Contact, Inquiry, Linked Listing, Showing, Offer and Closing. Good lead-to-close automation follows that chain instead of the generic Lead and Opportunity model.
- Use what the package already ships first: Front Desk lead capture, Lead Router, inquiry matching, Quicksend, drip campaigns, Action Plans and the Offer-to-Closing handover.
- Salesforce Flow fills the gaps between those records: SLA clocks on new leads, showing reminders, compliance gates before an offer moves on, e-signature triggers and date-driven closing checks.
- Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025. Any Propertybase automation still built in them, including drip campaign triggers, should be rebuilt in Flow.
- Build every flow with entry conditions, fault paths and a set run order, test it in a sandbox, and retest after each Propertybase package upgrade.
Propertybase workflows decide how fast a new inquiry reaches an agent, whether a showing gets confirmed, and how cleanly an accepted offer turns into a closed deal. Propertybase is a real estate CRM built on Salesforce, so every brokerage on it can automate the whole journey from first contact to commission with Salesforce Flow, without another subscription.
This guide is for operations leaders, Salesforce admins and broker-owners at growing and mid-market companies in real estate. It walks through the deal one stage at a time: what Propertybase already does at each stage, what a flow should add, and the design mistakes that make automation fragile. Every product detail links to the vendor's own documentation.
What Is a Lead-to-Close Workflow in Propertybase?
It is the set of automations that moves one buyer or seller from a new contact to a recorded closing. In Propertybase that means capturing the contact and inquiry, routing it to an agent, matching listings, booking and following up showings, managing offers and running the closing. Each stage has its own record, and Flow connects them.
| Stage | Propertybase record | What Propertybase ships | What a flow adds |
|---|---|---|---|
| 1. Capture | Contact and Inquiry | Front Desk webforms and the WebToProspect API | Field clean-up, source tagging, priority flags |
| 2. Route | Contact (Routing Source) | Lead Router: teams, Click to Claim, Auto-Assign, Round Robin | An SLA clock that escalates uncontacted leads |
| 3. Qualify and nurture | Inquiry, Linked Listing | Matching, Quicksend, drip campaigns | Stage gates, guided qualification, drip triggers rebuilt in Flow |
| 4. Show | Showing (activity) | Showings on the calendar, client rating and feedback | Reminders, confirmation and feedback follow-up |
| 5. Negotiate | Offer | Offer path, counter-offers, addenda | Compliance gates and e-signature triggers |
| 6. Close | Closing | Closing from offer data, checklist, commission overview | Action Plan start, date-driven checks, alerts |
| 7. After close | Contact, Closing | Reports and dashboards | Commission roll-ups, review requests, re-engagement |
How Does the Propertybase Record Chain Work From Lead to Close?
Propertybase tracks a deal as linked records, not as one opportunity that changes stage. A Contact holds the person, an Inquiry holds what they want, Linked Listings and Showings hold the properties they consider, an Offer holds the negotiation, and a Closing holds the transaction. Automation works best when each flow belongs to one of those records.
Propertybase's own Getting Started series walks through this chain "from lead to close". The details that matter for automation are:
- Contacts are Individual or Company records with a Contact path that shows the person's current status. A contact can be a lead, a customer or a partner.
- Inquiries (the
pba__Request__cobject) capture what a buyer wants, such as property type, bedrooms and budget, and custom fields can add criteria. - Matching works in both directions: from an inquiry to available listings, and from a listing to the inquiries that match it.
- Linked Listings connect a contact to a listing and hold the contact's status and feedback on that property.
- Showings are activity records with start and end times, a 1–5 client rating and client feedback. One listing can have many showings.
- Offers tie a listing to buyer and seller records, with counter-offers, addenda and an Offer path, and an action that creates a Closing.
- Closings are created from the offer, copying its data, and hold status, target and actual closing dates, a commission overview and a closing checklist.
For the wider object model and how it sits inside Salesforce, see our guide to Propertybase Salesforce CRM architecture.
How Should Propertybase Capture and Route New Leads?
Let Front Desk capture the lead and Lead Router assign it, then add a flow that watches the clock. Propertybase already turns website, email and portal leads into contacts and inquiries, and already routes them to teams and agents. What it doesn't do by default is escalate a lead that nobody has contacted within your service-level time.
What Propertybase already does
Front Desk captures leads through Propertybase webforms, the WebToProspect REST API, or JSON and XML email formats. Lead Router then works in two steps. A process sets the contact's Routing Source, which assigns the lead to a Team. The team's Distributor then picks the agent: Click to Claim (everyone is emailed and the first to claim wins), Auto-Assign (one named user) or Round Robin (agents take turns). Agents can opt out while they are away, and admins can disable users.
Two Lead Router behaviours shape everything you build on top of it:
- Returning leads skip routing. If an existing contact or inquiry comes back, Propertybase gives it to the previous owner and emails them. Propertybase says this is not configurable, so your SLA logic must cover owners who have since left or gone quiet.
- Agent text alerts are regional. Routing notifications go by Chatter and by text message, but text alerts work only in North America (+1) and Australia, and agents must opt in. Elsewhere, plan on mobile Chatter or Salesforce notifications.
What a flow adds: the SLA clock
Put a record-triggered flow on the contact or inquiry, with a scheduled path that runs a set time after assignment. If the lead still has no logged contact, the path can reassign it, alert the team lead with a custom notification on desktop and mobile, or both. Keep the routing rules themselves simple. Geography, property type and price band cover most brokerages, and every extra rule is one more thing to test and explain to agents.
Before you add routing logic in Flow, decide which tool owns assignment. Lead Router, Salesforce assignment rules and a custom flow should never all assign the same record. If you outgrow Lead Router, Salesforce's Omni-Channel Flow can route custom objects by agent capacity and skills. Our post on Salesforce features Propertybase brokerages underuse covers that option in detail.
What this looks like in practice: for a multi-office residential brokerage with more than 120 agents, Twopir Consulting built three-tier Flow routing by geography, property type and agent capacity, with escalation for high-intent leads. The published case study reports that lead response went from 4–6 hours to under 15 minutes.
How Do You Automate Qualification and Nurture in Propertybase?
Make each stage ask for the data the next stage needs, and let matching and drip campaigns do the follow-up. A buyer who reaches a showing without a budget or a financing status creates work later. Gate the move to the next stage on the fields that matter, guide agents through the qualifying call, and keep long-term prospects warm automatically.
Gate stages on the fields that matter
Salesforce Path shows key fields and "guidance for success" at each step, and it works on custom objects, so you can add it to inquiries as well as the contact path. Pair it with a validation rule that stops an inquiry moving to an active status until budget, preferred area and financing status are filled in. Validation rules apply to every save, including integrations and records saved through the API. So check that your webforms and portal feeds can still create new inquiries at the first status.
Guide the qualifying call
A screen flow walks an agent through the call one screen at a time and writes the answers to the right records: search criteria on the inquiry, consent and preferences on the contact, and a follow-up task. Agents get a short script instead of a long page layout, and every inquiry is qualified the same way.
Let matching and drip do the follow-up
Propertybase's matching screen lets an agent email selected listings, create linked listings or start an Action Plan in a few clicks. For one-to-one email, Quicksend sends templates with inline listings to up to 20 recipients. For longer cycles, drip campaigns send a scheduled series of emails to a contact, and setup includes an "Automated Email Opt Out" field for contacts who don't want them.
For more nurture ideas, see our guide to lead nurturing with Propertybase and Salesforce.
How Do You Automate Showing Reminders and Feedback?
Time the reminders from the showing's start time, and send no more than two. A scheduled path can send one reminder the day before and one on the morning of the showing. If the showing moves, Salesforce reschedules the path automatically. After the showing, a follow-up task makes sure the client's rating and feedback get recorded.
Showings in Propertybase are activities with a start and end time, a location, an assigned agent, and fields for client rating and feedback. That gives a flow everything it needs:
Choosing the channel. The Send Email action in Flow needs domain-level and user-level email verification before it will send, and allows up to 150 recipients per action. For text messages to clients, Salesforce's Send Conversation Messages action works only on enhanced messaging channels such as enhanced SMS and WhatsApp. It reaches only people who have a messaging user record and who have given consent. Confirm the licences with your Salesforce account team before you design around SMS. If clients book their own viewings, Salesforce Scheduler handles self-service appointments in Enterprise and Unlimited Editions.
How Do You Build Compliance Gates Into Propertybase Workflows?
Block the step, not the person. Where your market or your brokerage requires identity documents or proof of funds before an offer moves forward, stop the status change until the documents are verified. Give managers a controlled override so a genuine exception doesn't stall the deal, and record who used it.
A compliance gate has three parts:
Collect
A screen flow on the offer asks for the required documents and creates a verification task for the compliance owner when they are uploaded.
Block
A validation rule, or a flow's Custom Error element, stops the offer moving to its next status while a "documents verified" field is unchecked.
Override
A custom permission lets named managers bypass the rule. A flow logs who overrode the gate and when, so an audit can see every exception.
If exceptions need sign-off rather than a single manager's judgement, Flow Approval Processes add stages, steps and decisions in Flow Builder. A record-triggered approval starts after the record is saved. Keep the rule's conditions narrow: a gate that fires on the wrong status blocks legitimate deals, and agents learn to work around it.
How Do You Automate the Path From Accepted Offer to Closing?
Use Propertybase's own handover from offer to closing, then let the closing record drive the checklist. When an offer is accepted, create the Closing from it so the data carries over. Then start an Action Plan of dated tasks, send documents for signature when the status changes, and run scheduled checks timed from the target closing date.
Hand over from offer to closing
Propertybase creates a Closing from an existing offer and copies the relevant data. Keep that handover and automate what happens around it. When the closing is created, a flow can start a closing Action Plan, Propertybase's template of tasks with day offsets, dependencies and assignees. Default templates cover new closings, buyers, sellers and listings.
Send for signature automatically
There are two common routes. Lone Wolf states that Authentisign is built into Propertybase, so offers can be sent, signed and tracked inside the CRM. Brokerages that use DocuSign can add the Send with Docusign flow action, which requires Docusign Apps Launcher 6.1 or later. It sends an envelope template from a record-triggered flow when your conditions are met, for example when an offer reaches the status where a contract goes out.
DocuSign's document writeback saves the signed documents and the certificate of completion back to the Salesforce record, and can update a status when signing completes. Two caveats from DocuSign's documentation:
- Data writeback supports only text and picklist fields.
- Writeback fails for users who have MFA for API logins turned on.
If your org still runs the legacy DocuSign eSignature for Salesforce app, DocuSign set October 16, 2026 as its last day of use. Move to the current app before you build any flows on it. Our DocuSign workflow automation services cover this migration.
Watch the dates
Scheduled paths timed from the closing's target date catch problems while there is still time to fix them. For example: check that the checklist is complete a week out, alert the agent and transaction coordinator three days out, and flag closings that pass their target date without an actual closing date. Because the paths reschedule themselves, a moved closing date needs no manual rework.
What Should Happen Automatically After a Deal Closes?
Settle the numbers, thank the client and schedule the next conversation. When a closing is marked complete, a flow can calculate commission and fee fields, update the contact's status, create a review or referral request, and enrol the contact in a long-term nurture. That way the end of one deal starts the next one.
- Commission and production. Propertybase says you can add custom fields to closings to calculate commissions and desk fee deductions, and that closings support forecasting team production. Calculate in a before-save flow, so the fields are right when the record is saved.
- Client status. Move the contact to its customer status on the Contact path, so marketing lists and reports pick them up.
- Review and referral. A scheduled path a few days after closing creates the agent's thank-you and review-request task, or sends a template email.
- Long-term nurture. Propertybase drip campaigns can start from a date field on the contact. An anniversary-of-purchase date is a natural trigger for an annual market update.
- Reporting. Each Propertybase dashboard component maps to one report. Build the stage metrics in the next section as reports first, then add them to a dashboard. Our guide to Propertybase reports in Salesforce has examples.
How Do You Build Propertybase Workflows That Don't Break?
Give each object one clear entry point, make every flow fire only when it should, and plan for failure. Most fragile Propertybase automation comes from a few habits: flows that re-run on every edit, several automations on one object with no set order, no error handling, and changes made straight in production.
Two more details are easy to miss. Scheduled paths run as the user who changed the record, so set a Default Workflow User in Process Automation Settings. And document every flow with a description that says what it does, which record it watches and who owns it.
Which Metrics Show Whether Your Lead-to-Close Automation Works?
Measure one number per stage, before and after each change. Automation that doesn't move a stage metric is just more to maintain. Capture a baseline from your own reports before you build, and compare like-for-like periods afterwards. Benchmarks from other brokerages tell you little about yours.
| Stage | Metric | Where the data comes from |
|---|---|---|
| Route | Time from inquiry created to first logged contact | Inquiry created date and the first activity |
| Route | Share of leads escalated by the SLA clock | A field set by the scheduled path |
| Qualify | Inquiries with complete search criteria | Inquiry fields required by your stage gate |
| Show | Showings held vs booked; feedback logged | Showing status, client rating and feedback |
| Negotiate | Offers blocked by the compliance gate; overrides used | The override log |
| Close | Days from accepted offer to actual closing | Offer status date and the closing's actual closing date |
| After close | Repeat and referral business from past clients | Contact source and history |
Where Should a Brokerage Start?
Automate your most painful bottleneck end to end, prove it with one metric, then move to the next. For most brokerages that is speed to lead, because it decides how many inquiries ever reach a showing. Before you build anything, audit what already runs, because a new flow layered on unknown automation is where most trouble starts.
Our Propertybase automation services cover each of these steps. For custom objects, pages and components beyond Flow, see Propertybase customization.
The Bottom Line
Propertybase already holds every step of a deal in its own record, from the first contact to the closing. Advanced workflows don't replace that model. They connect it, so no stage waits on someone remembering to act. Start with the package's own tools, add Flow where the gaps are, and build each automation so it fires once, fails loudly and survives the next upgrade.
- 1
Automate along Propertybase's own chain (Contact, Inquiry, Showing, Offer, Closing), not a generic lead and opportunity model.
- 2
Keep Lead Router for assignment and add a scheduled-path SLA clock for escalation.
- 3
Gate stages on the data the next stage needs, and give managers a logged override.
- 4
Time showing reminders and closing checks from the record's own dates, so they reschedule themselves.
- 5
Rebuild Process Builder automation in Flow, and check that your DocuSign app is current.
Map Your Lead-to-Close Workflow With an Architect
On a 30-minute discovery call, a Twopir Salesforce architect will walk through how a lead becomes a closing in your Propertybase org, show you where deals stall, and tell you which workflow to automate first.
Schedule a Discovery CallFrequently Asked Questions
It is the chain of automations that moves a buyer or seller from a new contact to a recorded closing. In Propertybase each stage has its own record: Contact, Inquiry, Linked Listing, Showing, Offer and Closing. Salesforce Flow connects them with routing, reminders, compliance gates, e-signature and closing checks.
Yes. Lead Router assigns new contacts and inquiries to a team through a Routing Source, and the team's distributor picks the agent by Click to Claim, Auto-Assign or Round Robin. Returning leads go back to their previous owner. Add a Salesforce Flow scheduled path to escalate leads nobody contacts in time.
Use a record-triggered flow on the showing with scheduled paths timed from its start time, for example 24 hours before and on the morning of the showing. If the showing is moved, Salesforce reschedules the paths automatically. A path after the end time can create a task to record the client's feedback.
Yes. Lone Wolf states that Authentisign is built into Propertybase. Brokerages using DocuSign can add the Send with Docusign flow action, which sends an envelope when a record meets your conditions, and document writeback saves the signed files to the record. The legacy DocuSign app's last day of use was October 16, 2026.
They still run, but Salesforce ended support for Process Builder and Workflow Rules on December 31, 2025, so they get no support or bug fixes. Propertybase's own drip campaign automation instructions use Process Builder. Rebuild those triggers as record-triggered flows, using Salesforce's Migrate to Flow tool as a starting point.
Start with Flow. Salesforce Architects recommend Flow for light automation, Flow with invocable Apex for medium complexity, and Apex triggers for heavy, high-volume objects. Whichever you choose, use one entry point per object and don't mix Flow and Apex triggers as entry points on the same object.
Add a validation rule, or a flow's Custom Error element, that blocks the offer's next status until a documents-verified field is checked. Collect the documents with a screen flow, give named managers a custom-permission override for genuine exceptions, and log every override so audits can review them.
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.