Yes, for the questions your own records already answer: which instalment is next and when it is due, what has been received, where the signed sale agreement is, and the registration status. AI answers from the buyer's file in Arabic or English. Bank details, handover commitments, contract changes and disputes always go to a named person on your team.
#Key takeaways
- Most off-plan buyer messages are status questions the CRM already holds an answer to.
- AI answers only from the buyer's own file and published project updates, never from general knowledge.
- Bank details are never sent or changed by AI; they come from the signed agreement and a person confirms them.
- Handover dates, contract changes, cancellations and complaints are handed to a person with the full thread.
- A well-kept buyer portal may be enough; a workflow earns its place when buyers ask on WhatsApp in two languages across several projects.
#What does a developer's customer team handle?
After the sale, buyers message the sales agent who sold them the unit, the customer relations inbox and the call centre, often all three. They ask for a statement of account, a copy of the sale agreement, their registration certificate, the next instalment date, construction progress and whether the handover date has moved. Many are overseas buyers writing in English; many write in Arabic.
The customer relations officer looks each answer up in the CRM, the finance system and the document store, then types it into WhatsApp. The sales agent has moved on to the next launch and forwards everything.
#Which questions can AI answer, and which must it not?
- answer from the file: next instalment and its due date, instalments received, receipts, copies of the signed agreement and registration documents, the buyer's own contact details on file.
- answer from published updates: construction progress the developer has already published, in the same words.
- hand to a person: any change to the payment plan, late payment, handover dates beyond what is published, cancellations, resale and assignment, complaints, and anything legal.
- never: send, confirm or change bank account details in a message; those come only from the signed agreement and the official escrow record.
#Why do bank details deserve their own rule?
In Dubai, buyer payments for off-plan units go into a project escrow account under Dubai legislation portal, law no. 8 of 2007, checked november 2026%20of%202007.html), and legal guidance for developers, such as Mondaq, checked november 2026, treats escrow compliance as a core obligation before selling off-plan. Buyers need to know exactly where money goes.
That makes bank details a target for fraud: a message that looks like it is from the developer, with a new account. A workflow that never sends or changes bank details, and tells buyers so, removes one opening. Prompt injection, ranked first in the OWASP top 10 for LLM applications, is another reason the AI only reads from records and cannot act on what a message tells it.
#A buyer-query playbook for developers
- Pull last quarter's buyer messages and tag them: status, documents, payment plan changes, handover, complaints. Most teams find a few question types dominate.
- Make the buyer file complete: agreement, payment schedule, receipts, registration, contact preferences, language.
- Write the answer rules: which question types AI may answer, from which fields, and which always go to a person.
- Let AI draft answers in the buyer's language; a customer relations officer approves until the drafts stop needing edits, then automatic sending for statuses only.
- Handover to a person includes the thread, the buyer file and a one-line summary, so the buyer never repeats themselves.
- Review a sample each week with the head of customer relations.
Measure first-reply time, the share of messages answered without a handover, and complaints about wrong or missing answers.
#When is a buyer portal enough?
If your buyers already log into a portal or app that shows their schedule, receipts and documents, and they actually use it, push them there first. A reply template that links to the portal can cut a lot of messages without any AI.
A workflow earns its place when buyers ignore the portal and use WhatsApp, the developer runs several projects with different schedules, and the customer team answers the same status questions in two languages all day. See whether AI can answer WhatsApp customers in Gulf Arabic.
#Where does Stennir fit?
AI consulting from Stennir ranks five workflows across sales and customer relations, each with a cost and payback case, and recommends one build with its scope and hosting region. AI implementation builds buyer answers into your CRM and WhatsApp with the officer approving, then AI training works with the customer team on the real queue.
We are
Stennir builds a buyer-query workflow that answers only from the buyer's own file, hands everything else to a named person, and never touches bank details.
We aren't
Stennir is not a sales agent, a payment collector or a source of legal advice to your buyers.
#What should a head of customer relations do next?
Tag a sample of recent buyer messages by type and count the ones your records already answer. That is your case. See AI for sales teams, then take the free readiness assessment or book a 30-minute call.
#Common questions
Does it work for buyers who write in Arabic and English?
Yes. Arabic and English are fully supported, including Gulf dialect and messages that mix both, and the answer goes back in the buyer's language. Other languages common among overseas buyers are available on request, tested first on your own message history, with a person approving until the tone is right.
Can AI tell a buyer the handover date?
Only the date and wording the developer has already published for that project, quoted as published. Any question about a delay, a change or what the buyer is entitled to goes to a named person with the thread attached. AI does not interpret the sale agreement or make commitments on the developer's behalf.
What stays with us?
The accounts, the buyer data, the answer rules, the logs and the off switch. The workflow runs in your systems and the hosting region your rules require, under the UAE and Saudi data protection laws. If you stop working with Stennir, the records and the process stay with you.
What could go wrong?
An answer from an outdated schedule, a status read from the wrong unit, or a fraudulent message trying to change where a buyer pays. That is why AI reads only live records, unit matching is checked, bank details are excluded from the workflow entirely, and every answer is logged with its source field.
