A useful property conversation often ends with a question the agent cannot answer immediately. The problem is not saying “I need to check.” The problem is losing the question after the call. Keep unresolved questions in a short log, separate from confirmed property details.
Copy this question log
| Field | Fictional example |
|---|---|
| Property reference | Unit P-18 |
| Exact question | Is a parking space included in this offer? |
| Status | Waiting for confirmation |
| Source to consult | Person responsible for the current offer |
| Owner | Assigned colleague |
| Reply commitment | Agreed calendar date and time |
| Evidence received | Not yet received |
| Client informed | No |
Write one question per row. “Check everything about the apartment” is too broad to close reliably. Split parking, availability and viewing access into separate items if each needs a different source. Record only the information necessary for the enquiry; avoid copying unrelated private messages into a shared log.
Close the loop with evidence
When an answer arrives, record its source and confirmation date before updating the property record. Distinguish an informal recollection from a current written confirmation. If the sources disagree, keep the question unresolved and assign the next verification step. Do not choose the more attractive answer simply because it makes the offer easier to present.
For example, a colleague recalls that parking was included last month. That is a lead for checking, not confirmation of today's offer. The client-facing response can say that the detail is still being verified and give the next update time you can actually meet.
Review the promise, not just the question
A resolved question is not the same as an informed client. Keep a separate indication that the answer was communicated. If the promised reply time passes, send an accurate progress update through the agreed channel rather than inventing an answer. Before a handoff, make sure the next colleague accepts responsibility for open rows.
This is a proposed working template for teams exploring Devzonia. It can be used in an ordinary document or a suitable existing workflow; it does not assert that the platform includes these exact fields or automated verification.
