What OptProof can and can't do
Your CRM sends texts and places calls itself, and it gives apps no way to stop a send at the last second. So OptProof works in three ways: it puts do-not-disturb flags on contacts who shouldn't be contacted (the CRM then blocks them), it offers a Rule Check step you place before workflow texts, and it checks every send after it goes out. This table says plainly what that covers.
| Situation | What OptProof does | Guarantee? |
|---|---|---|
| A contact has a DND set by OptProof (litigator, DNC without consent, revoked, internal DNC) | the CRM blocks sends on that channel | Yes, for the send paths the CRM's DND covers. Which paths those are (Conversation AI, review requests, appointment reminders, bulk) is listed in the help docs |
| A workflow text with the Rule Check placed before it | Held until allowed, or failed | Yes, while the action stays in the workflow and premium actions are on. If removed, the CRM skips it (fails open) |
| A workflow text without the Rule Check, sent in quiet hours | Logged and flagged after it is sent | No. Detection only |
| A text typed by a user in the Conversations tab or mobile app at 9:30pm | Logged and flagged after it is sent | No. the CRM has no pre-send hook |
| Any phone call | Call DND for flagged contacts; logged and flagged after | No in-path control of calls |
| A contact created and texted within seconds, before the lookup returns | Held only if the Rule Check is the first workflow step | Partial |
| Accuracy of DNC, litigator and reassigned data | Reads the customer's own scrubber results; stores the source and list date; flags results older than 31 days | No. The data comes from the customer's scrubber and can be incomplete or stale |
| Where the contact actually is | Contact time-zone field, then address, then area code; when unsure, applies the strictest window of all candidates | No. Phones move; area codes are not locations |
| Whether a message is "marketing" or "informational" | Uses the purpose the customer sets on the action or the account default | No. The customer decides |
| Whether a consent record is legally sufficient | Stores what was captured, with proof | No. That is a legal question |
| Messages sent before install, or through other providers | Not covered, or monitored only if the CRM reports them | No |
| Legal compliance overall | — | Never claimed. The app is a tool, not legal advice |