Listing pages
Price, bedrooms, availability date, tenure, service charge — crawled straight from the site you already publish.
Property enquiries do not respect opening hours, and the agency that replies first usually gets the viewing. CustomerBot answers from your own listings and tenancy terms, then captures the lead while the interest is still live.
A Tuesday evening, after the office closed
Listings alone make a bot that repeats the website. These four together make one that answers the question behind the question.
Price, bedrooms, availability date, tenure, service charge — crawled straight from the site you already publish.
Upload the PDF. Deposit rules, referencing requirements, pet policy and break clauses become answerable.
Schools, transport links, parking zones. The questions that decide whether someone books a viewing at all.
Q&A pairs in your words: budget bands you work in, whether you take DSS, which postcodes you cover.
A form that demands details before answering anything is why so many property enquiries are abandoned. The order matters.
It answers first
Nobody gives their number to a form before they know the flat is still available.
Then it asks
Lead capture fires inside the conversation at the point the visitor is already invested.
The transcript comes with it
The agent opens the lead and reads exactly what was asked — no re-qualifying from scratch.
Export or work the list
Filter by status, bulk-update, export as CSV into whatever CRM you actually use.
Connect a viewing-availability endpoint as an API tool and the assistant reads live slots during the conversation. It can chain several calls in one reply, so “is it available and can I see it Saturday” is answered once.
How API tools are builtDescribed in one sentence
“Return the free viewing slots for a property in the next seven days.”
GET https://api.agency.com/viewings
?property_id={property_id}
&days=7
Authorization: Bearer ••••••••It knows whatever your site says. Re-crawl the listing page after you mark it let and the assistant stops offering it. If your listings come from a feed with a live status field, an API tool is the sharper option — the assistant calls the endpoint and reads availability at the moment it is asked.
It can call a booking or availability endpoint you configure as an API tool, so it can offer real slots and hold one. Describe the endpoint in a sentence and CustomerBot generates the tool definition; you supply the URL, method and any auth header.
It detects the language of the message and replies in it — 95+ languages, from English listing content. That matters in rental markets where a large share of enquiries come from people relocating.
Answers are retrieved from your content and cite the source. If the number is not in the pages or documents you trained it on, it says so and offers to pass the question on rather than inventing a figure.
Handover is built in. When the assistant hits something it should not decide — an offer, a negotiation, anything contractual — it says so and collects the details for a human to pick up, using the handover message you write.
Point it at your listings page and ask it about a property you know well. You will know within a minute whether it is good enough for your site.
Start free