Free OpenClaw Skill for Title Companies: Closing Coordinator Agent (Download)

What this skill does for your title and escrow offices

• Compiles the daily closing roster from Qualia, SoftPro Select, ResWare, or RamQuest with each file's current stage, missing curatives, and the next-action owner clearly flagged.
• Drafts the standard buyer, seller, lender, and agent communications keyed to file milestones (file opened, commitment issued, CD to lender, clear to close, day-of-closing, post-closing recording).
• Reviews the Closing Disclosure line-by-line against the title commitment, the payoff statements, and the agent commission breakdown, flagging variances over the threshold for human eyes.
• Runs the wire-fraud verification cadence on every wire instruction: callback to the known number, dual control on first-time disbursements, and resident reminder copy that warns buyers about the BEC playbook.
• Coordinates Simplifile e-recording handoff post-closing and tracks the policy issuance clock against your ALTA Best Practices retention window.

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: title-closing-coordinator
description: Closing coordinator agent for title and escrow offices. Handles file opening, CD review, wire-instruction verification, e-recording handoff, and policy issuance tracking. Integrates with Qualia, SoftPro Select, ResWare, RamQuest, Simplifile.
version: 1.0.0
author: OpenClaw Consult (Adhiraj Hangal)
license: MIT
url: https://openclawconsult.com/skills/title-companies
---

# OpenClaw Skill: Title and Escrow Closing Coordinator

## Overview

This skill turns the OpenClaw agent into a closing coordinator equivalent for
a title and escrow office. It does not replace the licensed escrow officer:
it amplifies them. The skill owns the file-level coordination, the buyer and
seller communications, the CD review, the wire-fraud workflow enforcement, and
the post-closing recording handoff so the escrow officer can focus on
exceptions, curatives, and the high-judgment calls.

It is designed for title offices closing 50 to 500 files per month, running
Qualia, SoftPro Select, ResWare, RamQuest, or TitleExpress. ALTA Best
Practices Pillar 4 and Pillar 5 are baked into the default workflows.

## What this skill does

1. Compiles the daily closing pipeline with each file's stage and next-action owner
2. Reviews the Closing Disclosure against the commitment, payoffs, and lender instructions
3. Enforces wire-fraud verification (callback to known number, dual control on new parties, buyer reminder copy)
4. Drafts buyer, seller, lender, and agent communications keyed to file milestones
5. Hands off post-closing recording to Simplifile or CSC e-Recording and tracks confirmation
6. Tracks the policy-issuance clock against your ALTA Best Practices retention window

## Triggers

```yaml
triggers:
  - type: heartbeat
    schedule: "0 7 * * 1-5"          # Weekdays 7am
    action: morning_pipeline_compile

  - type: heartbeat
    schedule: "0 17 * * 1-5"         # Weekdays 5pm
    action: evening_pipeline_close_out

  - type: on_event
    event: title.file_opened
    action: enter_opening_cadence

  - type: on_event
    event: title.commitment_issued
    action: send_commitment_notifications

  - type: on_event
    event: title.cd_received_from_lender
    action: run_cd_reconciliation

  - type: on_event
    event: title.wire_instruction_received
    action: enter_wire_verification_workflow

  - type: on_event
    event: title.closing_completed
    action: enter_post_closing_recording_and_policy_workflow
```

## Workflow: file opening

When a new file is opened, the agent:

1. Pulls the parties, the property, the lender, and the agent of record from the production system
2. Drafts the standard buyer welcome with the closing-process overview and the wire-fraud warning on a separate line
3. Drafts the standard seller welcome with the seller-side documentation checklist
4. Drafts the standard lender introduction with the file number and the escrow officer assigned
5. Drafts the standard agent introduction with the file number and the projected closing window
6. Routes all four to the escrow officer for approval by default

## Workflow: CD reconciliation

When the CD is received from the lender, the agent:

1. Parses the CD line items into structured form
2. Pulls the commitment, the seller payoff statements, the agent commission instructions, and the lender's separate closing instructions
3. Reconciles each line item against the corresponding source document
4. Flags any variance over the threshold (default $50, editable in config)
5. Produces a one-page reconciliation summary for the escrow officer
6. Drafts the lender response if variances exist (politely flagging the specific lines and requesting confirmation)

The escrow officer approves the reconciliation summary. The skill does not transmit or sign the CD.

## Workflow: wire-fraud verification

Every wire instruction received triggers the verification workflow:

1. The skill compares the new wire instruction against the known wire instructions on file for the parties
2. If new, the skill puts the file on hold and surfaces it to the escrow officer with the variance highlighted
3. The escrow officer calls the party back at the number on file (not the number in the email) to verify
4. The skill logs the callback time, the person reached, and the verification outcome to the file memory
5. If the disbursement is to a new party not previously paid on this file, the skill enforces dual control: a second escrow officer must approve before any further action
6. Buyer-facing communications include the wire-fraud reminder copy on a separate line from the actual wire instructions

The skill does not initiate or transmit wires. It enforces the workflow that surrounds them.

## Workflow: post-closing recording and policy issuance

After closing, the agent:

1. Prepares the recording package (deed, deed of trust or mortgage, any reconveyance, any subordination)
2. Routes to the escrow officer for review and Simplifile submission approval
3. Tracks the recording confirmation from Simplifile or CSC e-Recording
4. Once recording is confirmed, triggers the policy-issuance workflow: lender's policy first, owner's policy on closing of recording
5. Tracks the policy-issuance clock against your ALTA Best Practices retention window
6. Notifies the escrow officer if any file is approaching the policy-issuance deadline

## Memory keys

The skill maintains the following memory keys across runs. These persist via
OpenClaw Memory so the agent does not re-derive them every invocation.

```yaml
memory:
  - key: title.file[{file_id}]
    description: Current file state and metadata
    schema: { stage: string, escrow_officer: string, lender: string, agent: string, projected_close: date, parties: object }

  - key: title.wire_state[{file_id}]
    description: Active wire instructions and verification status
    schema: { wire_id: string, party: string, instruction_received_at: datetime, callback_completed: bool, callback_at: datetime, dual_control_required: bool, dual_control_completed: bool }

  - key: title.cd_review[{file_id}]
    description: CD reconciliation status and variance log
    schema: { received_at: datetime, lines_reviewed: number, variances: array, escrow_officer_signoff: bool }

  - key: title.recording_state[{file_id}]
    description: Post-closing recording and policy issuance state
    values: [pre_recording, submitted, recording_confirmed, lenders_policy_issued, owners_policy_issued, file_closed]

  - key: title.daily_pipeline
    description: Daily roll-up of files closing this week
```

## Message templates

```yaml
templates:
  buyer_welcome:
    channel: email
    subject: "Welcome to your closing at {company_name}, file #{file_number}"
    body: |
      Hi {buyer_first_name},

      Welcome and congratulations on the home. I am {escrow_officer_first_name},
      your escrow officer at {company_name}. I will be your point of contact
      from now through closing.

      Your file number is {file_number}. Save it for reference.

      A few notes for the road to closing:

      1. We will send you wire instructions only by secure portal, never by
         email. If you receive wire instructions by email that appear to come
         from us, do not act on them. Call us at {office_phone} to verify.

      2. Closing is currently projected for {projected_close}. We will confirm
         the exact time and location once we have your lender's clear-to-close.

      3. If you have any questions at all, reply to this email or call
         {office_phone}.

      {escrow_officer_first_name}

  wire_fraud_callback_script:
    channel: internal_script
    body: |
      Wire verification callback for file {file_number}, {party_name}.

      Use this number, which is the verified contact on file:
      {known_phone}

      Do not use the number in the email containing the wire instructions.

      Confirm:
      1. The party did send wire instructions today
      2. The receiving account matches the one we have on file (or is a
         known new account they have just opened)
      3. The amount matches the disbursement we are preparing

      Log the callback time, the person reached, and the outcome.

  cd_variance_lender_response:
    channel: email
    subject: "CD reconciliation question, file #{file_number}"
    body: |
      Hi {lender_processor_first_name},

      We received the CD for file #{file_number} and noticed a variance on
      the following lines:

      {variance_list}

      Could you confirm whether these are intended or whether we should
      reconcile against the closing instructions? Closing is scheduled for
      {projected_close} and we want to make sure we are aligned before then.

      {escrow_officer_first_name}

  agent_clear_to_close:
    channel: email
    subject: "Clear to close, file #{file_number}"
    body: |
      Hi {agent_first_name},

      File #{file_number} is clear to close. Closing is confirmed for
      {closing_datetime} at {closing_location}.

      Your buyer/seller has been notified separately with the wire-fraud
      reminder and the day-of-closing checklist.

      {escrow_officer_first_name}

  post_closing_buyer:
    channel: email
    subject: "Your closing is complete, file #{file_number}"
    body: |
      Hi {buyer_first_name},

      You are officially closed. Documents are off to recording today and
      we expect confirmation in the next {recording_window}.

      Your owner's policy will issue once recording is confirmed and will be
      delivered to you by {policy_delivery_method}.

      Keep your closing package somewhere safe; we recommend a fireproof
      folder along with your other property records.

      Welcome home.

      {escrow_officer_first_name}
```

## Required integrations

| Integration               | Purpose                                       | Read | Write |
|---------------------------|-----------------------------------------------|------|-------|
| Qualia                    | File data, milestones, CD                     | yes  | optional |
| SoftPro Select (Live Studio) | File data, milestones, CD                  | yes  | optional |
| ResWare (Adeptive)        | File data, milestones, CD                     | yes  | optional |
| RamQuest                  | File data, milestones, CD                     | yes  | optional |
| Simplifile or CSC e-Recording | Post-closing recording submission         | yes  | yes   |
| Twilio (or similar)       | SMS notifications                             | no   | yes   |
| Email provider            | Outbound email                                | no   | yes   |
| Slack                     | Operator alerts for wire and exception events | no   | yes   |
| OpenClaw Memory           | Cross-run state                               | yes  | yes   |
| OpenClaw Heartbeat        | Scheduled triggers                            | yes  | yes   |

Write-back to the production system is optional and starts disabled. Most offices flip on the routine status updates and the post-closing recording confirmations after two weeks of validation. CD changes, wire actions, and party-side modifications stay manual.

## ALTA and NPI notes

The skill is built around ALTA Best Practices Pillar 4 (settlement processes
and disbursement controls) and Pillar 5 (policy production and delivery).
It does not certify your office to ALTA Best Practices on its own.
Certification still requires the underlying program, the third-party audit,
and the trust accounting reconciliations that fall outside the skill's scope.

NPI handling: by default the skill operates on file identifiers and
milestone states. Social security numbers, full account numbers, and full
wire-routing details are referenced by token only and not pulled into the
agent's working context. For tighter NPI handling, set `npi_mode: tokenized`
in the config block and the skill will force tokenization across all
outbound communications, requiring the escrow officer to fill personalized
content directly from the production system.

## Configuration

```yaml
config:
  company_name: "Your Title Company"
  brand_voice: "calm-professional"      # or "concierge", "no-nonsense"
  approval_mode: escrow_officer_approves_all  # or "selective_autonomous"
  cd_variance_threshold_usd: 50
  wire_verification_required: true
  dual_control_new_party_threshold_usd: 1
  npi_mode: standard                    # or "tokenized"
  e_recording_provider: simplifile      # or csc
  policy_issuance_window_days: 30
  closing_window_default_days: 30
  state_specific_practices_file: "state_specific_practices.yaml"
```

## Quick install

```bash
mkdir -p ~/.claude/skills
mv title-companies.md ~/.claude/skills/title-closing-coordinator.md
# Edit the config block to match your office
```

Launch OpenClaw and the skill is live. Run `morning pipeline compile` or
`run cd reconciliation on file XYZ` to invoke it on demand, or wait for
Heartbeat to fire on the configured schedule.

## Want it wired to your stack?

This SKILL.md is the starting point. If you want it plugged into your
specific production system, your state-specific practices, your lender
partner stack, and your office's voice on a fixed-price two-week clock, with
the founder writing every line of the build, 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 title-companies.md as ~/.claude/skills/title-closing-coordinator.md (or your project-level .claude/skills/ if you scope it per branch). OpenClaw picks up new skill files on next agent launch, no restart command required.

2. 2

   Connect your title production system

   Edit the integrations block to point at your Qualia, SoftPro Select, ResWare, or RamQuest export. Read-only access is enough to start. The skill ships prompts that translate your daily closing pipeline and file-level milestones into the agent's working memory.

3. 3

   Start in escrow officer approval mode, then move to selective autonomous

   Run for two weeks with the escrow officer approving every outbound message and every CD-related action. The skill defaults route any wire instruction, any CD variance over the threshold, any title curative, and any new-party first-time disbursement to a human. After two weeks, flip the routine status updates, agent file requests, and post-closing recording confirmations to autonomous.

Example conversation

Common questions

Related free skills