WhatsApp AI Receptionist for builders

What is included in the setup

• Knowledge card built from a 20-minute call
• WhatsApp Business API connection on your number
• Appointment booking into Calendar/Sheet
• Human handover with owner alert
• Daily 7 PM summary

What you need before the call

• Your WhatsApp Business number (or we provision one)
• Meta Business Manager access for verification
• Services, prices, timings, address, staff names
• Where bookings should land: Google Calendar or a Sheet

A normal day at a builder & developer with this setup

1. 8:30 AM: front desk opens WhatsApp Business on the shared number. Overnight enquiries from Facebook and site hoardings are already sitting there with the bot's first reply sent — project name, unit sizes, and starting price range for the flats or plots being asked about.
2. 10:00 AM onward: a site visit request comes in. The bot checks the site executive's calendar slots for the day and books a walk-in time, drops it into the shared Sheet with client name, number, and preferred project phase.
3. Around lunch, a buyer asks for the price list PDF for a specific tower and floor. The bot sends the current rate card on file — same one the sales team uses, so nobody quotes an old rate from three months back.
4. Afternoon: a query comes in about loan approval status or payment schedule that the bot can't answer confidently. It hands over to the counsellor's number and sends an owner alert on WhatsApp so the call isn't missed during a site visit.
5. 3:30 PM: a lead asks about registration, khata transfer, or RERA number for the project. Bot shares the RERA registration ID on file and points to the sales office for documentation questions, without giving any legal opinion.
6. 6:00 PM: site executive back from the day's visits logs which walk-ins converted, which need a follow-up call, directly against the bot-booked entries in the Sheet.
7. 7:00 PM: owner gets the daily summary — enquiries received, site visits booked, visits done, and unanswered questions that need a callback tomorrow morning.

Rules and platform limits it works within

WhatsApp Business policy: only pre-approved message templates can be sent outside a 24-hour reply window, so the setup uses approved templates for visit confirmations and reminders, and keeps free-form replies inside the live chat window.

DPDP Act 2023: buyer phone numbers, budget details, and visit history are personal data. The setup stores this only in your connected Calendar/Sheet, doesn't share it with third parties, and you control who has access.

RERA: the bot shares the project's registered RERA number and rate card exactly as given by you. It does not make price promises, possession date claims, or discounts on its own — those come from the sales team only.

What the leak costs: a worked illustration

Illustration only. Assume a mid-size builder gets 6 missed enquiries a day during peak hours (site visits, weekend crowd) because front desk is on a call or on-site. Assume 1 in 5 missed enquiries would have converted to a site visit, and 1 in 4 site visits converts to a booking. That's roughly 1-2 lost site visits a week from missed replies alone, before even one lost sale is counted.

Setup fee is Rs 15,000 one-time, care plan Rs 2,500 a month — about Rs 83 a day. If the bot recovers even one extra site visit a month that would otherwise have gone cold waiting for a reply, the monthly cost is already covered many times over on a single unit's margin.

Questions builder & developer owners ask

Our price list changes every few weeks when we release a new phase or tower. How does the bot stay updated?

You send the updated rate card to us or update it in the connected Sheet, and the bot picks it up from there. There's no separate retraining call needed for a price change — it's part of the care plan.

Can the bot handle price negotiation or discount questions from buyers?

No, and it shouldn't. It shares the standard rate card and hands over any negotiation, discount, or payment plan discussion to your counsellor with an owner alert, so pricing decisions stay with your sales team.

We get enquiries in Hindi, Marathi, and English mixed together. Will the bot manage that?

Yes, the knowledge card built from the 20-minute call is set up to handle mixed-language enquiries the way your front desk actually gets them, and it hands over to a human whenever it isn't confident of the reply.