Collect property requirements, share approved project information, and coordinate site visits on WhatsApp. Your sales team receives the conversation and handles advice, negotiation, and follow-up.
In one line
Real-estate WhatsApp automation is most useful for structured intake, approved document delivery, appointment coordination, consent-aware follow-up, and contextual human handoff. Qualification, advice, negotiation, and closing remain with authorised people.
Industry guide reviewed .
Maintained by the Waaru product team. Read our editorial and product-claim review method.
Platform free. AI features are paid separately.
The example keeps property type, area, budget, approved material, visit slot, lead source, and sales owner attached to the same journey. Each stage has a source and a responsible person.
LEAD RE-204
Property enquiry · campaign source retained
Operating boundary
Before publishing, decide which source supplies the lead, which approved content can be sent, which calendar owns the visit, and where a sales person takes responsibility.
Use the business's connected WhatsApp number, purpose-specific consent, approved teammate roles, and the minimum permissions required by a connected CRM, sheet, or calendar.
The workflow can use inbound replies, structured Flow answers, contact fields, conversation history, and records returned by a connected provider within its documented boundary.
Logic Flow can update its own contact and conversation state and read verified availability from supported calendar actions. Booking creation is completed through a separate supported action or by the sales desk, not by the conversational flow.
An inbound message, Flow submission, verified provider event, or human action can move the journey. A portal notification is useful only when its source and fields reach Waaru through a tested interface.
Test duplicate portal leads, missing project matches, stale brochures, unavailable slots, reassignment, opt-out, late replies, and provider downtime before launch.
Do not infer financial capacity, legal eligibility, project suitability, or purchase intent. Do not generate property claims, availability, prices, or approvals that were not reviewed by the business.
Unknown requirements, no-match cases, failed bookings, and negotiation questions stay in the inbox with the captured requirement and original lead source for a human owner.
The problem
Property leads often arrive in bursts from ads, portals, referrals, and offline campaigns. A fast acknowledgement is useful, but a useful sales reply depends on requirement, approved project facts, visit availability, and a clear owner. Manual copying makes all four inconsistent.
Source
Use a source label, campaign parameter, portal identifier, referral note, or CRM record when that value reaches Waaru through a tested interface. Do not claim direct support for every portal. If the source sends a lead to a compatible CRM, sheet, Zapier path, or approved endpoint, map the actual fields and failure behaviour before making it part of the operating workflow.
Qualification
A WhatsApp Flow or guided conversation can ask for property type, preferred area, budget range, purpose, possession timeline, and preferred contact time. These are declared requirements, not a prediction of purchase intent. Use explicit rules to route the thread and let the sales owner review it. The lead-qualification capability guide explains the deterministic boundary.
Property material
Use ordered conditions on the collected requirement to select an approved brochure, floor plan, project location, or rate sheet. Store a content owner and review date for material that changes. RERA places responsibility on promoters for information in advertisements and prospectuses, so the workflow should never improvise registration, pricing, availability, amenity, possession, return, or approval claims.
Appointment
A Logic Flow can read verified availability through a supported Google Calendar or Cal.com action and collect the preferred date and location. It does not create or modify the booking. Complete that write through a separate supported action or the sales desk, then confirm the project address, slot, owner, and change route in the thread. If availability cannot be verified, hand off the request instead of presenting an unconfirmed slot.
Follow-up
A published intake flow is for the active inbound journey. Later follow-up uses approved templates and an eligible audience through the appropriate campaign path. Define purpose, wording, timing, audience, owner, and stop conditions. A reply, opt-out, do-not-contact request, reassignment, or closed outcome should change the next action before another message is admitted.
Operations
Track enquiries with a retained source, complete requirements, no-match cases, time to human acceptance, site visits requested and confirmed, follow-up eligibility, opt-outs, and messages stopped. Closed-deal attribution belongs in the business's CRM or sales system with a defined window. Do not turn a delivered WhatsApp message into a claimed conversion.
A structured workflow can collect declared requirements such as area, property type, budget range, timeline, and preferred contact time. It should route using explicit rules rather than infer financial capacity or purchase intent.
Only through a tested path the portal or business provides, such as a compatible CRM, sheet, Zapier workflow, WhatsApp entry point, or approved endpoint. Confirm the exact source, fields, consent, deduplication, and failure path rather than assuming every portal connects directly.
A configured rule can select approved material from the collected requirement. The business remains responsible for the document, version, project match, regulatory information, and every claim it contains.
Availability can be read from a supported Google Calendar or Cal.com connection. Booking creation and changes happen outside the conversational Logic Flow through a separate supported action or authorised staff. Test calendar ownership, timezone, assignment, failure, and change handling before publishing.
No. It organises repeatable intake, approved document delivery, scheduling, and routing. A person remains responsible for advice, suitability, negotiation, exceptions, and closing.
Start with source retention, complete requirements, time to acceptance, site visits requested and confirmed, opt-outs, and stop conditions. Join closed-deal outcomes in the CRM using the team's own definition and attribution window.
Research notes
This guide describes an operating model, not legal, financial, or property advice. The business remains responsible for every project claim and its regulatory review.
WhatsApp's Business Messaging Policy governs acceptable business use, message purpose, user control, and opt-out handling.
WhatsApp Business Messaging Policy · Accessed 20 August 2026
The Ministry of Housing and Urban Affairs RERA FAQ states that promoters are responsible for the accuracy of information in advertisements and prospectuses.
Ministry of Housing and Urban Affairs, Government of India · Accessed 20 August 2026
Meta documents WhatsApp Flows as structured experiences that open inside WhatsApp.
Meta for Developers · Accessed 20 August 2026
Plan property enquiry questions
Collect viewing preferences without guessing customer intent.
Lead qualification
Use explicit answers and rules before human review.
Zoho CRM integration
Review contact, lead, deal, event, and action boundaries.
Google Calendar integration
Map availability, booking ownership, and recovery.
Human handoff
Carry the source and requirement into the sales inbox.
WhatsApp flow builder
WhatsApp opt-in rules
Map one enquiry source to one accountable sales handoff.
Bring the current lead fields, approved property material, calendar, CRM, consent, and owner rules. Start with the path your team can verify end to end.
