Source-bounded implementation brief

Qualification for a Open-house lead

For a open-house lead, qualification 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 intent, timeline, stated budget, constraints, missing fields and confidence. Use that evidence to decide which questions are relevant and whether human review is needed, 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

intent, timeline, stated budget, constraints, missing fields and confidence.

Four-step implementation

  1. Collect only the stated event, property source, attendance intent, contact permission and requested next step.
  2. Create the stage record: intent, timeline, stated budget, constraints, missing fields and confidence.
  3. Use the record to decide which questions are relevant and whether human review is needed.
  4. Stop when protected-class inference, lending decision, legal advice or insufficient evidence; pass context to the listing team responsible for the event when required.

Stop and escalate

Stop automation for protected-class inference, lending decision, legal advice or insufficient evidence. Do not use this flow for surprise messaging, implied representation or inaccurate event details.

Evidence boundary

Qualification organizes stated needs; it must not become discriminatory screening, credit approval or a prediction of transaction success. 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