Source-bounded implementation brief

Follow-up sequence for a Buyer lead

For a buyer lead, follow-up sequence 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 purchase timeline, budget range, financing status, target area and property constraints only as relevant to this stage. Store approved channel, template version, send window, prior activity, attempt count and stop state. Use that evidence to decide whether another approved message is due, then hand off to an authorized agent with property context when the stop conditions require it.

Required workflow record

Lead context

purchase timeline, budget range, financing status, target area and property constraints.

Stage record

approved channel, template version, send window, prior activity, attempt count and stop state.

Four-step implementation

  1. Collect only the stated purchase timeline, budget range, financing status, target area and property constraints.
  2. Create the stage record: approved channel, template version, send window, prior activity, attempt count and stop state.
  3. Use the record to decide whether another approved message is due.
  4. Stop when reply, opt-out, invalid contact, appointment, owner pause or attempt limit; pass context to an authorized agent with property context when required.

Stop and escalate

Stop automation for reply, opt-out, invalid contact, appointment, owner pause or attempt limit. Do not use this flow for steering, invented availability or unverified financing conclusions.

Evidence boundary

Automated follow-up requires consent, suppression and local messaging rules; sequence execution does not guarantee delivery or response. 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