NOD/NTS Foreclosure-Stage Disposition System

Business problem

The client's existing outbound system (Signal Sniping / "Niche Data" SMS campaigns) treated all foreclosure-stage leads (NOD and NTS homeowners) with one generic non-responder path. NOD and NTS leads are homeowners at legally distinct stages of foreclosure, each requiring different urgency, compliance handling, and emotional context: a homeowner 90+ days from auction needs a different cadence than one 7 days out; a bankruptcy filing triggers an automatic legal stay where continued outreach is a compliance risk, not just poor customer experience; a reinstated loan should be nurtured, not sold to; and heirs of a deceased owner need a different conversation entirely, avoiding certain legal terminology and flagging situations a bot should never navigate alone. The client needed these distinctions enforced inside the CRM itself, not left to inconsistent human judgment, while staying inside the existing disposition-engine architecture already built for them.

Flow

My role

• Translated client call notes and a written SOP (trigger conditions, cadences, SMS copy, AI bot objectives, and edge cases for all 7 dispositions) into a fully implemented, live GoHighLevel build.
• Designed and built the GHL automation logic for all 7 new dispositions.
• Extended the existing shared seller_disposition-changed sync automation (from the core Seller Disposition Engine) rather than building parallel one-off workflows.
• Designed and built the auction-date compliance automation for NTS Active.
• Built the Bankruptcy Hold compliance-check reminder as an automated CRM task.
• Translated the client's legal/compliance edge cases (bankruptcy stay, heir disputes, minor heirs) into CRM-enforceable logic rather than documentation alone.

Technical implementation

• Core extension point: the existing seller_disposition-changed sync automation gained 7 new branches, each handling tag application, pipeline stage update, and disposition-specific campaign enrollment.
• The 7 dispositions: NOD Early (1 text every 3–4 days for 30 days, then weekly), NTS Active (1 text every 1–2 days, with auction-date auto-stop), NTS Postponed (1 text every 5 days, re-escalates as new auction date nears), NOD Reinstated (1 text every 30 days indefinitely), Bankruptcy Hold (zero outreach, AI bot disabled, automated 30–45 day compliance-check task), Referred to Housing Counselor (1 text every 21 days, warm-only tone), and Heir Follow Up (1 text every 3 days for 21 days then weekly, probate-avoidance messaging with human handoff on legal edge cases).
• Auction-date compliance automation (NTS Active) — the most senior-level build in this project: triggers on the auction_date custom field changing, gated on seller_disposition = "NTS Active", waits until auction_date equals today, then removes the contact from the NTS Active SMS campaign. The team manually reclassifies the contact after the auction based on outcome.
• Lead entry point: leads enter this 7-disposition system either as non-responders falling out of the Signal Sniping campaign, or via manual disposition assignment after a qualifying call confirms a specific legal situation.
• AI bot logic: disposition-specific objective sets — e.g. NTS Active's bot urgently confirms auction date and reinstatement amount same-day; NOD Reinstated's bot stays soft and relationship-first; Heir Follow Up's bot avoids certain legal terminology and flags disputed-heir or minor-heir situations for human handoff. Bankruptcy Hold disables the AI bot entirely while the legal stay is active.

Architecture

Non-responders from the Signal Sniping campaign, or leads manually classified after a qualifying call, trigger the shared seller_disposition-changed sync automation (now with 7 new branches) which sets tag, pipeline stage, and campaign enrollment. NTS Active additionally watches auction_date and auto-removes the contact from outreach once the auction date arrives; Bankruptcy Hold disables all outreach and the AI bot, replacing it with an automated 30–45 day compliance-check task.

Challenges

• Compliance requirements (auction-date hard stop, bankruptcy-stay outreach freeze) could not be left as documentation-only steps — failure to enforce them programmatically creates real legal exposure for the client, not just a degraded customer experience.
• Translating plain-language SOP triggers ("auction date gets postponed," "seller files bankruptcy") into exact field-level conditions and trigger types required care to ensure system behavior matched intent precisely.
• Extending shared infrastructure (the existing seller_disposition-changed automation) without disrupting the original 20-stage disposition engine already live on that same automation.

Solutions

• Built the auction-date hard stop as a field-change-triggered, condition-gated, Wait-Until-field-value automation — entirely native to GoHighLevel, no external scheduler or third-party dependency.
• Disabled the AI bot entirely for Bankruptcy Hold and replaced human-memory-dependent monitoring with an automated 30–45 day compliance-check task in GHL.
• Extended the existing shared sync automation rather than duplicating workflow logic, keeping the architecture consistent with the core Seller Disposition Engine.

Results

Technologies

GoHighLevel (custom fields, workflow automations, Wait Until field-value conditions, tags, pipeline stages, SMS campaigns, automated tasks) · Closebot AI (disposition-specific bot objectives)