Free OpenClaw Skill for Real Estate Brokerages: ISA and Transaction Coordinator Agent (Download)

What this skill does for your real estate brokerages

• Triages new leads from Zillow, Realtor.com, Homes.com, and your IDX site through Follow Up Boss, kvCORE, Sierra Interactive, or BoomTown with intent (active buyer, future buyer, seller, investor, just-curious) and routes to the right agent by zip code and specialization.
• Runs the new-lead speed-to-lead cadence: first message inside 5 minutes, second at hour 1, third at hour 24, drop-off lead reactivation at day 7, 30, 90, and 6 months.
• Manages transaction milestones from accepted contract to close: inspection 5 days, appraisal 7-14 days, financing contingency, title, walk-through, with each milestone chased through dotloop or SkySlope.
• Reactivates the contact database on a 30-, 90-, and 365-day cadence by buyer-state (warm-buyer, cold-buyer, past-client) with house-anniversary touchpoints baked in for closed clients.
• Pulls MLS data (via RETS or RESO Web API) for daily new-listing alerts to active buyer searches and price-drop alerts to favorited listings.

What's inside this OpenClaw skill

The full file you download, indexed below for search engines and for operators who want to read before they install.

---
name: real-estate-isa-tc
description: ISA and transaction coordinator agent for real estate brokerages. Handles overnight lead triage, 5-minute speed-to-lead, MLS new-listing and price-drop alerts, transaction milestone chase from contract to close, and database reactivation. Integrates with Follow Up Boss, kvCORE, Sierra Interactive, BoomTown, dotloop, SkySlope.
version: 1.0.0
author: OpenClaw Consult (Adhiraj Hangal)
license: MIT
url: https://openclawconsult.com/skills/real-estate-brokerages
---

# OpenClaw Skill: Real Estate Brokerage ISA and Transaction Coordinator

## Overview

This skill turns the OpenClaw agent into a combined ISA (inside sales agent)
and transaction coordinator equivalent for your residential real estate
brokerage. It does not replace the ISA team or the in-house TC: it amplifies
both. The skill owns the speed-to-lead messaging, the agent matching, the
transaction milestone chase, and the database reactivation so the human team
spends their day on qualified buyers and sellers, not on chasing tire-kicker
text messages.

It is designed for residential brokerages, teams, and indie brokers. Small
commercial deals (under $5M sale, under $50K monthly lease) work; larger
commercial has a different workflow and is not in scope here.

## What this skill does

1. 5-minute speed-to-lead messaging across Zillow, Realtor.com, Homes.com,
   IDX
2. Lead triage and agent matching by zip code, price range, and specialization
3. Transaction milestone chase: inspection, appraisal, financing contingency,
   title, walk-through
4. Database reactivation at 30-, 90-, 365-day, and house-anniversary cadence
5. MLS new-listing and price-drop alerts to active buyer searches
6. Past-client referral-ask sequence at closing anniversary

## Triggers

```yaml
triggers:
  - type: heartbeat
    schedule: "0/5 6-23 * * *"       # Every 5 minutes during awake hours
    action: poll_crm_for_new_leads_and_run_speed_to_lead

  - type: heartbeat
    schedule: "0 6 * * *"            # Daily 6am
    action: sync_mls_overnight_changes

  - type: heartbeat
    schedule: "0 8 * * 1"            # Mondays 8am
    action: compile_weekly_pipeline

  - type: heartbeat
    schedule: "0 9 * * 1"            # Mondays 9am
    action: run_database_reactivation_queue

  - type: on_event
    event: lead.created
    action: run_speed_to_lead

  - type: on_event
    event: contract.accepted
    action: enter_transaction_milestone_chase

  - type: on_event
    event: listing.price_dropped
    action: alert_matching_buyer_leads

  - type: on_event
    event: transaction.closed
    action: enter_post_close_nurture
```

## Workflow: speed-to-lead

When a new lead lands in Follow Up Boss, kvCORE, Sierra Interactive, or
BoomTown, the agent (inside 5 minutes):

1. Classifies the lead intent: active buyer (specific listings viewed),
   future buyer (general search, 3-12 month timeline), seller (home valuation
   request), investor (cash buyer, multiple inquiries), mortgage-only,
   tire-kicker, or junk
2. Drafts the first message keyed to intent (a buyer-of-three-specific-
   listings gets a different first message than a generic
   "what is my home worth")
3. Routes to the right agent by zip code, price range, and specialization
4. Logs the agent assignment and the message draft for agent approval
5. Falls back to autonomous send for templates the operator has marked
   as proven

The 5-minute window is the industry-standard threshold: leads contacted
inside 5 minutes are 9x more likely to convert than leads contacted at hour
1. The skill is purpose-built to keep the window green even overnight.

## Workflow: agent matching

The agent matching engine uses:

- Geographic match (lead's interested zip codes against agent's specialization)
- Price range match (lead's stated price range against agent's typical
  deal size)
- Specialization match (luxury, first-time buyer, investor, relocation,
  new construction)
- Agent capacity (current pipeline depth, days on duty, AGI quota status)
- Round-robin fallback when no perfect match exists

The matching logic lives in the config block and should be tuned to the
team's referral and lead-distribution rules.

## Workflow: long-cycle nurture

Future buyers (6-12 month timeline) enter a long-cycle nurture cadence:

- Week 1: friendly intro touch with neighborhood market overview
- Month 1: market update with neighborhood-specific stats
- Month 2: comparative analysis of recent sales in target zip codes
- Month 3-6: monthly market update with hand-picked listing examples
- Month 6+: shift to active-buyer cadence if engagement signals improve

The nurture content references the lead's stated criteria (target zip codes,
price range, bed/bath, must-haves) so each touch feels personalized.

## Workflow: MLS alerts

When new MLS data lands (RETS or RESO Web API):

1. Compute the diff against the prior pull (new listings, price drops,
   status changes, sold)
2. Cross-reference new listings against active buyer searches
3. Cross-reference price drops against favorited listings
4. Draft the alert messages keyed to the customer's stated interest
5. Route to the agent for approval before send (autonomous send for
   operator-approved alert templates)

## Workflow: transaction milestone chase

After contract acceptance, the agent enters the milestone chase:

- Earnest money receipt (typically inside 3 business days)
- Inspection: typically 5-10 day window; chase the inspector report,
  the buyer's objection notice, the seller's response, the resolution
- Appraisal: typically 7-14 day window; chase the appraiser, the value
  determination, any value-gap negotiation
- Financing contingency: typically 17-21 day window; chase the lender,
  the underwriting clear, the clear-to-close
- Title: chase the title company for commitment, exceptions, payoff letters
- Walk-through: drafted reminder 24-48 hours before closing
- Closing: drafted client celebration message

Each milestone is logged to dotloop or SkySlope automatically. The TC reviews;
the agent signs off.

## Workflow: database reactivation

The agent maintains a database reactivation queue:

- 30-day touch: past-client check-in with market context
- 90-day touch: neighborhood market update
- 365-day touch: closing anniversary message with referral ask
- Long-cycle leads: monthly nurture per the long-cycle cadence

The reactivation messages are agent-voice and approved before send. The
skill's draft is the starting point; the agent personalizes.

## Memory keys

```yaml
memory:
  - key: lead.profile[{lead_id}]
    description: Per-lead state
    schema: { lead_id: string, source: string, intent: enum, agent_assigned: string, stage: enum, ltv_segment: enum, last_touch: datetime }

  - key: lead.search_criteria[{lead_id}]
    description: Per-lead search criteria for MLS matching
    schema: { zip_codes: array, price_min: number, price_max: number, bed: int, bath: int, must_haves: array }

  - key: transaction.milestone_state[{transaction_id}]
    description: Per-transaction milestone status
    schema: { transaction_id: string, contract_date: date, closing_date: date, milestones: array, current_milestone: enum }

  - key: agent.capacity[{agent_id}]
    description: Per-agent pipeline capacity
    schema: { active_buyers: int, active_listings: int, transactions_in_progress: int, agi_ytd: number, days_on_duty: int }

  - key: mls.last_sync
    description: MLS feed sync state
    schema: { last_synced: datetime, listings_in_market: int, new_since_last_sync: int }
```

## Required integrations

| Integration              | Purpose                                        | Read | Write |
|--------------------------|------------------------------------------------|------|-------|
| Follow Up Boss           | CRM read-write                                 | yes  | yes   |
| kvCORE                   | CRM read-write                                 | yes  | yes   |
| Sierra Interactive       | CRM read-write                                 | yes  | yes   |
| BoomTown                 | CRM read-write                                 | yes  | yes   |
| Real Geeks               | CRM read-write                                 | yes  | yes   |
| Chime                    | CRM read-write                                 | yes  | yes   |
| dotloop                  | Transaction milestone tracking                 | yes  | optional |
| SkySlope                 | Transaction milestone tracking                 | yes  | optional |
| MLS RETS / RESO Web API  | MLS data for alerts and matching               | yes  | no    |
| Twilio / SMS provider    | Lead and client SMS                            | no   | yes   |
| Email provider           | Lead and client email                          | no   | yes   |
| Slack                    | Agent alerts for high-priority leads           | no   | yes   |
| OpenClaw Memory          | Lead and transaction memory                    | yes  | yes   |
| OpenClaw Heartbeat       | Scheduled triage and reactivation              | yes  | yes   |

## Compliance and platform notes

The skill respects TCPA opt-in status from the CRM's contact records. It
will not send marketing SMS to a contact without an SMS opt-in flag. State-
specific mini-TCPA rules (Florida, Oklahoma) layer additional restrictions
and should be reviewed in the config.

MLS data is the broker's licensed data via RETS or RESO Web API. The skill
does not scrape Zillow, Realtor.com, or Homes.com listing data (that violates
their TOS). It reads inquiries from those platforms as lead sources only.

NAR settlement obligations (buyer-broker agreement signed before showings,
written compensation disclosure) layer on top of the skill's workflow. The
buyer-broker agreement process stays with the agent; the skill drafts the
reminder to send it.

Fair Housing rules apply to all outbound copy. The skill's templates avoid
steering language by design, but the firm's compliance officer should review
the templates before production.

## Configuration

```yaml
config:
  brokerage_name: "Your Brokerage"
  voice: "warm-direct"
  approval_mode: agent_approves_all_initially
  speed_to_lead_window_minutes: 5
  overnight_silence_hours: [23, 6]  # 11pm-6am: queue, do not send
  long_cycle_nurture_months: 12
  database_reactivation_cadence:
    - days: 30
      type: past_client_check_in
    - days: 90
      type: neighborhood_market_update
    - days: 365
      type: closing_anniversary_referral_ask
  agent_matching_priorities: [geography, price_range, specialization, capacity, round_robin]
  transaction_milestones:
    - earnest_money: { window_days: 3 }
    - inspection: { window_days: 10 }
    - appraisal: { window_days: 14 }
    - financing_contingency: { window_days: 21 }
    - title_clear: { window_days: 21 }
    - walk_through: { hours_before_close: 36 }
  tcpa_state_overrides:
    florida: mini_tcpa
    oklahoma: mini_tcpa
```

## Quick install

```bash
mkdir -p ~/.claude/skills
mv real-estate-brokerages.md ~/.claude/skills/real-estate-isa-tc.md
# Edit the config block to match your brokerage
```

Launch OpenClaw and the skill is live. Run `triage overnight leads` or
`compile pipeline` to invoke it on demand, or wait for Heartbeat to fire
on the configured schedule.

## Want it wired to your stack?

The free SKILL.md is the starting point. If you want it plugged into your
specific kvCORE or Follow Up Boss build-out, your agent specialization rules,
your lender and home-warranty partner workflows, and your house brand voice
on a fixed-price two-week clock, the door is at
https://www.adhirajhangal.com/work

Install in 60 seconds

1. 1

   Drop the file into your OpenClaw skills directory

   Save the downloaded real-estate-brokerages.md as ~/.claude/skills/real-estate-isa-tc.md (or your brokerage-level .claude/skills/). OpenClaw picks up new skill files on next agent launch.

2. 2

   Connect your CRM, transaction tool, and MLS feed

   Edit the integrations block to point at your Follow Up Boss, kvCORE, Sierra Interactive, or BoomTown CRM, your dotloop or SkySlope transaction tool, and your MLS RETS or RESO Web API feed. Read access is enough for the lead triage and transaction chase workflows.

3. 3

   Launch in approval mode, validate, then flip to autonomous

   Run for two weeks with the team lead or broker approving every outbound message. The skill defaults route any contract-terms question, any commission discussion, and any earnest-money issue to the agent. After validation, flip the speed-to-lead messages, the new-listing alerts, and the database reactivation to autonomous; keep transaction milestone communication in agent-approves mode.

Example conversation

Common questions

Related free skills