Building a compliant TCPA process.

kx 21 Contact.IO 2026 Denver · Aug 23–25 TCPA Compliance · Inbound Calls Beyond policies — creating defensible workflows for raw inbound calls. Jordan Soblick · kx21.com 2026

Treat every inbound as an outbound.

kx 21 The Challenge · 01 // The Golden Rule Inbound compliance isn't about policies — it's about process. Operate as if every caller could be a litigator, and build the workflow that proves it. kx21.com Contact.IO 2026

The raw inbound problem.

kx 21 The Challenge · 02 The core issue Countless companies take RAW inbounds with no verification layer. TCPA litigation stays at elevated levels in 2026 — yet raw calls still go straight to an agent. When we point it out, the answer is always the same: " How else can I do it? — The question we're here to answer.

The "consumer-generated" myth.

Everyone wants to hear it

Platform reporting gaps

Best-effort utilities

kx 21 Reality Check · 03 Reality check 01 "Consumer generated" sounds like the magic answer. No vendor can truly guarantee it. 02 Facebook and Google Ads rarely provide reporting adequate to support the claim. 03 Form-verification tools document behavior, not intent — rarely holding up in litigation. Use them as one layer — never your only defense.

No single layer is foolproof. The stack is the strategy.

kx 21 The Solution · 04 A cohesive, common-sense approach 01 Hosted webform + pre/post-ping Scrub before the call connects 02 Form verification software Kapture / TrustedForm 03 Kurrent · SIP routing & DID tracking Every call mapped to its source, end to end 04 IVR caller-ID verification Phone must match the lead record 05 TCPA litigation scrub Known-litigator blacklists 06 Carrier dip analysis Line type · subscriber · address 07 Line-type & burner detection Flag non-fixed VOIP 08 Subscriber name matching Lead name vs registered subscriber 09 Express consent reverification Recorded on every call 10 Strategic script disqualifiers Questions litigators can't answer

Hosted webform, pre & post-ping.

kx 21 Step 1 of 5 Step 1 · Layers 01–02 Pre-ping Low-cost scrubs first — internal DNC, cheap databases. Filter obvious bad leads before you spend. Post-ping Premium scrubs — reassigned-number database, plus session capture & form verification (Kapture or similar). 01 Partner webform → 02 Pre-ping scrubs → 03 Post-ping scrubs → 04 Form verification → 05 Qualified → IVR Product · Kapture Require your hosted webform — no exceptions. Kapture builds one instantly, matched to your page's design, then video-proofs every submission — including the TCPA consent given — as a tamper-evident record in your own bucket.

Never connect directly to agents.

kx 21 Step 2 of 5 // Step 2 · The gate When a lead enters your inbound universe, every call passes through verification layers first — whether the agent is live or AI. No raw call reaches a human.

A bulletproof IVR.

kx 21 Step 3 of 5 Step 3 · Layer 04 · Non-negotiable The lead's phone number must match the inbound caller ID. Vendors routinely modify caller IDs to circumvent form rejections. Lead record (614) 555-0148 = Inbound caller ID (614) 555-0148 → Route to IVR Lead record (614) 555-0148 ≠ Inbound caller ID (702) 555-9931 ✕ Drop — "Could not connect"

Screen the call before you answer.

kx 21 Layer 03 · Screening gate Kurrent × KontrolX · screen at the SIP edge On every inbound DID, Kurrent queries KontrolX as a screening API — blacklist · prior disposition · consent — and allows or drops the call at the SIP edge, before it ever connects. The gated-IVR logic, one step earlier. Inbound DID (614) 555-0148 → KontrolX screen Clean · consent on file ✓ Connect & route Inbound DID (702) 555-9931 → KontrolX screen Blacklist hit ✕ Drop at the SIP edge Slips through mid-stream? Kurrent kills the bad DID , traces the lane , and caps the source — without touching good traffic.

Run the TCPA litigation scrub.

TCPA Litigator Blacklist

TCPA Litigator List

WebRecon (or equivalent)

kx 21 Step 4 of 5 Step 4 · Layer 05 Once the phone number matches, run least-costly routing against known-litigator sources. A Industry-maintained database of known serial litigators. B Cross-reference against filed TCPA lawsuits. C Comprehensive professional-litigant identification.

Carrier dip analysis.

kx 21 Step 5 of 5 Step 5 · Layers 06–08 Line-type verification Identify non-fixed VOIP "burner" numbers — a strong signal of litigation intent. Subscriber-name matching Lead name vs. subscriber record. Family plans differ — even imperfect data is a useful signal. Address verification Confirm the physical address tied to the phone number. Partner · here at Contact.IO We recommend our friends at TrestleIQ — go stop by their booth. Their enrichment & screening APIs plug straight into KontrolX , our lead-orchestration & attribution platform at kx21.

The agent probing technique.

kx 21 Agent Technique · 05 When subscriber name ≠ lead name " We notice you provided your name as [X], but your phone number is showing registered to someone else. Can you verify your home address? Deploy whenever subscriber name does not match the lead record.

Reverify express consent on every call.

kx 21 Operating Principle · 06 Layer 09 · Operate as if everyone is a litigator " Before we proceed, and in case we get disconnected, I need to read you a consent statement. A simple, non-disruptive addition to any call script. ✓ Creates a documented, recorded consent event on every call ✓ Provides a fresh legal basis regardless of lead source ✓ Simple, non-disruptive, works with any existing script

The courts are shifting.

Oral consent is sufficient

Texts aren't "telephone calls"

kx 21 Legal Precedent · 07 Two 2026 rulings 5th Circuit · Feb 2026 Bradford v. Sovereign Pest Control — the statute says "prior express consent," not "written." The court rejected the FCC's 2012 written-consent rule, applying Loper Bright 's end of Chevron deference. Binds the 5th Circuit only. Other circuits & state laws may still require written consent. 7th Circuit · Jul 2026 Steidinger v. Blackstone Medical — unwanted marketing texts aren't "calls" under §227(c)(5), killing the private DNC text claim in IL, IN & WI. First circuit to rule after McLaughlin . §227(b) autodialer claims & state statutes survive. 7th Circuit only. Bradford v. Sovereign Pest Control of TX, Inc., No. 24-20379 (5th Cir. Feb. 25, 2026). · Steidinger v. Blackstone Medical Services, No. 25-2398, 2026 WL 2028517 (7th Cir. July 14, 2026); see McLaughlin Chiropractic Assocs. v. McKesson Corp., 606 U.S. 146 (2025). Source: Holland & Knight alerts (Mar. & Jul. 2026).

Strategic script devices.

kx 21 Strategy · 08 Layer 10 · Closing statements The closing statement of truth " Since we're submitting this to a company contracted under [Government Entity], I need to read you a Statement of Truth and record your consent: the information provided on today's call is true and accurate, given of your own free will — and not under the duress or guidance of any third party. A recorded closing that directly rebuts a manufactured or coached claim. Disqualifiers — the asymmetry Specific account numbers Policy or account numbers genuine prospects have and litigators don't. Insurance / MBI details A natural friction point bad actors can't clear. Details they don't have Legitimate consumers answer. Litigators can't.

Mark Dobronski.

kx 21 Real-World Case Study · 09 Specialty Medical Equipment, Inc. v. Dobronski RICO countersuit ✓ 1 Feb 3, 2025 The false patient Used a false alias and fabricated Medicare ID to pose as a DME patient needing diabetes & sleep-apnea supplies. Called Specialty Medical Inc. 2 Feb 4, 2025 The callback Called back to "verify" — building a convincing false patient profile across two days. 3 The trap Identity revealed Disclosed his real identity — and that the callback number was on the Do-Not-Call Registry. A manufactured TCPA claim. ✓ Feb 26, 2026 Specialty Medical countersued under RICO Judge Goldsmith denied Dobronski's motion to dismiss on all four grounds — RICO enterprise, wire fraud, pattern of racketeering, and Noerr-Pennington all rejected. Specialty Medical Equipment, Inc. v. Dobronski et al., No. 2:25-cv-10664, 2026 WL 540262 (E.D. Mich. Feb. 26, 2026).

MBI Verification API.

How it works

Why it matters

Thought leadership

kx 21 Fraud Prevention Tool · 10 A tool we built Validate a Medicare Beneficiary Identifier in real time — before passing a consumer to an agency. 01 AI or live agent collects the MBI during the call. The API validates it instantly — invalid numbers flag on the spot. 02 Fraudulent actors and serial litigators can't provide a valid MBI. Legitimate consumers pass easily. 03 Build verification gates litigators simply cannot pass. Script + API tools cut fraud.

27 phones is a business, not a nuisance.

kx 21 Legal Strategy · 11 Challenging the serial litigator's standing DNC protects residential — not business A litigator running 27+ numbers has converted those phones into a commercial instrument, outside the DNC's zone of protection. Outside the zone of protection The TCPA was enacted to protect consumers from unwanted calls at the dinner table — not to arm a business built on manufactured claims. 27 phones = inviting contact A person with 27 phones is operating a business, not being "bothered." Courts may look favorably on the argument. Counsel's note — consult your litigation attorney before deploying these arguments in court.

Ten layers. One defense.

kx 21 Summary · 12 The complete TCPA-proofing process 01 Hosted webform + pre/post-ping Scrub before connect 02 Form verification software Kapture / TrustedForm 03 Kurrent · SIP routing & DID tracking Every call mapped to its source, end to end 04 IVR caller-ID verification Match or drop 05 TCPA litigation scrub Litigator blacklists 06 Carrier dip analysis Line · subscriber · address 07 Line-type & burner detection Non-fixed VOIP 08 Subscriber name matching Name vs registration 09 Express consent reverification Recorded, every call 10 Strategic script disqualifiers Questions litigators fail

Spend where it matters most.

kx 21 Economics · 13 Cost vs. risk management Pre-ping Internal DNC lists, cheap databases — filter obvious bad leads first. Low cost · every lead Post-ping Reassigned-number DB, TCPA scrubs — only on leads that pass the first gate. Premium · gated Per-call Line-type verification, subscriber matching — only for leads clearing both pings. Targeted · fewest

Common mistakes.

kx 21 Avoid These · 14 Avoid these ✕ Relying solely on form verification as your compliance strategy ✕ Skipping caller-ID verification in your IVR system ✕ Not documenting consent on the call itself ✕ Failing to probe or escalate mismatched subscriber information

The recommended stack.

kx 21 Recommendations · 15 Technology & outcomes Technology stack Call routing & DID tracking Kurrent — SIP on your Telnyx, end-to-end Session capture & forms Kapture or TrustedForm Carrier intelligence TrestleIQ TCPA scrubs Litigator Blacklist · Litigator List · WebRecon Reassigned numbers Industry-standard RNDAS providers Outcomes & impact ✓ Reduced litigation risk Without killing conversions or adding friction for genuine prospects ✓ Documented compliance trail Every step supports your legal defense ✓ Agent empowerment Identify bad actors and act in real time ✓ Business velocity maintained Filters bad actors, not legitimate calls

Document everything.

Form submissions

IVR verification

Recorded consent

Agent notes

kx 21 Documentation · 16 Building your litigation defense 01 Timestamps and verification results. 02 Results and caller-ID match / mismatch events. 03 Consent statements captured on every call. 04 Verification discrepancies and escalation records. Kapture · E-Sign Campaign requires a signed document — a legal retainer , a disclosure? Kapture 's e-sign captures a legally-binding signature with video proof — IP + time/date stamp of who signed — at a fraction of a DocuSign or SignNow envelope. Key takeaways: Treat every inbound as outbound · Never rely on a single layer · Caller-ID matching is non-negotiable.

kx 21 Recommended Counsel · 17 Recommended counsel ⚖ "Understanding the client's real goal is at the heart of success in litigation. The best results come from a strong strategy at the very beginning, tailored to the client." Attorney Lisa Messner — Partner, Mac Murray & Shuster LLP Contact [email protected] · (614) 939-9955 Experience 20+ years TCPA & class-action defense Recognition Best Lawyers in America® 2024 · AV Preeminent® Awards Ohio Super Lawyer® · Columbus CEO Top Ohio Lawyers Admitted OH · IL · DC · multiple federal circuits · pro hac vice FL, TX, CA, IN, MD

Questions?

kx 21 Contact.IO 2026 Thank you · the kx21 product family KontrolX Orchestrate Lead orchestration & attribution. Intake → enrich → screen → place. Sell the whole system, not every lead. kx21.com Kurrent Route Call routing & tracking on your Telnyx — SIP routing, ring trees, attribution, recording, payouts. kx21.com Kapture Prove Forms, proof & e-sign — build a form instantly, then video-proof every submit & signature (incl. TCPA consent) in your bucket. kx21.com Komms Answer AI voice agents that work the phones — priced by concurrent line, minutes & LLM included. kx21.com Jordan Soblick [email protected] Scan to sign up kx21.com