How Do Property Agents Use PropKaki on WhatsApp?

It is the PropKaki assistant, reached by messaging a number from your own phone. Nothing to install — WhatsApp is already on it.

It runs the same 49 tools as the web app. That is worth being blunt about, because it is the opposite of how most products do channels: there is no lane that works on the website and not here. Valuations, transaction comparables, stamp duty, TDSR and affordability sums, project and block research, market trends, the agent directory, the official-document library, the listing copy, the deck, the video and the prefilled forms all answer on both.

What changes is how the result reaches you, and how much it remembers between messages. Those two things are the reason to use it.

This is the single most confusable thing about PropKaki, so it is worth a table.

This page is the first row. You are the one typing, the answers come to you, and no client sees any of it. The other two are covered in their own guides, linked at the foot of this page.

Four kinds of thing, and they arrive differently.

The answer is a message, the way any reply is.

Result cards — a valuation, a comparables table, an affordability breakdown — arrive as images, sent after the text. There is a cap of two per turn, so a sprawling question returns the two that matter rather than a wall of pictures.

Prefilled paperwork arrives as a document. The filled file is rendered when you ask for it and discarded straight after — it is not kept in storage — so a draft with a client's details in it does not sit somewhere indefinitely.

A listing video takes longer. The request goes into a render queue and the finished MP4 arrives a minute or two later, in the same chat. If a render fails you are told, rather than left waiting.

A deck comes back as an editable .pptx document, built with PropKaki branding from the same deck engine the web slides studio uses.

Yes, and this is the whole argument for using WhatsApp over the app.

On a laptop, producing a deck ends with a file you then have to get to your client — download it, open another app, attach it, write the message. On WhatsApp the deck is already a WhatsApp document, in a chat, on the phone you will send it from. Forwarding it is two taps.

The same holds for a result card. A client asks whether the asking price is fair; you ask PropKaki; the valuation card comes back as an image; you forward the image. What your client receives is a clean, branded card with the numbers and the sources on it — not a screenshot of your own conversation.

That loop is why agents use this channel between appointments rather than saving everything for the evening.

This is the second reason the channel is different, and it is easy to underrate.

Because the thread is continuous and tied to your number, PropKaki keeps a client brief as you work: who they are buying or selling as, the budget, the must-haves, the purpose, the citizenship, whether they already own something, the area. That brief persists for about two weeks, so picking the conversation back up on Thursday does not mean re-explaining Monday.

Two consequences worth knowing:

• It remembers the figures it already gave you on that client, so it will not quietly contradict itself on a valuation two days later.
• It remembers the caveats it has already raised, so it stops repeating the same warning at you every turn.

When you move to a different client, it detects the switch and archives the previous brief rather than blending them — so client B never inherits client A's must-haves. It keeps the last few archived briefs, and you can search back over older conversations by keyword when you need something from one.

The same, and not by coincidence.

The tool registry is shared, and the filter that would remove tools on WhatsApp is empty — every lane the app can reach, WhatsApp can reach. More importantly, the lanes call the same underlying modules as the website's own tools, so a valuation asked on WhatsApp and the same valuation asked on the web are not two implementations that might drift; they are one, read twice.

Billing is shared too. Credits come out of one balance across the app and WhatsApp, and the same plan rules apply — the four client-production lanes (listing copy, deck, video, forms) need Pro or above on either channel.

If you are signed in, your client book is shared as well: named-client work you do on one channel is there on the other.

Three real differences, none of them about capability.

A deck opens differently. On WhatsApp you get the rendered .pptx as a file. On the web, the same lane hands you a pre-filled link into the slides studio instead, where you can edit sections, change the template and swap photos before exporting. If you intend to rework the deck, start it on the web; if you intend to send it, WhatsApp is fewer steps.

Cards are images, not interfaces. On the web a result card is live — you can expand it and follow it further. On WhatsApp it is a picture: better for forwarding, not something you can click into.

A video is not instant. It renders in a queue and arrives shortly after, rather than appearing as you watch.

Everything else — the tools, the data, the numbers, the honest declines — is the same product.

It declines rather than improvises, and the gaps are deliberate and listed:

• Unit-level detail it does not hold — the stack, facing or view of a specific unit; a new launch's live remaining units; MCST or maintenance fees; who bought a particular unit.
• Scheme specifics — school ballot odds, or exact HDB grant amounts and structured eligibility.
• Live external state — today's bank mortgage packages and rates.
• Speculation — en-bloc potential and reserve prices, per-unit lease-decay valuation, co-broke and commission norms.
• Analysis not yet built — buy-now-or-wait forecasts and multi-year appreciation calls.

When you hit one it tells you what it cannot do and offers what it can, rather than producing a confident number you would then have to defend. On a channel where you might forward the reply straight to a client, that behaviour matters more than it does at a desk.

No — you can message the number and start working without an account. Creating one and signing in links the two channels, which means your named-client work is shared: a client book built on the web is available on WhatsApp and vice versa. Credits come out of one balance either way.

Yes. You can send images, PDFs and documents on WhatsApp, and the same intake works on the web app. That is how a brochure, a price list or a floor plan gets into a conversation so the assistant can answer against it rather than in general terms.

No. This is a one-to-one thread between you and PropKaki's own number — no client is in it and no client sees it. If what you want is an assistant that answers your clients in your name, that is a different product with its own guide, linked below.

What this page describes. PropKaki's assistant as reached over WhatsApp by an agent: the shared tool set, how each kind of result is delivered, what the running client memory holds and for how long, and the three genuine differences from the web app.

The tool count. 49 lanes, read from the product's own registry rather than estimated. The filter that would remove tools on WhatsApp is empty, which is why this page says the sets are identical rather than "broadly similar".

Delivery. Result cards are sent as images after the text reply, capped at two per turn. Filled paperwork is rendered on request and discarded rather than stored. Listing videos render in a queue and arrive shortly after. Decks are delivered as an editable .pptx on WhatsApp and as a pre-filled studio link on the web.

Memory. The client brief persists for about two weeks and a small number of previous briefs are archived when you switch clients.

What this page does not claim. No time saved, no comparison of answer quality between channels, and no benchmark against any other assistant.

This is general information about a product, not financial, legal or professional advice.