Source-bounded implementation brief

CRM routing for a Open-house lead

For a open-house lead, crm routing 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 lead type, territory, language request, property, owner, queue, reason and timestamp. Use that evidence to decide which authorized team or person receives the record, 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

lead type, territory, language request, property, owner, queue, reason and timestamp.

Four-step implementation

  1. Collect only the stated event, property source, attendance intent, contact permission and requested next step.
  2. Create the stage record: lead type, territory, language request, property, owner, queue, reason and timestamp.
  3. Use the record to decide which authorized team or person receives the record.
  4. Stop when no eligible owner, duplicate record, conflict rule or required manual assignment; pass context to the listing team responsible for the event when required.

Stop and escalate

Stop automation for no eligible owner, duplicate record, conflict rule or required manual assignment. Do not use this flow for surprise messaging, implied representation or inaccurate event details.

Evidence boundary

Routing rules must match the actual CRM, staffing and permissions. Assignment does not prove response or acceptance. 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