A practical workflow for real-estate CRM and agency operations teams

Give each agency territory a more useful local market brief

A suburb name is useful for routing records, but it can be too broad for an agency territory briefing. Teams working the same locality may still need different preparation for different pockets: one area may have a shorter reported median time on market, while another may show a different median listed price.

A CRM can make that variation easier to use. Instead of attaching one suburb-wide label to every task, it can organise a small local briefing around H3 cells, show the exact evidence behind each cell and place the most relevant pockets into a human-reviewed work queue.

For the operations team, the benefit is a clearer handover. The territory brief can sit beside an agent’s existing area assignment, so the next planning session begins with a map, two consistently defined measures and a short list of cells to inspect. The team still supplies campaign knowledge, relationship history and the final decision about any follow-up.

Turn a locality into a reviewable territory queue

The workflow starts by resolving Richmond, VIC 3121 to locality ID VIC2167. A locality-to-H3 concordance then identifies five resolution 8 cells associated with that locality. The working brief pairs reported median days on market with median listed price for the same house cohort in each cell.

Those cells are not five suburb medians, and they should not be treated as smaller official suburbs. Each row is an observation for one H3 resolution 8 cell. The directional labels in the concept—north-west, central-west, north-east, south-west and south-east Richmond—are interface labels that help an operations team navigate the map.

The territory view can support three practical tasks:

• Scan the map: inspect a cell over an attributed geographic basemap, with its boundary and exact H3 identifier available.
• Compare like with like: keep the cohort fixed to houses, the H3 resolution fixed at 8 and the evidence fields consistent across all five cells.
• Prepare the queue: order cells by reported DOM, show median listed price as local context and let a team member review the evidence before creating a task or briefing an agent.

Keep observation, interpretation and action separate

Observation: across the five Richmond-associated H3 resolution 8 cells, the reported median DOM for houses ranged from 24 days in the central-west cell to 30 days in the south-east cell. Reported median listed prices spanned $1,275,000 to $1,575,000. Central-west combined the 24-day DOM figure with a median listed price of $1,575,000; north-east reported 26 days and $1,275,000; south-east reported 30 days and $1,510,000.

Interpretation: a single Richmond label would hide practical variation inside this five-cell view. DOM gives an operations team a consistent way to order the territory queue, while median listed price adds context for the advertised market represented in each cell. Reading them together can help a team prepare more relevant local evidence before an agent or vendor conversation.

These groups are queue rules for preparing work, not ratings of neighbourhood quality or predictions for a listing. Reported median DOM is an area-level days measure, not an estimate of how long a particular home will take to sell. Median listed price is an advertised-market measure in AUD, not a sale price, valuation or pricing recommendation.

Suggested action: let the CRM attach the relevant cell briefing to the next territory review. An operations lead can check the map and exact values, add current campaign knowledge and decide whether the agent needs a local evidence note, a vendor-expectations discussion prompt or no new task. Keep human approval before any outreach.

Make the brief useful inside the CRM

The most useful version is small and repeatable. A territory card can show the selected property type, capture date, H3 resolution, reported DOM and median listed price. A map click or keyboard selection can reveal the same evidence for each cell. The table beneath it gives operations teams a fast audit path and an accessible alternative to the map.

Refresh the fixed dataset when the agency’s data policy calls for a new capture, then rebuild the queue from a consistent set of cells and metrics. Do not blend the five cell medians into a Richmond suburb median or carry the cell result onto an individual property record. If the agency also wants a suburb-level briefing, retrieve and label a separate suburb-level measure.

The published workflow uses five distinct operations across nine requests and returns 21 rows. Five of those requests retrieve the boundary for one cell each. Distinct operation count, request count, returned rows and billing are separate measures. Inspecting the public map, filters or table creates no reader-time HtAG data request because the article uses the reviewed fixed snapshot.

Implementation appendix

The HtAG API documentation covers the five operations used in the published workflow:

1. GET /reference/locality — resolve Richmond, VIC 3121 and retain locality ID VIC2167.
2. GET /reference/concordance/locality-to-h3 — retrieve the five H3 resolution 8 cells associated with the locality.
3. GET /spatial/h3/market/median-dom — retrieve reported median_DOM in days for houses.
4. GET /spatial/h3/market/median-listed-price — retrieve reported median_listed_price in AUD for houses.
5. GET /spatial/h3/cells/{h3_index}/boundary — retrieve the boundary used to render each selected cell over the basemap.