Build controlled sales and lettings automations around supported property signals in the postcodes available to your branch. Choose whether eligible matches enter a review queue or proceed automatically after branch safeguards are applied.
Choose the opportunity and scope once. As daily property updates are processed, ProspectOS evaluates eligible matches and applies the configured controls before activity continues. Explore the Map and property intelligence.
Choose the target pipeline, branch postcodes, supported property signals and available targeting criteria.
ProspectOS compares daily property updates with the rules and filters configured for the automation.
Eligible matches remain subject to postcode access, own listing protection, blocked addresses, duplicate rules, wallet balance, limits and valid templates.
Choose whether eligible matches enter the Review Queue or proceed automatically after the configured checks are satisfied.
Choose the automation structure that fits the opportunity, from one controlled action to a longer sequence with review and exit controls.
Prepare one campaign when a property newly meets the selected supported signal and targeting rules.
Build a sequence using send, wait, condition and end steps, with configured exits when the property status or eligibility changes.
Use a qualifying sold event to prepare a campaign for a supported surrounding audience, subject to the selected radius and recipient limits.
Use supported propensity bands, confidence levels and reason tags to prioritise selected off market properties. Treat these as signals for review, not certainty about vendor intent.
Set an automation to Automatic or Review Required. Both modes remain subject to branch scope, territory, safety, wallet, template and limit controls.
Eligible matches can proceed after branch and postcode scope, own listing protection, blocked address, duplicate, wallet, limit and template checks are applied.
Eligible matches enter the Review Queue and require an authorised user to approve or reject them before the send proceeds.
Automation should make prospecting more consistent while keeping the branch controls visible and practical.
Set an activity limit for each automation and monitor recorded usage against it.
Hold eligible matches for authorised approval before the send proceeds.
Pause or resume an automation without rebuilding its configured rule.
Keep each automation within the active branch and the postcodes available to that branch.
Open reporting for an automation and review recorded sends, costs and outcomes where available.
Review automation reportingRecorded sends can retain their automation, property, branch, template and cost context. When engagement or an enquiry is captured, the team can manage the opportunity and review the recorded activity across ProspectOS.
A property meets the configured rule and passes the required controls before the selected letter or postcard proceeds.
The campaign uses the approved design and written template selected for that automation.
Supported QR engagement, form responses, calls or replies can be recorded with the available campaign and property context.
When an enquiry or prospect record exists, the team can assign ownership, record activity and manage the next action, valuation and outcome.
Compare recorded automation, campaign, postcode and outcome information to understand which activity deserves further attention.
Bring one branch, one priority postcode and one instruction growth objective. We will show how supported property signals can move through review or automatic workflows while branch controls remain visible.
Follow the journey from property signal to recorded prospecting activity.