For real estate agencies in Singapore, Dubai & Malaysia

Every agent's WhatsApp leads, in one CRM the agency actually owns

Your leads are scattered across your agents' personal phones, answered whenever someone happens to look, and gone the day that agent resigns. This is the system that captures every WhatsApp conversation into your CRM, replies in seconds, screens the enquiry with AI, and assigns it to the right agent by rules instead of by reflex.

An agency that cannot see its own WhatsApp is running blind

You pay for the listings. You pay for the campaigns. The enquiries they generate arrive as WhatsApp messages on thirty or three hundred personal handsets, and from that moment the agency has no idea what happened. How many came in. How many got a reply. How fast. How many turned into viewings. Which agent is sitting on twenty leads they will never work.

Underneath that, three concrete failures: speed to lead (the buyer messaged four agencies and yours answered third), screening (agents burn half-days on viewings that were never going to convert), and assignment (a duty roster that is fair but slow, or a group chat where the fastest thumb wins).

None of these is solved by buying a CRM and asking agents to fill it in. They are solved by connecting WhatsApp to the CRM directly, so the data arrives without anyone typing it. Five parts, below.

Your pipeline is sitting on forty personal phones

Ask most agency principals how many leads the office received last month and the honest answer is a guess. Not because nobody is counting, but because there is nothing to count: enquiries arrive as WhatsApp messages on individual agents' handsets, get worked or not worked, and leave no trace anywhere the agency can see.

That has a second, sharper cost. When an agent leaves — and in this industry they do — the entire relationship history leaves with them. Every negotiation, every "call me after CNY", every buyer who said no to one unit and yes to a similar one, walks out on a phone you do not own. The agency paid to generate those leads and keeps nothing.

Connecting each agent's WhatsApp Business number to one CRM workspace fixes both at once. Every conversation becomes a contact record the agency owns, tagged with the number it arrived on, with WhatsApp recorded as the lead source. Nothing changes for the agent's daily routine. See how that works on the WhatsApp integration for Twenty CRM page.

  • Every agent's WhatsApp number feeding one CRM workspace
  • Leads owned by the agency, not by whoever holds the handset
  • Contact history survives agent turnover and team transfers
  • A real answer to "how many leads did we get last month, and from where?"

Speed to lead, when the buyer is messaging four agencies

A buyer who sees a listing does not send one enquiry. They send four, in the same two minutes, to whichever agents the portal surfaced. In practice the deal goes to whoever replies first with something useful — not to whoever knows the property best.

Which means your agency's conversion rate is partly a function of whether a particular agent happened to be free at 9:40pm. That is not a strategy, it is a coin flip, and it is the single most fixable leak in an agency's funnel.

An automated first reply goes out in seconds — acknowledging the enquiry, confirming the listing is available, and asking the first qualifying question — while the CRM simultaneously creates the lead and starts the clock on time-to-first-human-response. The buyer stops waiting; you start measuring.

  • Automated first reply within seconds, on every WhatsApp number
  • Listing availability confirmed without waiting for an agent
  • Time-to-first-response tracked per agent, per team, per branch
  • After-hours and weekend enquiries covered like weekday ones

Lead routing and assignment across the whole roster

Most agencies allocate leads one of two ways: a duty roster that is fair but slow, or a group chat where the fastest thumb wins, which is fast but corrosive. Neither survives contact with volume, and both produce the same argument at month end about who was given what.

Rule-based lead assignment settles it in the second a lead is qualified. Round robin within a team, weighted by current workload so your top producer is not handed forty leads they cannot service. Routed by listing, by district or project, by language, by price band, or by whoever is actually on duty. The moment the owner is decided, three notifications fire: the enquirer gets a confirmation, the assigned agent gets the full lead detail pushed to them, and the team leader gets visibility without chasing anybody.

Then the system enforces what happens next. A follow-up task with a deadline is created on assignment; a reminder fires before it lapses; an escalation reaches the team leader if it lapses anyway, and the lead can be reassigned rather than left to rot. The same mechanics are detailed on our lead management page.

  • Round robin with workload weighting, or rules by district, language or price band
  • Duty roster and on-call logic reflected in the routing
  • Enquirer, assigned agent and team leader all notified in the same instant
  • Deadlined follow-up tasks, reminders, escalation and automatic reassignment
  • A timestamped allocation record that ends the month-end argument

See WhatsApp conversations in the CRM, without reading over shoulders

Agency management wants to know what is happening in the pipeline. Agents do not want a manager scrolling their personal chats. Those two things sound incompatible, and the usual compromise — asking agents to summarise conversations into a CRM at the end of the day — is a task nobody does properly, ever.

The integration takes the middle path. The conversation is attached to the lead record in the CRM: the number it came in on, WhatsApp as the lead source, and an activity timeline of what was written against that lead and when. Whoever picks the lead up next sees the history rather than a bare phone number. Nobody had to type it in.

Agents keep their own WhatsApp Business number and keep replying in WhatsApp exactly as they do now. That matters more than it sounds — the graveyard of agency CRM projects is full of tools that asked agents to change how they message. This one does not, which is why it actually gets adopted.

  • WhatsApp conversations visible on the CRM lead record, no manual logging
  • Every contact tagged with the WhatsApp Business number it arrived on
  • Activity timeline of what changed on the lead and when
  • Agents keep their number and their habits — adoption is not a fight

AI that screens the enquiry before the agent invests an afternoon

A viewing costs an agent half a day once travel, keys and waiting are counted. A meaningful share of enquiries were never going to convert: budget nowhere near the asking price, a tenant who wanted a different district entirely, a buyer eighteen months from being financing-ready, or someone who has already engaged another agent.

An AI agent on the same WhatsApp number establishes that inside the conversation, in the enquirer's own language, at whatever hour they messaged — budget band, timeline, tenant or buyer, preferred areas, financing readiness, existing representation. Each answer is written to the CRM as a structured field, so the agent opens a screened lead with a profile instead of "Hi, is this still available?".

It also books the viewing. Our Panthrr agents respond, profile and schedule around the clock with unlimited conversations and no per-message charge — and everything they capture flows into the CRM through the same integration. Both are on our products page.

  • In-conversation screening: budget, timeline, area, financing, representation
  • Structured CRM fields, not a paragraph someone has to read
  • Viewings scheduled automatically into the agent's calendar
  • Multilingual — English, Mandarin, Malay, Arabic, Hindi
  • Always on: 2am enquiries handled like 2pm ones

The product underneath all of this

WhatsApp Integration for Twenty CRM

Everything above rests on one piece of software we build and maintain: the Twenty WhatsApp integration. It connects your agents' WhatsApp Business accounts to a single Twenty CRM workspace — cloud or self-hosted — so every conversation becomes a contact automatically, tagged with the number it arrived on, with WhatsApp as the recorded lead source and a full activity timeline. It installs from inside Twenty in minutes and needs no code, and your agents never change how they message.

Singapore, Dubai and Malaysia

The same WhatsApp problem, shaped differently by how each market's agencies are structured.

Singapore

Enquiries from the major listing portals land on CEA-registered salespersons' personal WhatsApp within seconds of a listing going live, and the same buyer is usually talking to several agencies at once. Agency-level visibility is the gap: leads generated by the firm end up as private chat threads, and co-broke arrangements make clean, provable allocation matter.

Dubai

Brokerage teams are large, multilingual and high-turnover, and enquiry volume from the property portals and Meta campaigns is relentless. WhatsApp is the default channel for buyers, tenants and other brokers alike, which makes per-agent numbers feeding one CRM — and an audit trail of lead allocation — the difference between a managed pipeline and forty private ones.

Malaysia

Registered negotiators work across states and price segments, often on their own handsets, with buyers messaging in English, Malay and Mandarin. Leads come from the local portals and Facebook straight into WhatsApp. Without a bridge into a CRM, an agency's own lead spend effectively becomes the personal property of whoever answered first.

Ten years in real estate, from three sides of the same problem

Two technical founders, a decade in residential real estate technology. We did not arrive at agency WhatsApp from the outside:

  • Inside the classifieds — we helped introduce the WhatsApp and enquiry systems that the listing portals run on today. The enquiry flood now hitting your agents' phones is partly our doing.
  • Alongside agents — we built the CRMs and daily tools property agents actually use, which is how you learn the difference between software agents tolerate and software they adopt.
  • As tenants and buyers — navigating the same broken search, chasing the same unanswered messages, from the other side of the conversation.

We built this because nobody enjoys the WhatsApp mess — not the agents drowning in it, not the buyers and tenants chasing replies, not the landlords waiting on updates. And because we write the software ourselves, when your co-broke rules or your roster logic is unusual, we build for it instead of explaining why the platform cannot.

What changes

The agency owns its leads

Every WhatsApp conversation becomes a CRM record the firm controls, so a departing agent does not take the pipeline with them.

Every enquiry gets a reply while the buyer is still looking

An automated first response goes out in seconds, on every number, at every hour — not whenever an agent next unlocks their phone.

Allocation stops being an argument

Rule-based routing with workload weighting, plus a timestamped record of who was assigned what and when.

Agents spend their afternoons on viewings that can close

AI screening filters out the enquiries that were never going to convert and hands over the ones with a real profile attached.

Management sees the pipeline in real time

Leads, response times, conversion by agent, team and branch — in dashboards, not in a spreadsheet someone updates on Friday.

Frequently Asked Questions

Find out what your agency's WhatsApp is actually costing you

Start with the product page to see how WhatsApp and Twenty CRM fit together, or book a call and we will map where your enquiries are going today.