Automated Outreach (GHL)

Fire the first touch on every fresh pre-foreclosure lead automatically, by text and email, before a human ever knocks a door or dials a phone. The engine keeps every lead moving on the right cadence so nobody goes cold from neglect, and it hands off to a person the moment a lead replies.

• A brand-new NOD (notice of default) lead lands in the system and needs its first touch the same day
• An enrolled lead is due for its next scheduled touch per its badge (Gold, Silver, Bronze)
• A lead has gone unresponsive and is due for a re-touch on the spaced schedule
• Any day the engine is live and leads are flowing through the pipeline, which is every day starting this Monday

• The messaging number is registered for business texting (A2P 10DLC) before the engine sends a single message. Nothing goes live on an unregistered number.
• Every lead entering the engine has already been scrubbed for LITIGATOR status. A lead labeled LITIGATOR never enters the automated engine, full stop.
• Every lead's DNC status is visible in the CRM before the engine touches it. DNC leads stay in the database but are excluded from automated sends; see the compliance note below.
• The lead's badge (Gold, Silver, Bronze) and timeline position are set per sop-kod-cadence-by-badge so the engine sends at the right frequency from the first touch.
• A setter or closer is available to pick up any reply within the speed-to-lead window. The engine only works if a human is standing by to catch what it starts.

• Every brand-new NOD lead received its first automated touch the same day it was scrubbed and badge-tagged
• No message went out before 8am or after 9pm local to the lead's property address
• No LITIGATOR-flagged lead is enrolled in the engine, and no DNC-flagged lead received an automated send
• Every inbound reply got a human response inside the speed-to-lead window, not just a queued next-day follow-up
• Every automated touch, scheduled or re-touch, is logged on the lead's record with an accurate next-touch date
• The messaging number's A2P 10DLC registration is current, not lapsed

• Problem: A lead that should have gotten a same-day first touch didn't send until the next day. Fix: Check whether the scrub (litigator check) or badge tagging was the bottleneck. The send can't fire until both are done, so fix whichever step is lagging rather than manually pushing the send.
• Problem: A DNC-labeled lead got an automated text. Fix: Stop the engine's sends to that lead immediately and confirm the DNC flag is actually set in the CRM, not just noted somewhere else. Escalate per sop-kod-close-compliance for how to handle the lead going forward; automated contact does not resume.
• Problem: A reply came in but nobody picked it up inside the 60-second window. Fix: Check whether a setter or closer was actually staffed and watching inbound during that time block. Respond as soon as it's caught, but treat the miss as a staffing gap to fix for the next block, not a one-off.
• Problem: A lead is getting touched by the automated engine and also getting cold-called or door-knocked on the same day with conflicting messaging. Fix: Confirm the automated touch was logged to the CRM per step 7. If it wasn't logged, a human working their own list won't see it and will duplicate the outreach. Log retroactively and note the gap.
• Problem: Messages stopped sending across the board. Fix: Check the A2P 10DLC registration status on the messaging number first; a lapsed registration blocks sends silently. This is a registration issue, not a cadence issue.