An audit-ready stop reason for a lead should answer four questions: what happened, when was it checked, who owns the next decision, and what evidence would change the state? A short note can be enough: “Customer asked for no further calls on June 18; owner is operations; keep Do Not Contact unless the customer reopens the request.” That is more useful than “closed - no response.”
The evidence date prevents an old note from becoming a permanent assumption. If a request moved to another service area, the owner may need to check the current boundary. If a duplicate was merged, preserve the relationship between records. If a form contains an opt-out, keep the stop signal visible instead of hiding it inside a general status.
The next owner also needs to know whether the stop applies to internal work or customer-facing contact. A team may still need to resolve a duplicate internally while being prohibited from sending another message. A record can be operationally active and still be Do Not Contact. Those states should not be forced into one label.
Review the exception states
For service business Do Not Contact evidence, use a small redacted sample that includes stopped, paused, duplicate, and missing-context rows. Do not include passwords, payment details, full conversations, recordings, or private customer lists. Ask a second reviewer to explain each stop reason without opening the original system. If the explanation depends on an invisible note, the handoff is not yet auditable.
The Missed Lead Recovery review makes the decision boundary visible without sending messages or changing a CRM. It can show whether a row belongs in Ready, Hold, Duplicate, Do Not Contact, or Missing Context. The owner remains responsible for checking permission and deciding what to do.
A good stop reason is not a dead end. It is a small piece of operational evidence that protects the next person from making the same assumption again. When the reason, date, owner, and change condition are visible, a pause becomes something a team can inspect instead of a record that silently disappears from the queue.
Start with a bounded review: use a small redacted sample. AI Cleanup Doctor does not send messages, change a CRM, or decide contact permission. See the local-only review.
Review boundary: This article organizes supplied evidence. It does not prove platform fault, employee fault, attribution accuracy, duplicate billing, consent, lead quality, calls, jobs, rankings, orders, ROI, revenue or AI citations.