Source-bounded implementation brief

Property-source check for a Landlord lead

For a landlord lead, property-source check should preserve the person’s stated context, create an auditable record and stop before unsupported automation. It does not prove that a production CRM, calendar, messaging or property-data connection is active.

Direct answer

Capture property type, unit count, location, service need, occupancy and decision timeline only as relevant to this stage. Store listing identifier, approved source, retrieval time, status, fields used and freshness rule. Use that evidence to decide whether a property statement can be shown or must be withheld, then hand off to the property-management or leasing team when the stop conditions require it.

Required workflow record

Lead context

property type, unit count, location, service need, occupancy and decision timeline.

Stage record

listing identifier, approved source, retrieval time, status, fields used and freshness rule.

Four-step implementation

  1. Collect only the stated property type, unit count, location, service need, occupancy and decision timeline.
  2. Create the stage record: listing identifier, approved source, retrieval time, status, fields used and freshness rule.
  3. Use the record to decide whether a property statement can be shown or must be withheld.
  4. Stop when missing source, stale record, conflicting fields or licensing restriction; pass context to the property-management or leasing team when required.

Stop and escalate

Stop automation for missing source, stale record, conflicting fields or licensing restriction. Do not use this flow for legal conclusions, guaranteed occupancy or unsupported savings.

Evidence boundary

A property-data connection requires authorization, licensing and freshness controls. The public demo does not prove a live MLS connection. This guide describes a workflow specification, not a deployed integration, legal conclusion, fair-housing approval, response-time promise, conversion forecast or transaction result.

Scope a reviewed workflow

Use this brief to document sources, records, stop conditions and ownership before implementation.

Discuss a custom PropBot Studio workflow