Source-bounded implementation brief
Structured intake for a Seller lead
For a seller lead, structured intake 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 source URL, inquiry topic, supplied contact fields, free-text request and timestamp. Use that evidence to decide whether enough context exists to continue or ask one clarifying question, 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
source URL, inquiry topic, supplied contact fields, free-text request and timestamp.
Four-step implementation
- Collect only the stated property address, ownership role, motivation, timeline and requested valuation help.
- Create the stage record: source URL, inquiry topic, supplied contact fields, free-text request and timestamp.
- Use the record to decide whether enough context exists to continue or ask one clarifying question.
- Stop when sensitive data, unsupported request, empty inquiry or user request to end; pass context to the listing or valuation team when required.
Stop and escalate
Stop automation for sensitive data, unsupported request, empty inquiry or user request to end. Do not use this flow for invented valuations, guaranteed sale timing or pressure tactics.
Evidence boundary
Intake records what the person supplies; it does not validate identity, representation, facts or eligibility. 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