DialProof detects verbal opt-outs in your call transcripts, propagates suppression everywhere it legally must go, and produces the timestamped proof chain you can hand a lawyer.
No audio ever routes through DialProof. Your dialers keep dialing.
2,810 TCPA suits, up 67% in two years
Cross-channel revocation rule now applies
First AI-voice class actions are live
Class complaint seeking to hold OpenAI and Twilio liable for a customer's AI robocalls and texts on an enablement theory: the platforms allegedly facilitated and profited from the violations.
PendingFCC proposed a $4.49M forfeiture, its first know-your-customer enforcement of this kind, after illegal robocalls crossed the platform's network.
FCC · Feb 2025FCC consent decree: the voice platform admitted its robocall-mitigation certification was noncompliant and was placed under a compliance plan.
FCC · Jul 2026$1M FCC settlement for transmitting the AI voice-cloned "Biden" primary robocalls. The consultant behind the calls drew a proposed $6M fine.
FCC · 2024The pattern: enforcement and litigation now reach the platforms and infrastructure, not just the dialer.
The platforms that dial do not ship this loop. DialProof runs it on top of the stack you already use, and writes every step to an append-only ledger.
DialProof captures calls through whichever channel each platform offers: a rolling-cursor pull from its API, a post-call webhook, or both, deduplicated into a single record, so a silently dropped webhook never becomes a missing call. It can also sit inline as the gateway, receiving the vendor's payload first, recording it, then forwarding it untouched to your CRM. Every raw payload is preserved verbatim as evidence.
t + 0sNot a chatbot reading transcripts. The first pass is a deterministic scan: auditable, repeatable, versioned. Only flagged and sampled calls go to LLM adjudication, which classifies the revocation and catches the oblique phrasing a keyword list misses. Every verdict is pinned to the exact utterance and its timestamp.
t + 4sOne detection fans out automatically: DND across channels, across every sub-account holding that number, onto your internal do-not-call list, and out to your other connected dialers.
t + 8sMinute-level timestamps from detection to completed suppression, sealed into a ledger you can export. Pre-dial batch scrubbing and the audit binder ride the same spine.
t + 16sSelf-generated evidence is weak under adversarial scrutiny. When a demand letter arrives, a screenshot of your own CRM is an assertion. A third-party ledger is a record.
DialProof is structurally independent from the platforms that dial and the agencies that run them. That independence is the product: a suppression event recorded, classified, propagated, and timestamped by a system that is not you.
Every stored transcript is scanned, and the scan itself goes on the ledger. Confirmed opt-outs are sealed into an append-only chain and anchored into the Bitcoin blockchain: our first proofs confirmed in block 960334, and anyone can verify them with open-source tools, no DialProof account required. Spoken word to confirmed, sealed record: under 30 minutes, measured. And before a protected number can be dialed again, the gate answers no, with the refusal itself anchored as evidence.
If you run AI voice campaigns for clients, the exposure is yours and your clients' at once. DialProof is built to be operated by an agency and resold to the businesses it protects.
Your brand in front of your clients. DialProof stays the neutral evidence layer underneath.
Priced as a SKU you resell with margin, not a cost line you absorb. Compliance becomes a revenue item on your client invoices.
Coverage audits, alerts, and detection health checks. A DIY zap breaks silently. DialProof tells you when anything in the chain stops working.
Straight answers, because this category attracts overclaiming.
A small group of agencies will run DialProof first, at real pricing, with direct access to the team.
If AI outbound is your business, ask for a slot.
Request a pilot