Source-bounded implementation brief
Consent capture for a Seller lead
For a seller 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 address, ownership role, motivation, timeline and requested valuation help 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 or valuation team when the stop conditions require it.
Required workflow record
Lead context
property address, ownership role, motivation, timeline and requested valuation help.
Stage record
channel, disclosure text, affirmative action, timestamp and source page.
Four-step implementation
- Collect only the stated property address, ownership role, motivation, timeline and requested valuation help.
- Create the stage record: channel, disclosure text, affirmative action, timestamp and source page.
- Use the record to decide whether the requested communication is permitted.
- Stop when no affirmative permission, withdrawal, STOP request or unsupported channel; pass context to the listing or valuation team when required.
Stop and escalate
Stop automation for no affirmative permission, withdrawal, STOP request or unsupported channel. Do not use this flow for invented valuations, guaranteed sale timing or pressure tactics.
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