Portal enquiries sit in a shared inbox
Property Finder, Bayut and Dubizzle emails land in one mailbox. Whoever opens them first takes the client, and the enquiries nobody opens are never followed up.
Propertybase is a real estate CRM that runs inside Salesforce. For a Dubai brokerage it can hold every portal enquiry, listing, agent and offer in one place. Twopir Consulting sets it up around how your brokerage sells and leases: enquiries captured and shared out by Sales Rotation, follow-up rules built in Salesforce Flow, listings sent to Property Finder, Bayut and Dubizzle with the RERA permit (Trakheesi) number attached, and dashboards for every team. We tell you which parts come as standard, which are vendor packages and which we build.
Trusted by 500+ organizations, including brokerages, property managers and real estate investment groups running their sales and listings on Salesforce with Twopir Consulting.












What We Configure
A Dubai brokerage lives on portal enquiries and portal listings. The CRM decides whether an enquiry reaches the right agent and gets a call back, and whether a listing goes live with the details the portals require. These are the six gaps we are asked to close most often.
Property Finder, Bayut and Dubizzle emails land in one mailbox. Whoever opens them first takes the client, and the enquiries nobody opens are never followed up.
Leads are handed out by hand or by habit. Agents question the fairness, and a returning buyer is given to a new agent instead of the one who already knows them.
Nothing tells a manager which new enquiries are still waiting for a first call, so slow follow-up only shows up later as a lost deal.
Each portal gets its own upload, and a missing permit number, location or sub-type stops a listing until someone spots it. Prices and statuses drift between the CRM and the portals.
Budgets, areas and property types are kept in personal notes and chat threads. When a matching listing comes in, nobody is told, and the match leaves with the agent.
Agent performance, portal return and pipeline are put together by hand each week. Team leaders either see every team's clients or none of their own.
Propertybase Salesforce Edition is a real estate CRM, owned by Lone Wolf Technologies, that installs into Salesforce as a managed package. For a Dubai brokerage it holds contacts, buyer and tenant inquiries, properties, sale and rent listings, and offers in one Salesforce org. Front Desk turns portal enquiry emails into records. The Middle East Portal package publishes listings to the UAE portals, and the Sales Rotation package shares new enquiries among your agents. Salesforce itself adds Flow automation, reports, dashboards and the sharing model.
Three parties are involved, and it helps to keep them apart. Lone Wolf licenses Propertybase, owns its roadmap, and has Propertybase Support install the Middle East Portal and Sales Rotation packages. Salesforce is the platform underneath. Twopir Consulting designs and configures the org around your brokerage and builds what the packages do not cover. We implement Propertybase; we do not resell it. The vendor documents the portal package in its Middle East Property Portal Integration guide.
This page covers the brokerage operation: portal leads, rotation, follow-up, listings, matching, reporting and permissions. Propertybase also models projects, buildings and units for developer and off-plan sales, and supports discreet private-client work. Those are separate setups, and we only touch on them here. For the wider rules of selling property in Dubai, see our guide to selling property in Dubai and Abu Dhabi with Salesforce and Propertybase.
We help growing and mid-market companies solve complex CRM, integration and business system challenges, and that is where most Dubai brokerages sit. Enterprise brokerages with several offices and hundreds of agents use the same building blocks at a larger scale. For our full range of Propertybase work, see Propertybase consulting services.
Most of what a Dubai brokerage needs already exists in Propertybase, in one of its vendor packages, or in the Salesforce platform. Custom work is the smaller part, and it should be named before the project starts. This is how we label each piece.
| Capability | What it does for a brokerage | Type |
|---|---|---|
| Contacts, inquiries, properties, listings, offers | The core records: who the client is, what they want, what you have to sell or lease, and the offers made on it. | Standard |
| Front Desk portal lead capture | Turns portal enquiry emails sent to a dedicated address into contacts and inquiries. Dubizzle and Property Finder are on the vendor's list of ready-made parsers. | Standard |
| Inquiry and listing matching | Finds listings that fit a buyer's inquiry, and buyers whose inquiries fit a new listing. Results go out by Quicksend or as a PDF. | Standard |
| Middle East Portal package | XML feeds that Dubizzle, Bayut and Property Finder collect, plus the UAE listing fields, including the RERA permit (Trakheesi) number. | Package |
| Sales Rotation | Assigns new web enquiries to agents in turn, creates a follow-up task and emails the agent. | Package |
| Follow-up SLAs and escalation | Reminders, response-time rules, escalation to a team leader and reassignment, built on the task Sales Rotation creates. | Platform · Configuration |
| Dashboards and agent KPIs | Standard Salesforce reports and dashboards on Propertybase data, designed per role. | Platform · Configuration |
| Permissions by team | Salesforce roles, org-wide defaults, sharing rules and permission sets decide who sees which clients and listings. | Platform · Configuration |
| Lead parsing for portals not on the list | Bayut is not on Front Desk's published parser list, which the vendor says is incomplete. New parsers can be requested from Propertybase Support. Otherwise it is an integration. | Vendor request · Custom |
| WhatsApp, telephony, Arabic interface | Not in the Propertybase documentation. Delivered through a third-party app or a custom integration with the Salesforce org. | Custom |
| Commission splits and payouts | No UAE commission model is documented. Commission structures are built as custom objects and automation in your own namespace. | Custom |
| Feeds or APIs beyond the package | A custom XML or JSON endpoint for a website or partner the package does not serve, built in Apex on live Salesforce data. | Custom |
The split matters for cost and for upgrades. Standard features and packages are maintained by the vendor, and configuration can be maintained by your admin. Custom work is yours to maintain, so we keep it small, document it, and build it outside the managed package (see Propertybase customization). Want this table filled in for your brokerage? Book a discovery call and we will mark up each row against your current setup.
A portal enquiry should become an assigned inquiry with a follow-up task and a deadline, without anyone forwarding an email. This is the path we configure, and what powers each step.
Portal emails go straight to a Front Desk address, not forwarded or copied in, so the parser can read them. Website forms post through Propertybase's web-to-prospect service. Each one creates a contact and an inquiry.
Powered byFront Desk · web-to-prospect (standard)
Each inquiry carries a rotation name. Several rotations can run side by side, each with its own agents. We set them up for sales, leasing or language desks, and use Flow to pick the rotation where the source does not set it.
Powered bySales Rotation (package) · Flow (configuration)
Active members take enquiries in turn on their rostered working days. Enquiries that arrive after 4pm count as the next day's, and a default user catches anything left unassigned.
Powered bySales Rotation (package)
When a known contact enquires again, the rotation can route it to the contact owner, to the previous agent, or to the listing's own agent when the portal listing ID is captured. A separate Front Desk inbox per team can take priority.
Powered bySales Rotation re-enquiry options (package)
The rotation creates a follow-up task and emails the agent. We add the response-time rules on top: a reminder, then escalation to the team leader, then reassignment if the task is still open.
Powered bySales Rotation task (package) · Flow SLAs (configuration)
The agent runs matching from the inquiry, sends a shortlist by Quicksend, and records each suggested property as a linked listing so the client's feedback stays on file.
Powered byInquiry matching · Quicksend (standard)
Need routing by area, price band or language, or weighted by agent capacity? Sales Rotation does not document those rules. We build them in Salesforce Flow alongside it, which is the Propertybase automation work we do for brokerages generally.
In Propertybase a property is the physical unit and a listing is one offer of it, for sale or for rent. One property can carry many listings over time. The Middle East Portal package publishes listings from that record to Dubizzle, Bayut and Property Finder, so each listing is kept in one place instead of three.
| Listing data | What the portal feeds need |
|---|---|
| RERA permit number (Trakheesi) | A required field for UAE portal publishing. Short-term rentals on Property Finder also need the DTCM permit number. |
| Core details | Title, description, price (with a price unit for rentals), bedrooms, bathrooms, size and listing type. |
| Property type and sub type | Chosen from the predefined values the portals accept, not typed freely. |
| Location | Picked with the Dubizzle selector and the Property Finder finder components. The Property Finder location also feeds Bayut. |
| Broker's listing ID and agent | Your own reference for the listing, and the listing agent's details, which the feed turns into an agent ID. |
| Optional fields | Arabic title and description, developer, availability dates, amenities, and portal-specific fees such as service charge and number of cheques. |
What we add on top: brokerage rules for who can approve a listing for the portals, listing status kept in line with offers (an accepted offer marks the listing sold, a reservation marks it reserved), and reports on listings blocked by missing data. Off-market listings simply stay unflagged, so they never enter a feed. Where a website or partner needs a feed the package does not produce, we build it; see Propertybase integration services.
Agents use a CRM when it saves them time on the next call. These are the parts of Propertybase we set up for that, and how each one is delivered.
Every assigned enquiry has a task with a due time, and nothing waits silently.
The inquiry record holds what the client wants, so the next agent does not start from zero.
Configured once in the Control Center, then used from any inquiry or listing.
Offer buttons move the listing with the deal, so availability is never a phone call.
Propertybase runs in the Salesforce mobile app on iOS and Android, with the same records.
Propertybase's own mass email campaigns reach past clients when new stock fits them.
Propertybase reports and dashboards are standard Salesforce ones, so they read live data without exports. The work is deciding what each role needs to see, and making sure the data behind it is captured. These are the dashboards we usually build for a brokerage.
| Dashboard | What it shows | Who uses it |
|---|---|---|
| Portal return | Enquiries, viewings and offers by portal and by listing, so marketing spend follows results. | Owner, sales director, marketing |
| Speed to first contact | Time from assignment to the first completed follow-up, per agent and per team, with overdue tasks listed. | Team leaders, sales manager |
| Agent pipeline | Open inquiries, viewings, offers and closings per agent, against the targets you set. | Agents, team leaders |
| Rotation fairness | Enquiries assigned per rotation member and how returning clients were routed, so the rules can be shown to be fair. | Sales director, admin |
| Listing health | Listings by status, listings cleared for the portals, listings held back by missing data such as the permit number, and time on market. | Listings team, team leaders |
| Offers and reservations | Active, accepted, countered and cancelled offers, and reserved listings, across the brokerage. | Owner, managing director |
A dashboard is only as good as the data under it. That is why rotation, follow-up tasks and offer status are set up first, and why reporting design is a phase of its own in our Propertybase reporting work.
Client lists are a brokerage's most valuable asset, and the one most likely to leave with an agent. Access is controlled by Salesforce's sharing model, not by Propertybase itself. We design it with you, role by role, before any data is loaded.
| Role | Clients and inquiries | Listings |
|---|---|---|
| Agent | Their own contacts and inquiries. Private by default, shared only when a rule says so. | All active listings, so they can match any buyer, while owner details stay limited. |
| Team leader | Everything owned by their team, through the role hierarchy. Can reassign within the team. | Team listings, plus approval of listings for the portals where you want a check. |
| Sales director or managing director | The whole brokerage, read-only by default, with full reporting. | The whole brokerage. |
| Listings or back-office team | Only what their tasks need, through permission sets. | Create and edit listings, permits and portal fields. |
| Admin | System access, with exports limited to named users. | Rotation, matching and portal settings. |
Propertybase uses its own objects in the pba__ namespace, not Salesforce's sales objects. Salesforce Lead, Opportunity, Campaign and Case are not available to Propertybase customers unless they buy Salesforce licences separately, so a brokerage's process is designed on the objects below.
Buyers, sellers, landlords and tenants, with company records for agencies. Owner of the relationship and its history.
What a client wants: the Request object (pba__Request__c) in the API. Carries the rotation name and the matching criteria.
The unit, and each sale or rent offer of it. A listing's record type, sale or rent, is fixed once it is created.
Offers and counter offers drive listing status. Linked listings record which properties a client was shown and what they thought.
Two directions. Listings go out as XML feeds the portals collect. Enquiries come in as emails Front Desk parses into contacts and inquiries.
Website enquiry forms create contacts and inquiries through web-to-prospect, ready for the rotation. Listings can flow back to the site.
WhatsApp and telephony connect through a third-party app or a custom integration, logging conversations against the contact and inquiry.
Custom Apex endpoints serve listing data to partners. Accounting sync carries closed deals and commissions to finance.
Rotations and their members, Front Desk inboxes, matching filters, portal field mapping, page layouts, validation rules, follow-up and escalation flows, reports, dashboards and sharing rules are all configuration.
We deliver them that way, because configuration is what your admin can maintain.
Commission models, messaging integrations, custom feeds and APIs, and lead parsing for sources Front Desk does not read. Propertybase ships in its own locked namespace, so this work sits in your org beside it.
That keeps the managed package upgradeable. See Propertybase API and integrations for the technical side.
The same platform is set up very differently for a leasing desk and a team selling a developer's launch. These are the starting points we see most, and what each one needs.
Two desks share the portals but follow different processes and targets.
A brokerage moving from spreadsheets, email and a basic CRM to Propertybase for the first time.
Propertybase is installed, but agents work around it and leaders do not trust its numbers.
Each branch runs its own leads and listings, and management needs the combined view.
Launches bring a spike of enquiries for one project alongside the resale business.
A luxury team inside a larger brokerage that needs off-market listings and discreet client records.
The value is operational, and you can see it in the CRM itself rather than in a forecast. This is what a well-run Propertybase org looks like day to day.
Portal and website enquiries are assigned by rule, and the rule can be shown to every agent.
Overdue first calls show up on the day, and the escalation runs without a manager chasing.
A second enquiry goes to the agent who already knows the client, not to the next name on the list.
Price, status and permit are edited once and reach every portal from the same record.
New stock is checked against waiting buyers' inquiries, and the brokerage keeps the match when an agent leaves.
Agent and portal performance come from live dashboards instead of a weekly spreadsheet.
Each team sees what it should, and exports are limited to the people who need them.
New agents, rotations and SLA rules are configuration changes, not development tickets.
The length of the project depends on how many teams, portals and rotations you run, how much data has to move, and how much custom work the split table turned up. We scope that in discovery rather than quote a generic number. The general method is on our Propertybase implementation page; this is how it applies to a brokerage.
Portal accounts, permit process, teams and desks, how leads are shared today, what leaders report on, and where deals stall.
DeliverableCurrent-state map and the capability split for your brokerage
The data model on contacts, inquiries, properties, listings and offers; rotation and SLA rules; the sharing model; the dashboards.
DeliverableSigned-off design, custom work named and sized
We coordinate the package installs with Propertybase Support, then configure Front Desk, rotations, matching, portal mapping, layouts and Flow.
DeliverableConfigured org, demoed to each team
Contacts and listings migrated and cleaned, one listing tested per portal before the rest, and test enquiries run through every Front Desk inbox and rotation.
DeliverableValidated feeds and a passed test log
Separate sessions for agents, team leaders, the listings team and admins, then the feeds and rotations switched on in a planned order.
DeliverableLive org, launch runbook, trained users
We watch rotation fairness, overdue follow-ups and blocked listings in the first weeks, adjust the rules, then hand over or stay on.
DeliverableAdmin guide and support plan
These three engagements were Salesforce builds for UAE real estate firms rather than Propertybase rollouts. They are here because the same problems come up: availability agents can trust, listings published from one source, and portal publishing that does not depend on manual uploads. Each figure is scoped to the engagement that produced it.
A Salesforce property inventory system that replaced spreadsheets with live availability and inline inquiry capture.
XML feed generation that serves live Salesforce listings to every external property website from one endpoint.
Custom publishing from Salesforce straight to two UK portals, Zoopla and Rightmove, through Apex and a Lightning component.
The third client moved listing publishing out of Propertybase and into custom Salesforce code to reach two UK portals. For Dubizzle, Bayut and Property Finder, the Middle East Portal package is normally the first choice, and custom publishing is the fallback when a portal or partner needs more than the package sends.
A brokerage CRM project goes wrong when nobody says early which parts are standard and which are custom. We say it in discovery, and build to it.
Front Desk, the Middle East Portal package, Sales Rotation and matching are set up first. Custom work is only proposed where they stop, and it is named in the design.
Inquiries, listings and offers, not Salesforce leads and opportunities that your licence does not include. Your process fits the objects the vendor maintains.
Follow-up rules, sharing and dashboards are Salesforce work. We build them to sit cleanly beside the managed package, so upgrades do not break them.
Inventory, listing feeds and portal publishing for UAE firms, on Salesforce. We know where a portal feed breaks and what a brokerage's agents actually need from the CRM.
You get documented rotations, rules and dashboards that your admin can maintain. When you want us to stay, we run the org with you through Propertybase support and managed services.
Yes, in two directions. For listings, the Middle East Portal package, which Propertybase Support installs, publishes XML feeds that Dubizzle, Bayut and Property Finder collect on a schedule. For leads, Front Desk turns portal enquiry emails into contacts and inquiries, and Dubizzle and Property Finder are on its list of ready-made parsers. Bayut is not on that published list, so its lead emails need a parser requested from Propertybase Support or a small integration.
In a UAE listing field that the Middle East Portal package adds, and it is required for portal publishing. Short-term rentals on Property Finder also need the DTCM permit number. The package's validation rules stop a listing from being cleared for the portals until the required data is present, and we add reports that show which listings are held back and why.
Sales Rotation is a Propertybase package that hands new web enquiries to agents in turn. Each inquiry carries a rotation name, and active members on their rostered working days receive enquiries one after another. The agent gets a follow-up task and an email. Returning clients can go to the contact owner, the previous agent or the listing's agent, and several rotations can run at once, for example one per team.
Yes, with Salesforce Flow. Response-time rules are not a documented Propertybase feature, but Sales Rotation creates a follow-up task for every assignment, and Flow can watch that task: send a reminder, escalate to the team leader and reassign the enquiry if it is still open. This is configuration, not custom code, so your admin can adjust the times later.
Usually only a few. Portal feeds, lead capture, rotation and matching come from Propertybase and its packages, and follow-up rules, dashboards and permissions are Salesforce configuration. Custom work tends to be commission models, WhatsApp or telephony integrations, lead parsing for sources Front Desk does not read, and feeds or APIs the package does not produce. We name each one in the design before any build starts.
Not with Propertybase licences alone. Lead, Opportunity, Campaign and Case are among the Salesforce objects that Propertybase customers cannot use unless they buy Salesforce licences separately. A brokerage's process is built on Propertybase's own objects instead: contacts, inquiries, properties, listings and offers. In practice they cover the same ground for a brokerage.
Yes. Access is set by Salesforce's sharing model: private defaults on contacts and inquiries, a role hierarchy that gives team leaders their team's records, and sharing rules for any exceptions. Listings can stay visible to every agent for matching, while client records stay private. We design this with you before any data is loaded.
A first conversation covers your portal accounts, teams, how leads are shared today and what management needs to see. That is enough to fill in the standard, package, configuration and custom split for your brokerage, and to say what the setup would take. No obligation to proceed.
Talk to a Salesforce architect who implements Propertybase