NovKeeping a buyer informed when there is no answer yet
How to communicate a pending answer without inventing dates, hiding uncertainty behind status language, or making the buyer repeat the same question.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
Waiting becomes frustrating when the buyer cannot tell whether anything is actually happening. “We are checking” may sound reassuring the first time. By the third message, it can become a placeholder that hides the fact that nobody has a confirmed answer yet.
I think a pending answer deserves the same precision as a final one. A dramatic explanation or a stream of updates would add noise. They need to know what is known about the delay, what is not known, and whether the unanswered point now affects another decision.
Suppose a buyer has asked whether a particular service forms part of the terms for one apartment. I do not yet have confirmation. The useful status might be very simple: the question has been sent to the party responsible for confirming the service; no confirmation has been received. If a document is being checked, I can say that. If no response time has been given, I should not manufacture one.
“Pending” should describe an actual state
A status word is useful only when it corresponds to something concrete. “With the developer” means the question was sent and accepted by the relevant contact. “Waiting for the document” means we know what evidence is missing. “No reply yet” means exactly that. These are more informative than a general “in progress,” even though none of them produces the answer the buyer wants.
I also avoid turning guesses into explanations. If the other side is silent, I do not know whether they are busy, waiting for an internal approval, checking records, or simply slow to respond unless somebody has told me. Inventing a plausible reason may reduce tension for a moment, but it gives the buyer false context.
Dates need the same discipline: a promised update date should be explicit even when the substantive answer is not ready. A promised date should come from someone who can reasonably stand behind it. If no date exists, saying “I do not have a confirmed timing yet” is more useful than choosing tomorrow because tomorrow sounds acceptable.
A useful update repeats the question, not just the delay
When several issues are open, people can lose track of what each status refers to. I prefer an update that carries the subject with it: “We are still waiting for confirmation of whether the storage room is included with this specific unit.” The buyer can see immediately that the original question has not been replaced by a more general conversation.
This matters when a reply comes back but does not actually answer the question. A sales team might say, “Storage is available in the building,” while the buyer asked whether a particular room is included in the purchase. A message has arrived; the question remains open. Closing it because somebody replied would create a false sense of completion.
Silence can become part of the decision without becoming evidence against the property
There is a point at which the absence of an answer changes the process. Not because silence proves a problem, but because the buyer has their own timetable. They may need to choose between properties, book travel, or decide whether to commit funds elsewhere.
At that stage, the conversation should move from “When will they reply?” to “What do we do if this remains unanswered?” Can the buyer proceed while treating the condition as unknown? Is the point important enough to pause? Is there another property that does not depend on the same unresolved term? These are decision questions, not communication questions.
An unanswered question remains unanswered. It should not silently become a yes because a deadline is approaching, and it should not automatically become a no because the delay feels suspicious.
Different open questions need different weight
One reason long property conversations become confusing is that every pending point is grouped under one status. A minor furnishing detail and a material payment condition can both be “awaiting confirmation,” yet they should not carry equal weight in the decision.
I prefer to keep the buyer's attention on consequence. Which pending answer could change the transaction? Which one would merely refine how the home is used later? Which has a workaround? Which has no reasonable substitute? This prevents a long list of small unknowns from obscuring the one that actually matters.
Good communication does not pretend to control the other side
Client support cannot guarantee the speed of every third party. What it can do is preserve clarity. One unanswered question should not require chasing several contacts, reconstructing old messages or guessing whether a delay has been forgotten.
Sometimes the clearest update is disappointing: there is still no new information. I would rather send that once, with the next sensible decision point, than send three optimistic messages that create a timeline nobody confirmed.
The standard is simple. At any moment it should be clear what is confirmed, what has been sent for confirmation, and what is simply unknown. Waiting may still be inconvenient. It does not have to be opaque.