Answering the comments under a real estate launch post
Dozens of people commented «details» under one launch post and none of them got a fact. What a developer should answer in public, what to move to WhatsApp, and how an AI agent turns a comment into a booked viewing.
The short answer. Answer every comment in public with one line that proves a person read it, then move the conversation to WhatsApp, where an agent can ask which unit and which day and book the viewing. Helm runs that workflow for real estate developers. It qualifies the lead one question at a time and hands the sales team a lead with fields filled in, not a screenshot.
What actually happens under a launch post
We counted one national developer's launch post. Dozens of people wrote one word: «details». Most got the same reply, «we've contacted you». None of the replies on the post carried a single fact: no price, no area, no delivery date, no next step.
That isn't a staffing failure. A launch post collects a day's demand in an hour, and a social team can only paste the same line. The buyers who wrote «details» were ready to say which unit they wanted. Nobody asked.
What to say in public
The public reply has one job: show the commenter, and everyone reading after them, that the question was seen and the answer is one tap away. Keep it short and specific to the post:
The two-bedroom units in phase two start at the published price. We've sent you the payment plans on WhatsApp — reply there with the size you want.
Don't put a price in public that isn't on the published list. Never post a payment plan in the comments.
What to move to WhatsApp, and why
Meta allows one private reply per comment, and the buyer has to answer before the conversation can continue. Our post on comment automation rules covers the limits. Inside WhatsApp, the agent can do what a comment thread can't:
- Qualify one question at a time. Unit type, budget band, cash or instalments, which day suits a viewing.
- Hold the viewing. A real slot on the sales team's calendar, with a location pin and a reminder the day before.
- Hand over properly. The agent creates a lead with the answers attached, routes it to a named agent, and passes on the full transcript.
What it never does here
The developer signs these before the build:
- It never quotes a price outside the published list.
- It never promises a unit it can't see in the inventory.
- It never negotiates a payment plan in chat. The buyer goes to a named agent with the transcript.
The rest of the launch
The same number runs the launch event: the invitation, the plus-one question, the QR ticket, the check-in at the door. For a broker network it can also send the daily inventory update and the payment-plan pack, in the broker's language.
The number to judge it by
Viewings held from launch leads, plus RSVPs checked in at the door. Publish the baseline before the build. For most developers, today's figure for comment-to-viewing is unknown, and finding that out is useful on its own.
What to send to start
The launch calendar: the next phase, the registered list, the payment plans. A first workflow is typically live within five working days of receiving them. The real estate developers page shows the desk qualifying a buyer from the first message to the booked viewing.
Helm builds the workflow that does this work in production, in your channels and your systems.
Start a workflow ↗All posts ↗