Use property fields, not keyword guesses
Property Intelligence reporting can query normalized property facts such as year built and geography. A request for homes built before a year should use the numeric field, not a search for that year in a note or label.
The result can include filtered counts, a bounded set of rows, unknown-year coverage and a full report link. An opportunity amount is a modeled estimate, not a paid invoice or collected revenue. Keep that qualification visible in any summary or exported report.
Choose the source deployment
- Open the relevant Property Intelligence deployment or ask Work to show the permitted choices.
- Select explicitly when several deployments are available.
- Confirm that the source is enabled and connected. A paused source cannot prove the workspace has no properties.
- State the geography and numeric range you actually need.
A useful report request
Using the selected Property Intelligence deployment, show properties in our authorized portfolio built before 1960 in the city I specify. Include the matched count, how many properties have an unknown build year, a bounded preview and the full report link. Do not create outreach or treat modeled opportunities as revenue.
“Before 1960” excludes 1960 itself. An unknown build year is not classified as an older home. Ask for the actual filter interpretation if the wording could mean an inclusive range.
This is a query of the permitted portfolio, not a search of every property in a city. The assistant should preserve both the portfolio and matched-report counts rather than imply complete market coverage.
Inspect the rows and the exclusions
Open the report link to review the complete available result. Check normalized addresses, service history and missing fields before making an operational decision. The visible rows in chat may be only a preview; do not calculate a population total from them.
A useful analysis identifies which opportunities depend on known property facts and which would require additional verification. Do not infer equipment condition, customer interest, replacement urgency or permission to market solely from the building’s age.
From report to next step
Ask for an internal review checklist or a clearly labeled PDF summary. If you prepare an outreach candidate list, review its accuracy and permission basis separately. Reporting does not send a message, create a booking or change customer records.
If the source disconnects or its settings change during the read, refresh the report after resolving access. Preserve the generation time and assumptions when comparing reports across periods so configuration changes do not look like genuine changes in demand.