How to handle property enquiries on WhatsApp

An effective property enquiry reply answers the question, identifies the listing and offers one useful next step. It should not force someone through a long questionnaire before giving them the information they requested. For an agent managing several listings, the challenge is keeping those answers accurate as prices, availability and viewing arrangements change. A shared property collection helps, but the quality of the conversation still depends on the rules behind it.

This guide explains a practical enquiry workflow for a small property team. LeadProps brings imported property information and a WhatsApp assistant into one workspace. The workflow below also applies when an agent is replying manually. Examples are illustrative, not live offers. Confirm property details with the responsible agent before making commitments, and treat a requested viewing as provisional until someone has confirmed access.

Start with the property, not the sales script

A useful first reply establishes what the person is asking about. If they send a listing link or reference, use it. If they say only “the apartment,” ask for the link, location or screenshot that will identify it. Guessing from the most recently advertised property can lead to a confident answer about the wrong home. Keep the source reference attached to the conversation so a colleague can recover the context later.

Once the listing is identified, answer the original question in plain language. Someone asking about bedrooms does not need a paragraph about the agency. Someone asking about rent needs the currency and rental period, not an unqualified number. When information is missing, say which detail needs checking and who will check it. A short, honest uncertainty is more useful than a polished answer that conceals an unknown.

A practical opening might read: “Thanks for asking about reference M204. It is listed as a two-bedroom apartment. I’m checking whether it is still available. Are you looking to move this month or later?” This acknowledges the enquiry, distinguishes a recorded fact from a pending check and asks a relevant follow-up.

Build a dependable reply sequence

Use a sequence that adapts to the enquiry rather than sending every question at once. First identify the property. Then answer the direct question. Next ask for the one missing detail that would improve the recommendation. Finally offer either a viewing request, a shortlist or a human follow-up. A conversation can stop at any point if the person already has what they need.

For a broad search, the most useful starting fields are usually transaction type, location, approximate budget, bedroom requirement and timing. Ask them in context. If the person already mentioned a two-bedroom rental, do not ask again whether they want to buy. Repeated questions make automation feel inattentive and can cause people to abandon an otherwise useful exchange.

Keep a short internal summary as the conversation develops. Record confirmed preferences separately from assumptions. “Interested in Marina” is a confirmed preference if the person said it. “Likely needs parking” is an assumption until asked. That distinction matters when the assistant searches for alternatives or another agent takes over. It also makes it easier to correct a misunderstanding without rewriting the entire conversation history.

Make price and availability explicit

A price reply needs three parts: the amount, the currency and the basis. An annual rental figure is not a monthly payment, and a sale price should not be mixed into a rental shortlist. Where a listing gives an asking price, describe it as an asking price. Do not imply that fees, furniture, utilities or other costs are included unless the record explicitly says so and the responsible person has verified it.

Availability is a separate field from the date a listing was imported. A fresh import does not prove that an owner still wants viewings. Agree how your team checks active stock and what the assistant should say when the status is uncertain. One sensible default is to share the recorded details while making clear that availability will be confirmed before arranging a visit.

When an agent corrects a price, update the property source used for future replies. Correcting a single chat leaves the next enquirer exposed to the old information. If several sources disagree, pause recommendations for that listing until the conflict is resolved. Keep a note of which source was checked and when, especially for properties that attract frequent enquiries.

Use photos to answer a specific question

Send a small, relevant selection of actual listing photos. If someone asks about the kitchen, start with the kitchen. If they ask whether the apartment has outdoor space, show the appropriate photo only when it genuinely belongs to the listing. Reusing an attractive image from another property creates confusion even if the layouts appear similar.

Avoid sending a large gallery before the person has shown interest. A few well-chosen images are easier to understand on a phone and reduce the chance that the useful information disappears in a stream of attachments. Explain what the images show with a short factual caption. Distinguish an actual property photo from a floor plan, illustrative render or community image.

Check that the links and images still load on a separate device. A photo visible in an agent’s logged-in browser may not be accessible to the recipient. Do not share owner documents, identity information or private access instructions as part of the initial enquiry. Public marketing images and internal operational documents should have separate handling rules.

Know when to hand over to an agent

Automation is useful for recorded facts and routine steps. It should hand over when the person asks for negotiation, an exception, sensitive information, a complaint or a commitment the system cannot verify. A clear handover is better than repeatedly rephrasing an answer. Tell the person that an agent needs to check the question and preserve the context so they do not have to start again.

Define ownership of the handover. “Someone will reply” is weaker operationally than assigning it to the agent responsible for the property. The team needs a way to distinguish a conversation awaiting the customer from one awaiting an internal answer. Otherwise both can look inactive even though only one requires action from the business.

A handover summary can contain the property reference, the customer’s question, facts already shared, their preferred contact time and the exact issue needing review. Keep it concise and avoid unnecessary personal details. If the customer asks to speak to a person, honour that preference rather than using additional automated questions to delay the transition.

Turn interest into a clear next step

Offer a next step that matches the level of interest. Someone comparing areas may benefit from two alternatives. Someone who has selected a property may want a viewing. Someone still deciding on timing may prefer to return later. Do not turn every enquiry into an immediate appointment request.

For viewings, ask for a date range or two possible times, then check agent availability and access. Repeat the date, local time and property reference in the confirmation. A message saying “tomorrow afternoon” becomes ambiguous when read later or by a colleague. If the person is in another time zone, state the property’s local time explicitly.

After a visit, ask one specific feedback question, such as whether the layout met their needs. Use that answer to improve the next recommendation. Avoid sending the same shortlist again without acknowledging the feedback. Record the outcome so that a colleague does not follow up as though the viewing never happened.

Check the workflow before enabling automatic replies

Test with a small, reviewed collection before connecting a larger inventory. Use sample conversations that include missing prices, unavailable properties, vague references and requests for a human. A successful test is not merely a fluent response; it is a response that stays within the information the team can support.

• Ask about a known listing and confirm that the reference matches.
• Ask about a missing feature and check that the assistant does not invent it.
• Ask for a price and confirm that currency and rental period are included.
• Request a viewing outside normal availability and check the handover.
• Ask to stop the conversation and confirm that the preference is respected.
• Correct a listing and repeat the question to check the new answer.
• Disconnect or interrupt the connection and check how the team notices.

Review a handful of real conversations regularly after launch. Look for repeated unanswered questions, confusing terms and unnecessary follow-ups. Improve the source records and response rules together. Changing tone alone will not fix an inaccurate property database.

Frequently asked questions

What should the first WhatsApp reply include?

Include an acknowledgement, the relevant property reference if known, an answer to the immediate question and one useful next step. If the property cannot be identified, ask for a link or reference before giving detailed information. Keep the message short enough to read comfortably on a phone.

Can a property assistant confirm availability automatically?

It can repeat the availability recorded in its source, but that source may be stale. Decide which checks your team requires before promising a viewing. If there is no reliable current confirmation, the assistant should state that an agent will verify availability rather than presenting an assumption as a fact.

Should every enquiry receive a full property brochure?

No. Start with the information that answers the question. A focused photo or short summary is often more useful than a large attachment. Offer additional material when the person wants it, and check that the brochure reflects the latest price and status before sharing it.

How does LeadProps fit into this process?

LeadProps provides a property workspace, listing imports and WhatsApp assistant features. Prepare accurate records first, configure the connection and test replies against your actual inventory. The operational checks in this guide remain the team’s responsibility; software does not independently verify owner approval, access or every property claim.

What should a team measure?

Measure whether enquiries receive useful answers, how long human handovers wait, how often details need correction and whether viewing requests reach a confirmed outcome. Raw message volume can be misleading. A shorter conversation that resolves the question is often better than a long exchange with no clear next step.