Leads forwarded, never imported
Front Desk processes leads the portal sends straight to your Front Desk address. Leads forwarded from an agent's mailbox, or copied in CC or BCC, are not imported, and they wait in an inbox instead.
Portal lead capture in Propertybase Salesforce Edition is the route an inquiry takes from a property portal, your website or another digital source to a complete Contact and Inquiry record: source identified, fields mapped, linked to the listing it asked about, checked for duplicates and handed to the right agent. Twopir Consulting designs that intake layer and keeps it reliable after go-live. Every route classified as native, supported, middleware or custom before anything is built.
Trusted by 500+ organizations, including brokerages, agencies and property businesses that run their listings, inquiries and deals in Salesforce with Twopir Consulting.












What We Connect
Most lost portal leads are not lost on the portal. They are lost in the few steps between the portal's email and a usable record in Propertybase, and nobody notices because nothing errors loudly. These are the six places we find them.
Front Desk processes leads the portal sends straight to your Front Desk address. Leads forwarded from an agent's mailbox, or copied in CC or BCC, are not imported, and they wait in an inbox instead.
Front Desk relies on a parser per source. A portal without one, or a portal that changes its email layout, produces import errors instead of contacts until the source is set up with Propertybase Support.
Budget, property type, language and the listing reference arrive in a description field, or not at all, so matching, routing and reports have nothing structured to work with.
The buyer asked about one listing, but the Inquiry is not linked to it. The agent calls without context, and the listing owner never learns the property drew interest.
A well-meant duplicate rule set to Block on create stops Front Desk and API leads from being saved at all. Set loosely, the same buyer appears three times with three agents.
Error alerts go to a former employee, source values are inconsistent, and there is no report of volume by portal, so a silent source shows up weeks later as a weak month.
Propertybase portal lead capture is the inbound half of a portal integration: the set of routes that turn an inquiry from a real estate portal, a website form or another digital source into a Contact and an Inquiry in Propertybase Salesforce Edition, with the source, the requirement and the listing of interest recorded on it. The outbound half, publishing your listings to portals, is called Portal Syndication in Propertybase and is a separate mechanism.
Propertybase documents the inbound routes. Front Desk receives portal emails at a unique address, parses them and creates a Contact, or adds a new Inquiry when the Contact already exists. Propertybase Webforms, the WebToProspect REST API and JSON-to-Email or XML-to-Email webforms bring in website inquiries. Lone Wolf Technologies, which acquired Propertybase in 2021, owns the package and these services; Salesforce provides the platform underneath, including duplicate rules, Flow, reports and the APIs; and Twopir Consulting designs, configures, tests and monitors the intake for your sources. The vendor's own documentation is in the Propertybase Salesforce help centre.
Everything on this page applies to Propertybase Salesforce Edition. Propertybase GO is a separate product with its own help centre and its own lead distribution, and the Flow, Apex and Salesforce API work described here does not apply to it. We help growing and mid-market companies solve complex CRM, integration, and business system challenges, and the same intake design serves larger enterprise brokerages with many offices and sources. For the full Propertybase practice, start at our Propertybase services page.
A portal lead passes six stages before an agent can act on it. Each one is held by a specific Propertybase or Salesforce mechanism, and each one is where we configure and test.
Every portal, form and campaign gets a name before it sends a single lead, so the record says where the buyer came from.
The portal emails your Front Desk address directly, and Front Desk separates the lead's data from the message.
Name, contact details, budget, property type, language and listing reference land in fields that can be searched.
A returning buyer gets a new Inquiry on the existing Contact, and possible duplicates are flagged rather than refused.
The Inquiry is tied to the listing the buyer asked about, so the agent and the listing owner both see the interest.
The new Contact or Inquiry sets a routing source, a team or rotation picks the agent, and the first task is created.
What happens after the hand-off, including qualification, routing rules, rotation and nurture, is lead management rather than lead capture. We build the follow-up automation itself on our Propertybase automation page.
Five kinds of route can bring a lead into Propertybase. The middle column is what Propertybase documents; the right-hand column is our design recommendation, confirmed against your org, portals and licences during discovery.
| Route | What Propertybase documents | When we use it |
|---|---|---|
| Native functionality | Front Desk email parsing into Contacts and Inquiries, with ready-made parsers for some portals; Propertybase Webforms (Lightning only, no change to incoming data). Portal Syndication publishes listings outbound, including to Idealista and Rightmove Overseas; that is listing publishing, not lead import. | First choice. Any source that can email Front Desk directly and has a working parser, and simple website forms. |
| Supported integrations | The WebToProspect REST API (needs a public API site and web development), JSON-to-Email and XML-to-Email webforms with tags such as InquirySource, ListingId, Language and UTM values, and the documented Facebook, Zillow & Trulia and Realtor.com lead capture. A source without a parser goes to Propertybase Support as a "New Portal Lead Source" request; Support analyses the portal's emails and gives a timeframe. | Website and campaign leads that need clean field mapping, and any portal whose parser has to be requested. We prepare the request and test the mapping before it goes live. |
| Middleware or aggregators | Aggregators are documented for outbound listings only: a generic Propertybase XML feed that a service such as XML2U converts for other portals (1001portales is listed as no longer supported). No aggregator is documented for inbound lead capture. | Outbound reach to portals with no native feed. For inbound, an integration platform that receives a portal's lead and posts it to WebToProspect is a design option we assess, not a documented Propertybase route. |
| Third-party apps | Propertybase is a managed package in a Salesforce org, so Salesforce AppExchange apps install alongside it. No specific app is documented by Propertybase for portal lead intake. | Only for a gap the routes above leave, such as enrichment or text-message alerts outside the regions Lead Routing covers, chosen per requirement after the native routes are mapped. |
| Custom API development | Propertybase objects are Salesforce objects, reachable through the Salesforce APIs; WebToProspect is Propertybase's own inbound API. Inquiry is the Request object (pba__Request__c) at API level. | Last resort, for a portal that offers an API or webhook but cannot email Front Desk and has no parser: Apex or an integration service writes the Contact and Inquiry, with logging and retries. |
General API and system integration work, such as MLS, e-signature and accounting, is covered on Propertybase API integrations and Propertybase integration. This page covers only how leads get in.
Publishing listings to a portal and importing that portal's leads are separate capabilities, and a portal can have one without the other. Propertybase says its list of ready-made lead parsers is not complete, so anything not documented here is verified per portal during discovery, never assumed.
| Portal | Listings out | Leads in | Our route |
|---|---|---|---|
| Idealista | Native. A supported Portal Syndication portal. | Not on the documented Front Desk parser list. | Lead emails sent directly to Front Desk, plus a "New Portal Lead Source" request to Propertybase Support; verified during discovery. |
| Rightmove Overseas | Native. A supported Portal Syndication portal. | Rightmove is on the parser list; the Overseas lead email is verified during discovery. | Native syndication; test the existing Rightmove parser against Overseas leads, and request a source if it does not match. |
| Rightmove, Zoopla | Native, including Zoopla Overseas. | Documented parsers (UK). | Native both ways: direct sending, field mapping checks and alert owners. |
| Fotocasa, Kyero, Habitaclia, pisos.com | No Propertybase documentation found. | No Propertybase documentation found. | Verified per portal during discovery: Front Desk plus a source request where the portal emails leads; the generic XML feed through an aggregator for listings; a custom build only where neither works. |
| Other documented lead sources | Zillow, LonRes, On the Market, Boomin and Realogy (Sotheby's) are also on the syndication list. | Parsers listed for portals in Australia, China, Dubai, Germany, Italy, the UK and the USA, such as Propertyfinder, Dubizzle, Immobiliare.it, Immoscout24 and Zillow. | Native intake, tested source by source before go-live. |
We do not claim a native connector for any portal Propertybase does not document, and we do not price one into a plan until the route has been tested. A portal's status can change, so the route is confirmed again at the start of every engagement.
Propertybase supplies the capture mechanisms. These are the decisions we make around them, built in a sandbox and tested with real sample leads from each source before they reach production.
A controlled list of sources, so every Contact and Inquiry carries the portal, form or campaign that produced it in one consistent value.
A mapping sheet per source, from the portal's email or the form's tags to Contact and Inquiry fields, agreed before Support configures it.
The listing the buyer asked about is carried in and linked, so the Inquiry, the agent and the listing owner share the same context.
One Contact per person, without refusing leads: Front Desk's own existing-contact check, backed by Salesforce matching and duplicate rules.
Quality enforced after the record exists, not at the door: an intake that rejects an imperfect lead loses the lead, not the error.
Capture ends when routing can start: the lead arrives with the values Lead Routing or Sales Rotation needs to pick the right agent.
Integration reliability is mostly about knowing quickly. These are the failures portal intake actually has, how each one shows itself, and the control we put in place so it is caught in hours rather than at month end.
| Failure | How it shows | Our control |
|---|---|---|
| Parse error | Front Desk sends its mandatory Error Alert; no Contact is created. | Error Alerts to a shared, owned inbox with a same-day check, and a source request when a layout changes. |
| Lead never reaches Front Desk | Nothing at all: forwarded or copied emails are not processed. | Every portal set to send directly; Forward Alert for sources that allow only one address. |
| Lead blocked on save | A duplicate or validation rule rejects the automated insert. | Duplicate rule on Allow, validation exempting intake, and a regression test after every rule change. |
| Fields lost in mapping | Records arrive with empty budget, type or listing fields. | A field-completeness report by source and test payloads with the exact, case-sensitive tags. |
| A source goes silent | Volume from one portal drops to zero without any error. | A daily count of new Inquiries by source on a dashboard, reviewed by a named owner. |
Our published portal work is on the publishing side, for brokerages in the UAE: the same portals, APIs and listing identifiers an intake design depends on. Each figure is scoped to the engagement that produced it.
Twopir Consulting transformed our real estate operations by unifying AML/KYC, inquiries, contracts, and commission tracking into a single Salesforce–Propertybase platform. Their API-driven approach automated workflows, reduced errors, and enabled real-time data synchronization. With improved visibility, collaboration, and compliance, we now operate faster, smarter, and with greater confidence.
Listing publishing moved from Propertybase into Salesforce, with Apex and a Lightning Web Component connected directly to the Zoopla and Rightmove APIs.
We have also built a single Apex REST endpoint that serves XML listing feeds to every external platform for Sotheby's International Realty (UAE): read the listing feed case study. No published case study of ours covers inbound portal lead capture on its own, and we do not present these as one.
Portal lead capture fails at the joins between the portal, Propertybase and Salesforce. We design those joins as one system and leave you able to see when one of them stops working.
Source, parsing, mapping, duplicates, the listing link and the hand-off are designed together, because a fix at one step usually moves the failure to the next.
Native, supported, middleware, third-party or custom, per source, from the vendor's documentation and a test. If a portal has no documented connector, you hear that before you plan around one.
Front Desk, webforms, duplicate rules and Flow first, so your admin can maintain the intake. Apex or an API build only where a source leaves no documented route.
Direct Zoopla and Rightmove API integration for one UAE brokerage, and listing feeds for Sotheby's International Realty (UAE). We know how portal identifiers and payloads behave in practice.
Alert owners, source dashboards and a runbook per source. If you would rather we watch it, Propertybase support and managed services covers feed monitoring after go-live.
Not through a documented ready-made parser. Idealista is a supported portal for Propertybase Portal Syndication, which publishes your listings to it, but it is not on Propertybase's documented list of portals that Front Desk already parses for inbound leads. The documented route is to have Idealista send lead emails directly to your Front Desk address and to request a New Portal Lead Source from Propertybase Support, who analyse the portal's emails and give a timeframe. We verify the route for your account during discovery.
Propertybase lists existing parsers for portals in Australia, China, Dubai, Germany, Italy, the UK and the USA, including Realestate.com.au, Domain.com.au, Juwai.com, Dubizzle, Propertyfinder, Immonet, Immoscout24, Immowelt, Immobiliare.it, Rightmove, Zoopla, Zillow, Trulia, Realtor.com and Homes.com. Propertybase says the list is not comprehensive, and no Spanish portal is on it, so any other source is checked and, where needed, requested from Propertybase Support.
We found no Propertybase documentation for these portals, either for publishing listings or for importing leads, so we do not claim a native connector. Each one is verified per portal during discovery: if the portal can email leads, Front Desk plus a New Portal Lead Source request is the first route; listings can reach portals without a native feed through Propertybase's generic XML feed and an aggregator; and a custom integration through the WebToProspect API or the Salesforce APIs is scoped only where neither works.
Two mechanisms work together. Front Desk adds a new Inquiry to an existing Contact instead of creating a second one, and a Salesforce Contact matching rule on the Standard Contact Duplicate Rule flags possible duplicates for agents. Propertybase warns that the duplicate rule must be set to Allow on create, because a rule that blocks duplicates also blocks leads arriving through Front Desk and the API. Duplicates are then reviewed and merged rather than refused at the door.
Yes, when the listing reference arrives with the lead. JSON-to-Email webforms carry a ListingId tag, and the Sales Rotation package can match a portal listing ID to a Listing and create a Linked Listing. It only works if the identifier the portal sends matches a listing ID held in Propertybase, which is why we keep listing IDs consistent between your portal feeds and your intake.
Front Desk sends an Error Alert for every lead it cannot process; that alert is mandatory. We route it to a shared inbox with a named owner, use Success Alerts while testing a new source, and add a dashboard of new inquiries by source so a portal that stops sending without any error is noticed within a day rather than at month end.
No. Everything on this page applies to Propertybase Salesforce Edition, the managed package that installs in a Salesforce org, where Front Desk, the WebToProspect API, Salesforce duplicate rules, Flow and reports are available. Propertybase GO is a separate CRM and website product with its own help centre and its own lead distribution settings.
A first conversation covers the portals and forms you use, how their leads reach Propertybase today and where they go missing: enough to say which routes are native, which need a source request or a build, and what to fix first. No obligation to proceed.
Talk to a Salesforce architect who works with Propertybase