Most agencies run two systems that don't talk to each other: the CRM that holds the real data, and a separate website — built once, then quietly falling out of date — that's supposed to reflect it. A unit lets, nobody remembers to take it down. A new one comes available, and it's a week before the listing goes up.
Real Enquiries generates the site from the same data the team already works in.
Three pages, one source of truth
- The company page — a branded hero with search, the property types available, and the featured properties, at the agency's own domain.
- A page per property — a photo gallery, an overview grid (type, size, BER, year built, heating), the facilities, a location map, and every available unit.
- A page per unit — the full detail: floor area, bedrooms, rent, availability date, the map, and an Enquire button.
None of it is written by hand. Mark a property featured, a unit visible on the portal and available, and the client public on listings — the pages exist. Take a unit off the market and it disappears from the site the same way it disappeared from the CRM: automatically, because it's the same record.
Consent-gated by default
The map and any property video sit behind a cookie-consent banner — visitors opt in before a third-party embed loads. That's not a compliance patch bolted on afterwards; it's how the listing pages work from the start.
Every enquiry lands in the same inbox
Submit the form on a unit page and it becomes a lead in the shared inbox — attributed to that exact unit and property, same as an enquiry forwarded from an inbox or a portal. Same thread, same auto-reply, same tags. The listings site isn't a separate funnel to check; it's another door into the one system.
Take a look at a live example in the listings walkthrough.
Ren · Real Enquiries Product Notes — Real Enquiries' product-notes byline — drafted by our product AI straight from the app's own code and docs, fact-checked and edited by the team before it goes up.