AI Chatbot for Real Estate: Listings, Visits, Paperwork

A property website gets the same questions every day, whether it belongs to a broker in Pune with sixty resale listings or a developer in Bengaluru selling two towers. How big is the 2 BHK? Is there a clubhouse? How far is the metro? When is possession? What do I need for the loan? Can I visit on Sunday? Most of those answers are already on the website, on a project page, a floor plan or a FAQ. A chatbot that answers from those pages saves the sales team the same twenty calls a day.

Property is also where a chatbot can do real damage, because the expensive questions sound just like the easy ones. "Is it available?" and "Will possession be on time?" are one sentence each, and a confident wrong answer to either costs a deal, or worse. This post covers what a property website's chatbot should answer, what it must leave to your team, and how to keep it right as units sell. The examples use TailGPT, and plan figures are as of 4 October 2026.

What can a property website's chatbot answer?

It can answer anything your listing and project pages state in words. TailGPT answers only from the pages you tick and the documents you upload, so the useful list is really a list of what your pages already say:

• Configuration. Which types a project has (1, 2 and 3 BHK, villas, plots, office units) and how many floors or towers.
• Area, as the page states it. Carpet area if you publish it. Write which measure you mean: a visitor who asks for carpet area should not get a figure that was something else on your page.
• Amenities. Clubhouse, pool, parking, power backup, security, a children's play area, whatever the amenities page lists.
• Location. The address, the landmark, and distances to the station, school or highway, if the page gives them.
• Possession timeline, as stated. "Possession from December 2027, as stated on the project page" is fine. Anything firmer than your page is not.
• Documents needed. What a buyer brings for a booking or a home loan, or what a tenant needs for a rental agreement, if you have a page for it.
• Visit timings. When the site office or sample flat is open, and who to call before coming.
• Payment plans and prices, only if published. If your price list is on the website or in an uploaded brochure, the bot can quote it. If it is not, the bot cannot.

What must it never promise?

It must never promise a price, an availability or an approval that your page does not state. The three questions to worry about are:

• "Is flat 1203 still available?" Your website does not know what was sold this morning, so the bot does not either.
• "Can you do it for less?" Negotiation belongs to a person with authority to agree.
• "Is the project approved? Will the bank fund it? Will possession be on time?" The bot can repeat what your page says about approvals and possession. It must not add to it.

TailGPT's design helps here. It answers only from your selected pages and documents, with no general knowledge, and when they do not cover a question it says plainly that the website does not cover it instead of guessing. So it will not invent a discount or a date. The bot phrases that answer itself; there is no fixed sentence. Such a question still uses one of your month's questions, because the bot looked and found nothing.

Help the bot say no well by writing the "no" onto your pages. A line on each project page such as "Availability changes daily. Call the sales office on the number below to confirm a unit" gives the bot something true to say, and the phone number to say with it.

One page with an old price is worse than no price at all. If a figure on your website is out of date, the bot will quote it as confidently as a current one.

Can it book a site visit?

No. TailGPT cannot book, schedule or confirm a site visit, and it does not collect a visitor's name or number. It answers questions; your team takes the booking. What it can do is name the next step. With the Sales role, it leads with configurations and prices from your pages and then points to where a visitor acts.

Answers are plain text, without clickable links, so the bot names the page in words, such as "the Book a Site Visit page", and gives a phone or WhatsApp number only if one is written on a page it has read. Two things follow:

• Give the visit page a clear, findable name, and put it in the menu.
• Write the sales number and visit timings, in text, on a page the bot reads. A number inside an image is invisible to it.

If you need the chat itself to capture a buyer's details, TailGPT is the wrong tool for that part. Why answers come before forms covers what an answer-first bot does for leads and when to choose something else.

Which pages should a property website's chatbot read?

The pages that state facts a buyer or tenant asks about, and none that state old facts. TailGPT lists your site's pages when you add it, and you tick the ones to read.

A TailGPT "page" is one address on your site, whatever its length, and the allowance is shared across your websites. As of 4 October 2026, Starter (₹4,000 a month) reads up to 1,000 pages and Growth (₹8,000 a month) up to 7,500. A broker with thousands of resale listings will need to choose. Uploaded documents do not count against pages, so a developer's brochures, price lists and specification sheets can go in as PDF or Word files. The full table is on the pricing page, and how to choose which pages your chatbot should read goes further on picking.

How do you keep listings current when units sell?

Update the website, then have TailGPT read it again. There is no automatic refresh: the bot answers from what it last read until you ask it to read again, and that comes from a monthly allowance shared across the account. As of 4 October 2026, Starter includes 2 re-reads a month and Growth 8.

• When units sell, mark them sold on the page, or untick a sold-out listing in the picker. An unticked page keeps answering until the next read, so batch the week's changes and read once.
• When prices change, keep the price list as an uploaded document. Uploading the corrected file with the same name replaces the old one and does not use a re-read.
• When a new project launches, check that its page is in the picker and ticked before you rely on it. A page published after you added the website may not be listed there. Uploading the new project's brochure is a quick way to give the bot its facts in the meantime.

How to keep your chatbot's answers up to date sets out a simple monthly routine.

Where does a project registration number fit?

If your project page shows its registration number, the bot can repeat it when asked, and that is all it should do with it. In India, the Ministry of Housing and Urban Affairs lists among the key features of RERA that developers must mention the RERA registration number in each advertisement or prospectus, that agents dealing in real estate projects must register with their state's Real Estate Regulatory Authority, and that information on registered projects is available through each state authority's online portal. The ministry also keeps a list of the state and union territory authorities.

Three habits keep the chatbot on the right side of that:

• Show the registration number, in text, on every project page the bot reads, so its answer comes from the same place your advertising does.
• Do not let the bot be the only place a number appears. It quotes your page; it cannot check the number against the state portal.
• Check with your state's RERA authority or your own lawyer before you decide what a chatbot on your website may say about a project. This post is not legal advice.

Outside India, the same logic holds: whatever your local regulator requires on listings, put it on the page, and the bot repeats the page.

How should a broker and a developer set it up differently?

A broker has many short listings that change often; a developer has a few deep project pages that change at milestones.

• A broker should tick the listings that are live, keep sold ones unticked, and lean on the Support or FAQ role for short, factual answers. Re-reads go furthest on a fixed day each week.
• A developer with one site per project can add each as its own website. Growth allows three websites live at once. Several chatbots can also share one website's content, each with its own role and look, such as Sales on project pages and Support on the customer care pages for existing buyers.

Buyers who prefer Hindi can ask in Hindi and get an answer from your English pages. That is in beta, so test it with your own questions before relying on it.

How do you test it before it goes live?

Ask it the questions that would hurt if answered wrongly. The free trial needs no card and gives one website, up to 500 pages read and 20 test questions, which is enough for this:

1. "What is the carpet area of the 2 BHK?" It should match your page exactly.
2. "Is flat 1203 available?" It should say the website does not cover that, and name your sales number or visit page.
3. "Can I get a discount if I book this week?" Same.
4. "Will possession definitely be in December?" It should repeat only what the page says.
5. "Book me a site visit on Saturday." It should name the visit page, not pretend to book.
6. "What is the RERA number for this project?" It should give the number on your page, or say the page does not show one.

If any answer goes beyond your pages, look for the page it came from and fix that page first. Once the bot is live, the list of "Questions your chatbot could not answer" on your dashboard shows, with a count for each, what buyers asked that your listings do not say.