Source-bounded implementation brief

Consent capture for a Landlord lead

For a landlord lead, consent capture 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 channel, disclosure text, affirmative action, timestamp and source page. Use that evidence to decide whether the requested communication is permitted, 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

channel, disclosure text, affirmative action, timestamp and source page.

Four-step implementation

  1. Collect only the stated property type, unit count, location, service need, occupancy and decision timeline.
  2. Create the stage record: channel, disclosure text, affirmative action, timestamp and source page.
  3. Use the record to decide whether the requested communication is permitted.
  4. Stop when no affirmative permission, withdrawal, STOP request or unsupported channel; pass context to the property-management or leasing team when required.

Stop and escalate

Stop automation for no affirmative permission, withdrawal, STOP request or unsupported channel. Do not use this flow for legal conclusions, guaranteed occupancy or unsupported savings.

Evidence boundary

Consent requirements vary by channel and jurisdiction; configured text and retention need qualified review. 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