Speed-to-Lead Response

skill

First-touch new leads within SLA, then run a scheduled multi-touch nurture with per-lead memory.

Download .md

Speed-to-Lead Response

Respond to new real estate leads within the SLA (service-level agreement — the target response window), then run a scheduled multi-touch nurture sequence that remembers what each lead cares about.

When to use

  • A new lead lands from a portal, landing page, or CRM (customer relationship management system) and needs a fast first reply.
  • The lead does not book or respond immediately and needs a structured follow-up cadence instead of a one-off message.
  • You need to track lead-specific details (budget, area, timeline) across multiple touches without repeating questions.

Tools

  • http-get
  • send-email
  • send-message
  • schedule-task
  • update-memory

Playbook

  1. On new lead notification, use http-get to pull the lead record from the CRM, e.g. GET https://api.example-crm.com/v1/leads/{id}, to confirm contact details, source, and any stated preferences.
  2. Check the elapsed time since lead creation against the SLA (typically under 5 minutes for hot leads). If the SLA window has already passed, note this and proceed with the fastest possible first touch.
  3. Send the first-touch reply immediately with send-email or send-message (whichever channel the lead used), acknowledging the inquiry and asking one qualifying question (budget range, target area, or timeline).
  4. Use update-memory to record what you learned: lead name, source, stated preferences, first-touch timestamp, and channel used. This becomes the per-lead memory the nurture sequence reads from.
  5. Use schedule-task to queue the next nurture touch (for example, a check-in 1 day later, then 3 days, then 7 days) if the lead has not replied or booked a showing.
  6. On each scheduled touch, re-read the lead's memory (via update-memory history) before drafting the message so follow-ups reference prior answers instead of repeating questions already asked.
  7. If a lead replies with a question outside public listing data (financing terms, contract advice, negotiation strategy), do not answer — this requires human handoff. Use send-message to alert the assigned agent with the lead's question and context.
  8. When a lead requests a showing or asks to speak with an agent directly, stop the automated sequence: cancel remaining scheduled touches and use send-message to hand the lead to the human agent with a summary of the conversation so far.
  9. If a lead goes cold after the final scheduled touch (no reply after the last nurture step), update memory with a "cold" status and stop scheduling further touches until a human re-engages.

Failure modes

  • Answering pricing, financing, or contract questions directly instead of routing to a human — always hand off legal or financial (loan, closing cost, contract term) questions.
  • Sending duplicate first-touch messages because the lead source posted the same lead twice; check memory for an existing record before replying.
  • Letting scheduled touches keep firing after a lead has already booked or gone cold, creating noise; always cancel or update the schedule when lead status changes.
  • Relying only on public portal data for lead research and never verifying against the CRM record, leading to outdated contact info or stale preferences.

Done when

  • The lead has received an acknowledged first-touch reply within the SLA window, logged with a timestamp.
  • Per-lead memory reflects the latest known preferences and status (active, booked, cold, or handed off).
  • The nurture schedule is either actively running, cancelled because the lead converted or went cold, or handed to a human agent.