Source-bounded implementation brief

Showing request for a Seller lead

For a seller lead, showing request 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 property, requested windows, timezone, attendee details, confirmation state and owner. Use that evidence to decide whether to request, hold, confirm, change or cancel a time, 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

property, requested windows, timezone, attendee details, confirmation state and owner.

Four-step implementation

  1. Collect only the stated property address, ownership role, motivation, timeline and requested valuation help.
  2. Create the stage record: property, requested windows, timezone, attendee details, confirmation state and owner.
  3. Use the record to decide whether to request, hold, confirm, change or cancel a time.
  4. Stop when no verified availability, missing responsible agent, conflict or unconfirmed attendee; pass context to the listing or valuation team when required.

Stop and escalate

Stop automation for no verified availability, missing responsible agent, conflict or unconfirmed attendee. Do not use this flow for invented valuations, guaranteed sale timing or pressure tactics.

Evidence boundary

A request is not a confirmed appointment. Calendar, property access and agent approval must remain authoritative. 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