LanguageENES

AI chatbot for real estate websites

Answers about the listing, at midnight

Property questions arrive outside office hours, from people comparing four listings at once. An assistant that reads your listings and your area guides answers them, and asks for a name when someone wants a viewing.

The situation before

A buyer on your site has three questions about one property: the service charge, the parking, and whether the school catchment is the one they think. Your form asks for their phone number before answering any of them.

What to feed it
  • Listing descriptions and specifications
  • Neighbourhood and transport guides
  • Fees, taxes and buying process explainers
  • The questions your agents answer every week

What it does

Knows which property

The widget reads the page it is on, so a question about square metres is about the listing in front of the visitor.

The area, not just the flat

Neighbourhood guides, transport notes and fee explanations answer the questions that actually decide a viewing.

A viewing request is a lead

When someone asks to see it, the conversation becomes a lead in HubSpot with the property and the transcript on it.

Questions people ask

Does it know when a property is sold?

It knows what the knowledge base holds. Sync the listings and a removed property stops being answered about.

Can it book a viewing?

It captures the request as a lead with the details and the transcript. The booking itself stays in your calendar and your process.

Does it work in two languages?

Yes, from the same listings, answering in the language of the question.

Connect it to