Source-bounded implementation brief

Consent capture for a Open-house lead

For a open-house 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 event, property source, attendance intent, contact permission and requested next step 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 listing team responsible for the event when the stop conditions require it.

Required workflow record

Lead context

event, property source, attendance intent, contact permission and requested next step.

Stage record

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

Four-step implementation

  1. Collect only the stated event, property source, attendance intent, contact permission and requested next step.
  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 listing team responsible for the event when required.

Stop and escalate

Stop automation for no affirmative permission, withdrawal, STOP request or unsupported channel. Do not use this flow for surprise messaging, implied representation or inaccurate event details.

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