NovA follow-up should be tied to the buyer’s event, not a generic timer
Why property follow-ups work better when they are connected to a buyer’s stated event or a meaningful change, instead of an arbitrary marketing timer.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
A marketing system can be perfectly punctual and still be badly timed. A buyer leaves their details, the clock starts, and the automation sends a message two days later, another on day five, and perhaps one more the following week. Nothing has to change in the buyer’s situation for any of those messages to exist. The sequence is driven by elapsed time because elapsed time is easy for software to measure.
Property decisions rarely move that neatly. Someone may be waiting to confirm a relocation date, sell another home, discuss a purchase with family, receive an updated offer for a specific unit, or simply reach a date they chose for returning to the search. In those cases, the question is not how long the lead has been inactive. It is what event would make the conversation relevant again.
A meaningful trigger can be small, but it needs a reason
Consider a hypothetical buyer who says, “I should know my moving date next month; contact me after that.” A three-day nurture message adds nothing to that instruction. The buyer has already supplied a better trigger than the marketing calendar. The system can either respect it or behave as though the conversation never happened.
The same applies when the trigger sits on the property side. A buyer may ask to hear if the price of one identified unit changes, if a handover date is confirmed, or if a missing document becomes available. A message sent after one of those events has a clear answer to “why now?” It carries new information connected to a question the buyer already considered material.
That does not mean every database change deserves a notification. Editing a photograph caption is not equivalent to changing the price. Reformatting a page is not equivalent to confirming the availability of the unit. An event-based system still needs judgment about which events matter to the decision.
The follow-up should carry the context that caused it
“Just checking whether you are still interested in Thailand property” is a surprisingly weak message when the original conversation was about one apartment and one unresolved condition. It forces the buyer to rebuild the history before anything useful can happen.
A better follow-up can be brief and specific: what the earlier question was, what changed or which agreed date has arrived, and whether the buyer needs to do anything. The purpose is not to reproduce every note in a CRM. It is to make the next message feel like a continuation of the same decision.
The same context matters on the company side. If an automated trigger creates a task for a manager but the task contains only a name and phone number, the automation has preserved timing while discarding meaning. The manager then opens with generic discovery questions, even though the system already knew why the contact reappeared. A useful handoff should preserve the unresolved question or the event that reopened it.
I would be particularly cautious with language that tries to compensate for the absence of an event: “Don’t miss out,” “Still thinking?”, or “This may be your last chance.” Those phrases can create movement without any underlying change. If a genuine deadline or availability constraint exists, it can be stated plainly and attributed to the relevant offer. If nothing has changed, urgency should not be manufactured simply because a timer fired.
A good automation also knows when to cancel itself
Marketing teams often evaluate automation by visible activity: messages sent, sessions recovered, replies generated. Trust also depends on the actions the system chooses not to take.
If the buyer has already rejected a scenario, an old reminder should not keep resurfacing it. If the unit is no longer available, the previous “come back and look” sequence should stop. If the buyer asked not to be contacted until a particular date, that preference should override the default cadence. A system that can stop is not doing less useful work; it is avoiding work that no longer belongs to the buyer’s decision.
There is another important distinction between types of permission. Someone may want alerts about a saved property without wanting general promotional messages. Agreement to one useful update should not silently become permission for every campaign the company can send. The more precisely the system understands the requested trigger, the easier it is to keep that boundary.
A follow-up earns its place when it reconnects the buyer with an unfinished decision at a moment that makes sense. A generic timer can be a fallback for some service workflows, but it should never become a substitute for the event the buyer actually described. Once the trigger is meaningful and the original context survives, automation feels less like pursuit and more like memory.