Why unknown answers deserve their own test
An AI chatbot for a real estate agency in Dubai should handle an unanswered property question as carefully as a confirmed fact. A fluent reply is not evidence that the price, availability or viewing slot is current. Use the following acceptance exercise when briefing a developer. It describes proposed behaviour to request and demonstrate, not a claim that every feature is already available from Devzonia.
Prepare a small approved property record
Create a fictional test listing, DX-TEST-01, with two bedrooms and a confirmed annual rent of AED 120,000. Leave the service-charge field blank and mark the next available viewing slot as awaiting agent confirmation. Give the record a verification time and a named internal owner. Keep the test listing outside public inventory. The amounts and reference here are examples, not market prices or available properties.
Run four conversations
First ask the annual rent: the assistant should return AED 120,000 with the correct annual period from the approved record. Next ask the service charge: it should say that this information has not been confirmed and offer an agent check. Then ask whether tomorrow at ten is booked: it must distinguish a viewing request from a confirmed appointment. Finally provide an older conflicting price in the conversation: the assistant should flag the conflict or follow the agreed source rule, rather than silently replacing the approved record.
Define the handover message
A useful handover contains the property reference, the exact unresolved question, the information already checked and the next responsible team. Example: “For DX-TEST-01, please confirm the service charge. The approved record contains no value. No amount was quoted to the customer.” Ask how a customer learns that the request was received. Do not promise a response time that the agency has not staffed and agreed.
Record evidence and decide
For each case, record the prompt, approved source, actual reply, expected behaviour, pass or fail, owner and correction. Pass the missing-value case only when the assistant avoids inventing an amount and preserves the unresolved question. Repeat a failed case after the relevant correction; do not treat a rewritten demo as evidence that all conversations are reliable. Check the same situations in both English and Arabic, including whether “annual” remains explicit.
Turn the test into a development brief
Send Devzonia your approved source fields and these four scenarios to discuss scope. Ask which parts require configuration, integration or new development, and agree the evidence needed for acceptance. Link this exercise to your main agency CRM requirements instead of building another competing general CRM page. Before launch, appoint someone to review unanswered questions and remove stale source records. A successful test supports this narrow workflow; it does not guarantee every future answer.
