Websites, Software & Automation for Real Estate
For brokerages and developers' sales teams in Dubai, the website is only one of several places a buyer shows up. We build the listing, enquiry and routing systems that get every lead to the right agent and keep it on the company's record.
Where brokerages lose enquiries
A typical Dubai brokerage receives leads from two or three property portals, its own website, WhatsApp, Instagram and phone calls. Each source arrives in a different format, often by email notification, and someone copies it into the CRM or forwards it to an agent. The same buyer enquires about three listings on two portals and becomes five records. An agent replies from a personal WhatsApp number, and when that agent leaves, the conversation history leaves too.
Listings have the mirror-image problem. Prices, availability and permit references are edited in one place and forgotten in another, so a unit that was let last week is still generating enquiries. The fix is rarely a new website on its own. It is a clear source of truth for listings and leads, with the website, portals and WhatsApp all reading from and writing to it.
The workflows we build for
- Listings
- One listing record with reference, community or project, unit type, price, status and the advertising permit reference that Dubai listings need. The website renders from it, portal feeds are generated from it, and a status change to sold or let removes the listing everywhere at once instead of relying on someone to remember.
- Off-plan enquiries
- Project pages built around what off-plan buyers actually compare: developer, handover date, payment plan, floor plans and unit mix. Brochure and floor-plan requests capture the project and unit interest, not just a name and phone number, and route to the agents assigned to that launch. Launch pages need to hold up under a traffic spike from a campaign going live.
- Portal leads
- Leads from property portals are pulled in through the portal's API, webhook or CRM connector where the portal provides one, and parsed from notification emails where it does not. Each lead is tagged with portal, listing reference and campaign, and matched against existing contacts by phone number so a returning buyer is not treated as new.
- WhatsApp-first buyers
- Many buyers, especially overseas investors, will message before they will fill in a form. Click-to-chat links on each listing pre-fill the listing reference, so the first message already says which unit it is about. On Meta's WhatsApp Business Platform, the conversation lands in a shared inbox or the CRM, agents reply freely within the 24-hour customer service window, and follow-ups after that use approved templates sent only to buyers who opted in. See WhatsApp automation.
- CRM and agent assignment
- Assignment rules you control: by listing owner, project, community, language or a round robin within a team. If the assigned agent does not acknowledge a lead within a window you set, it is reassigned and the team lead is told. The lead belongs to the company's CRM, not the agent's phone, and every touch is logged against it.
One WhatsApp enquiry, end to end
Buyer taps WhatsApp on a listing
The message opens with the listing reference already filled in.
The CRM creates or updates the contact
Matched by phone number, tagged with source, listing and language.
Assignment rules pick an agent
The listing agent if available, otherwise the next agent on that project or community.
The agent acknowledges or the lead moves
An unacknowledged lead is reassigned after your chosen window, and the reassignment is recorded.
A viewing is booked
The viewing slot goes on the agent's calendar and the buyer gets a confirmation with location details.
Follow-up respects the channel rules
After the 24-hour window, reminders go out only as approved templates to opted-in buyers, and the outcome is recorded against the deal.
Services that apply
- Web developmentListing search, project pages and fast, bilingual property sites.
- API and system integrationPortal lead intake, CRM sync and listing feeds.
- Workflow automationAssignment rules, reassignment timers and follow-up tasks.
- WhatsApp automationShared inbox, templates, opt-in capture and CRM logging.
- AI agent developmentAnswering listing questions and collecting budget and timing before an agent picks up.
- Analytics and conversion trackingLeads and viewings reported by portal, campaign and listing.
Relevant evidence
This page describes capability and approach rather than client results. We show brokerage work only with the client's permission and with its status labelled, and on a call we would rather walk through how the listing and lead-routing flow above would work with your portals and CRM than quote numbers we cannot share. Labelled work is listed under case studies.
Implementation risks
- Portal integration depends on each portal's API access and terms. Some leads may only be available through notification emails, which break when the email format changes.
- Permit references and listing status are only reliable if one person or process owns them. Automation spreads bad data as fast as good data.
- Agents who are used to working from their own phones need a reason to use the shared inbox. Rollout usually starts with one team.
- Moving an existing WhatsApp number onto the WhatsApp Business Platform needs checking first: what happens to chat history and to the number's use in the WhatsApp Business app.
- Marketing messages to past enquirers need a lawful basis and opt-in under the UAE PDPL and WhatsApp's own rules. Old contact lists often lack both.
- Migrating years of CRM or spreadsheet data is a project in itself. We usually migrate active deals and recent contacts first.
Where to start
Send us a list of your lead sources and the CRM you use today, or tell us you do not have one. We will map the gaps before recommending a build. Request a project proposal.

