Home Blog AI voice agents for real estate in India: website callbacks and CRM follow-up
Workplate Journal / Voice guide

AI voice agents for real estate in India: website callbacks and CRM follow-up

Design a real-estate callback workflow with a sample call script, a CRM handoff example and a checklist for site-visit enquiries.

For a real-estate team, a useful first AI calling workflow is a website callback requested by the visitor. Use the call to confirm the project, understand what the person is looking for and agree the next step. Give the sales team a short record they can act on. Start with one project and a defined set of questions before adding more.

From website enquiry to site-visit follow-up

  1. Offer a callback on the project page. Explain what the call is for and let the visitor choose from the available callback slots.
  2. Confirm the enquiry. Ask if it’s still a convenient time and which project they want to discuss. Capture only what the next person needs.
  3. Use approved project details. Answer from the current project brief. Route questions on live availability, exact prices or commitments to the sales team if the agent can’t verify them.
  4. Agree one next action. Record a preferred visit time or arrange a human callback. Tell the caller whether the time is confirmed or still needs approval.
  5. Hand over the record. Include the project, what the caller asked, the agreed next step and who should act. Check that repeat enquiries can be matched to the right contact.

What to prepare before adding the callback button

  • A project brief: approved location, configurations, visit hours and the person responsible for keeping the answers current.
  • Two kinds of time slot: the slot when the agent should call and the slot when the visitor can tour the property. A confirmed callback does not reserve a site visit.
  • A handoff destination: the CRM owner or queue, the fields to capture, and a fallback if the integration cannot save the record.
  • A confirmation rule: decide when the agent can confirm a visit from verified availability and when an adviser must check it first.

Worked example: a Saturday visit request

A visitor to a fictional Ahmedabad project requests a callback. They want a two-bedroom flat and ask about a Saturday afternoon visit. The agent records the request, explains that the sales team will confirm availability, and leaves a follow-up for the assigned adviser. The adviser checks the schedule and confirms the slot. The team treats the visit as booked only once it is confirmed.

Project: Example Heights (fictional)
Enquiry: two-bedroom flat; asked about a Saturday visit
What was promised: an adviser will confirm an available time
Visit status: requested, awaiting confirmation
Next action: check Saturday slots and call back
Owner: assigned adviser
Due: Friday afternoon

When the adviser confirms Saturday at 3 p.m., they update the visit status to confirmed, record the time and send the visitor the meeting details. Keep the original request in the call history so another adviser can see what changed. Track requested callbacks, connected calls and confirmed visits separately.

How to handle common callback exceptions

What the agent should say and what the team should record
ExceptionResponse and next action
The preferred slot is unavailableOffer a verified alternative or capture another preference for the adviser to check. Keep the visit pending until a time is confirmed.
The caller already has an enquiryCheck the existing contact and project. Where they match, record the new conversation against that enquiry. If the caller is asking about another project or shares a number, have the adviser verify before merging records.
The caller asks for an unverified priceExplain that the team needs to confirm the current price for the unit. Capture the project and configuration and assign a quote follow-up; do not give a figure from memory.
The CRM record does not saveUse the fallback queue or call record to recover the request. Assign someone to reconcile the record and check that the promised follow-up still happens.

A sample callback script

Hello, I’m the automated calling assistant for [company]. You requested a callback about [project]. Is now a good time? What would you like to know about the project?

I can note your preferred visit time. Our team will check availability and confirm it. Is [day and time] your first preference?

Before going live, test an unavailable slot, a repeat enquiry, a price the agent cannot verify and a caller asking for a person. Check that each test ends with an accurate record and a clear owner.

Keep a project callback separate from a sales campaign

A visitor who asks for a call about one project has given you a specific reason to contact them. Keep the call tied to that enquiry. Before using the same number for another project, a launch announcement or a later campaign, check the separate promotional calling rules and the recipient’s preferences or consent with your telecom provider.

  • Keep the original request. Record the form or other source, date and time, project, phone number and what the visitor asked for. Where commercial communication relies on a customer enquiry, TRAI’s September 2026 summary describes a seven-day window from the enquiry and requires a verifiable written or digital record. It also describes advance declarations for automated outbound calls; confirm the setup with your telecom provider before the pilot.
  • Tell the visitor what happens next. On the form, explain that the business will call about the project and say if it will use an automated assistant. At the start of the call, identify the business and explain any recording or transcription. If you rely on consent, keep a record of the choice and provide a way to withdraw it.
  • Limit the lead record to its purpose. A visit enquiry may need a name, phone number, project and time preference. Avoid collecting identity documents or payment details for an initial callback. Decide who can access recordings and CRM notes, when they are deleted, and who handles privacy requests. Check what applies at launch under the phased DPDP commencement schedule.

Example: A visitor requests a Saturday visit for Example Heights, then asks you to stop calling. Record the request and check that queued calls covered by it are cancelled, the sales adviser sees the update, and the number is suppressed from the applicable calling list. Don’t treat that enquiry as permission to call about a different project.

Have your telecom provider and privacy or legal owner review the form, script and follow-up rules before launch. The customer service guide explains how the checks differ for inbound support, requested callbacks and promotional calls.

For portal, broker or partner leads: verify what the visitor saw and agreed to before the lead was shared. Permission for a portal to contact a visitor does not automatically permit a developer or broker to call them about a launch. Check whether sharing with your business and the specific promotional use are covered, then confirm the applicable telecom checks. See the contact sourcing checklist.

A checklist for your first project

Project and approved information owner:
Where visitors request a callback:
Callback hours and call purpose:
Enquiry fields the agent needs to capture:
Where site-visit availability is checked:
Who can confirm a visit:
CRM destination and owner:
Fallback if the slot or CRM record cannot be verified:
How the team confirms the next step with the visitor:

Set this up with Workplate Voice

Workplate Voice provides a website Call Us widget for scheduled callbacks. Its Workplate CRM integration can add call context and follow-up actions to a lead record. Google Calendar is available for booking workflows. Configure and test the booking rules before letting the agent confirm times.

Start with one call workflow.

Explore how Workplate Voice handles enquiries, scheduled callbacks and follow-ups.

Explore Voice