Turn a messy vendor address into a listing-ready property record

A listing starts taking shape well before the photographer arrives. An agent may receive an address in a text message, type it into the CRM and then re-enter property details from another source. A small variation such as “10 mary st richmond vic 3121” can create a second record, while useful fields remain blank.

A better intake step turns that text into a matched property record for a person to review. The example below uses illustrative intake text, not a real vendor submission. It shows how a real estate CRM could present the result without overwriting anything the vendor has already confirmed.

View the demo screenshot

Illustrative listing-intake concept using a fixed HtAG snapshot captured 14 September 2026. The property source was refreshed 29 August 2026.

Match the property before filling the record

The first step sends the entered text to the address geocode endpoint. The inspected match for this example is 10 Mary Street, Richmond VIC 3121. Before proceeding, the agent can inspect the returned number, street, locality, state and postcode against the vendor’s information.

Once the match is accepted, the CRM keeps the returned address key, 10MARYSTREETRICHMONDVIC3121. That returned key connects the approved address to the next request and can also help the CRM recognise another entry for the same property.

This is an identity check, not a reason to replace recent information. The accepted match should sit alongside the original intake text and any vendor-confirmed address details so the agent can resolve a difference deliberately.

Put six physical fields in one review

Using the accepted address key, the property summary returns six physical attributes needed for this example:

• Property type: house
• Bedrooms: 3
• Bathrooms: 2
• Car spaces: 1
• Land area: 176.22 m²
• Internal floor area: 153 m²

All six fields are sourced and ready for human review. Keep the source refresh date of 29 August 2026 alongside them, preserve the vendor’s confirmations, and let the agent decide which values belong in the listing record.

The demo is a fixed-data walkthrough: match the address, review the source facts, then prepare the handoff. Switch tabs to explore the review steps. The six sourced fields and refresh date remain available as context; your CRM would manage the actual confirmation and saving.

Build a controlled CRM handoff

A customer product can implement this pattern as a review queue: geocode the entered address, let the agent inspect and accept the match, cache the accepted address key, then request the property summary. The CRM can compare the returned fields with its current record and present only the decisions that need attention.

That sequence keeps the vendor’s statements and the property record’s refresh date visible throughout the agent’s review. It also keeps the workload bounded: one address match followed by one property-summary request after acceptance. Changing tabs in a fixed demo or reopening a cached review should not create another HtAG data request.

Implementation appendix

1. GET /address/geocode — submit the free-text address and inspect the selected record’s number, street, locality, state and postcode before retaining its address key.
2. GET /property/summary — use the accepted address key to retrieve the physical property attributes for review.

See HtAG API access and current pricing to add reviewable property data to your listing-intake workflow.