Can AI Reply to Your Clients on Your Own WhatsApp?
Your assistant answering on the number your clients already message you on — what it can reply with, what you keep control of, and where it currently stands.
Yes. PropKaki can run your AI assistant on your own WhatsApp number, so clients who already have you in their chat list get an immediate, grounded answer instead of silence. It is the same assistant as your public link, answering property questions from real URA and HDB records, recording what a client is looking for, sharing your listings and booking viewings. Every conversation lands in the same inbox as your link, and you keep bot-level controls over what it does. It is currently being rolled out to agents one at a time rather than being self-serve.
Your public assistant link solves a problem you have with strangers. It does nothing for the twenty people already in your chat list, because they will never think to tap a link — they will just message you, at 11pm, the way they always have.
That is what this is for: your assistant answering on your own number, for the clients who already have it. This page covers what it replies with, what stays under your control, and — honestly — where it currently stands, because it is not yet something you can switch on yourself.
Can AI reply to your clients on your own WhatsApp?
Yes. PropKaki can answer on your own number — the same assistant as your public link, for the clients who already have you saved.
Yes. The same assistant that runs on your public PropKaki link can answer on your own WhatsApp number, so a client who already has you saved gets a grounded reply instead of a read receipt.
The distinction from your link matters. A link works on people who do not have your number — someone off your Instagram bio, a portal profile, a QR on a name card — and part of its job is collecting a contact. This works on people who already have you, which means there is no link to share, nothing for them to install, and no contact to capture. Its job is coverage: the message that lands while you are in a viewing gets a real answer at the time it was asked.
One honest caveat up front, covered properly further down: this is being rolled out one agent at a time, not switched on from a settings page.
Whose WhatsApp is this — and how is it different from you using PropKaki?
This is your clients messaging your number and your assistant replying. You using PropKaki on WhatsApp is a separate thing on PropKaki's number.
PropKaki touches WhatsApp in two completely different ways, and confusing them is easy.
| Whose number | Who talks to it | What it is for | |
|---|---|---|---|
| Your reply assistant (this page) | your own number | Your clients | Answer the message you could not get to |
| Your assistant — link | none; a web link you share | Your clients | Catch an enquiry from someone who does not have your number |
| PropKaki on WhatsApp | PropKaki's number, in your WhatsApp | You | Price a listing, run numbers, produce client work |
This page is the first row: your clients, your number, your name on the reply. The third row is you doing your own research, privately, and no client is ever in that thread. Both have their own guides, linked at the foot of this page.
What does it actually reply with?
Grounded property answers from real transaction records, with the working shown — not a deflection or a canned holding message.
It answers the question, which is the entire difference from an auto-reply.
A standard WhatsApp Business away message says you are unavailable. This reads what the client asked and answers it: what a flat in their block has been transacting at, what the stamp duty comes to, whether their timeline works, what the MOP rule actually says. The figures come from real URA caveat and HDB resale records with the period and the count attached, not from a model's recollection.
It runs the same grounded assistant as your public link, so a client gets the same quality of answer whichever way they reached you.
And where it cannot ground something — a specific unit's facing, live remaining units at a launch, today's mortgage packages — it says so and points them to you, rather than inventing a number that arrives under your name.
What else can it do besides answering?
Record what the client is looking for, talk through your own listings, book a viewing or a consultation, and hand you the thread.
Five things beyond the answer, each one a switch you hold:
- Record what they are after — budget, timeline, buying or selling, which area — picked up from the conversation rather than an interrogation.
- Take their contact details when they volunteer them.
- Talk through your own listings, drawn from your verified record rather than invented.
- Book a viewing.
- Book a consultation for the client who wants to talk about their move rather than one unit.
All five arrive switched on by default, and you turn off whichever you do not want. That is worth stating clearly, because it is the opposite of what people usually assume: the assistant starts fully capable and you narrow it, rather than starting inert and being assembled.
What stays under your control?
Whether it is live at all, whether it answers anything beyond property, which skills run, and how much it can ever spend.
Four levers, and they apply across the assistant rather than per conversation:
- Live, paused or draft. Pausing stops it answering, immediately.
- AI on or off. A separate switch from pausing, for when you want the page or line to exist without the assistant replying.
- Property questions only. Turn this on and it declines anything off-topic instead of obliging.
- Spending caps. A daily cap per conversation and a monthly cap across all of them. It stops at your number, not at ours.
On top of that, every message it sends is in your inbox to read, message by message with the time on it. Nothing happens in your name that you cannot go back and check.
Being straight about a limit: these are assistant-wide settings, not per-chat. There is no switch today that mutes it for one specific client while it keeps answering everyone else.
Where do those conversations end up?
In the same inbox as your public link, so a client's history does not split across two places.
One inbox.
Whichever door a client came through — your public link, your own WhatsApp number, or the app — the conversation lands in the same place, with the channel marked on it. That matters more than it sounds: if the two were separate, a client who first tapped your link and later messaged your number would exist twice, and you would be reading half a history in each.
You get the full transcript, timestamped, along with whatever the assistant worked out about what they are looking for.
How do you get it, and what stage is it at?
By asking. It is being rolled out one agent at a time and is not yet a setting you can switch on yourself.
Honestly: not from a settings page, not yet.
Connecting a business's own WhatsApp number to a third-party assistant is not something a product can simply toggle — it runs through WhatsApp's own approval process for providers, and that approval is a gate outside PropKaki's control. Until it clears, agents are being onboarded one at a time, by hand.
So the way in is to ask, and PropKaki walks you through connecting the number and setting the assistant up.
What you can do today without waiting is run the same assistant on your public link, which is live for any CEA-registered agent and needs no approval from anyone. Most agents start there; the number is an addition to it, not a replacement.
No date is being promised here, because the timing is not ours to promise.
What is the biggest mistake agents make with an auto-reply?
Using one that deflects. A holding message tells a client you are unavailable — which is what they already suspected.
The usual auto-reply confirms the fear rather than answering the question.
"Thanks for your message, I'll get back to you shortly" tells a client, at the moment they are deciding whether you are the responsive one, that you are not available. They then message somebody else — not out of disloyalty, but because they had a question and you did not answer it.
The thing worth automating is not the acknowledgement. It is the answer. A client who asks what their flat is worth at 11pm and receives a real figure with the transactions behind it has had their question answered by you, at 11pm, whether or not you were awake for it.
Do your clients need to install anything?
No. They message the number they already have for you, in the WhatsApp they already use.
No. There is nothing for a client to download, no account to create and no link to tap. They message the number they have always messaged. From their side nothing about the conversation is new except that a reply arrives quickly.
Can you take over the conversation yourself?
Yes — you read every message and reply as normal. What does not exist yet is a per-chat mute that silences it for one client only.
You read every conversation in full and can reply yourself at any time; it is your WhatsApp. What is not built yet is a per-conversation switch — a way to mute the assistant for one specific client while it keeps answering everyone else. The controls today are assistant-wide: pause it, switch the AI off, or restrict it to property questions only.
What happens if it does not know the answer?
It says so and points the client to you, rather than guessing.
It declines and hands off. There is a maintained list of things it does not have — a specific unit's stack or facing, a launch's live remaining units, today's bank packages, en-bloc speculation — and on those it tells the client it cannot answer properly and points them to you. On a channel carrying your name, an assistant that occasionally says "I don't know" is the only kind worth running.
Methodology and sources
Capabilities and controls are described as currently built. Where something is planned rather than shipped, this page says so instead of implying it.
What this page describes. Running the PropKaki assistant on an agent's own WhatsApp number: what it replies with, the five skills and their default state, the controls available today, where conversations land, and the current rollout stage.
Defaults. The five skills — recording what a client is after, taking contact details, sharing your listings, booking viewings and booking consultations — are on in a new assistant's configuration and are switched off individually.
Controls are assistant-wide. Pause, AI on/off, property-questions-only, and daily and monthly spending caps all apply across the assistant. A per-conversation mute is not built, and this page says so rather than describing it as available.
Rollout. Connecting an agent's own number depends on an external approval process for messaging providers. Agents are onboarded individually while that stands, and no launch date is claimed.
What this page does not claim. No response-time figure, no number of enquiries handled, no conversion rate, and no comparison against other auto-reply tools.
This is general information about a product, not financial, legal or professional advice.
Got a question this raised? Ask PropKaki.
Take any point from this analysis and apply it to your own project, budget or decision.
PropKakiFor most buyers this year, staying well within budget beats trying to time the market.