Enterprise TCPA suppression
Serial TCPA filers seed their numbers into lead sources on purpose, then wait for the dial. We maintain the registry of who they are — 600,000+ litigator numbers, 100,000+ associated names, 260 million troll and DNC records — and suppress them at the moment of dial, across every brand, campaign and vendor you run.
TCPA class actions filed in the first four months of 2026 — up 23% over the same period in 2025.
TCPAWorld, June 2026Statutory damages per call or text. Willful violations run $1,500–$4,500 each, with no cap on class size.
47 U.S.C. § 227Typical cost to defend a single TCPA matter through discovery — before any settlement is paid.
2026 industry benchmarkNew litigator numbers our research team adds to the registry every month. Yesterday's list is already stale.
TCPA Litigator ListWhere standard plans stop
Self-serve scrubbing answers one question: is this number clean right now. At enterprise volume you need three more — can the pipe carry peak dial rate, can you prove the check happened, and can you isolate risk across the brands, clients and lead vendors sitting under your roof. That is a different product.
| Standard plans | Enterprise | |
|---|---|---|
| Throughput | Shared pool — 50 single-scrub calls/sec, 5 batch calls/sec | Dedicated cluster, no shared ceiling, capacity sized to your peak dial rate |
| Tenancy | One account, one list | Sub-accounts per brand, client, campaign or lead vendor — with isolated keys and reporting |
| Evidence | Result returned at query time | Timestamped, retained scrub records you can produce in discovery or a regulatory exam |
| Coverage control | Standard litigator + troll + DNC lists | Add your own internal suppression, revoked-consent and complaint files to the same call |
| Onboarding | Self-serve API keys | Solutions engineer, dialer integration, and a retroactive scrub of your existing database |
| Commercials | Fixed packages, monthly or annual | Negotiated volume agreement, MSA, DPA and security review |
The platform
Six things enterprise buyers actually evaluate us on. Every one of them is a question we expect on a security review, and every one has a documented answer.
Our Name Recognition Algorithm matches on the litigator, not just the number they used last time. When a serial filer rotates to a new prepaid line, the name still trips the flag — the failure mode that catches most number-only lists.
Single-record scrub returns in single-digit milliseconds so it can sit inline in the dialer without hurting connect rates. Batch throughput benchmarked at 790,000 records in 56 seconds.
Your own API cluster rather than a shared pool — no neighbour traffic, no rate ceiling, and capacity provisioned against your peak hour rather than your average.
Every scrub is logged with timestamp, list version and verdict, and retained on your schedule. When a demand letter arrives, the question "did you check before you called?" has a file behind it.
Sub-accounts, scoped API keys and per-segment reporting. Score lead vendors and publishers on the litigator density they deliver, and cut the ones poisoning your file.
Litigators, TCPA attorneys, demand-letter trolls, DNC complainers, federal DNC and your own internal suppression — resolved in a single request instead of five sequential ones.
Who we protect
Serial filers do not target randomly. They target the sectors where outbound volume is high, consent chains are long, and settlement is cheaper than litigation. Shares below reflect 2026 TCPA case distribution.
You are liable for calls you did not place, on consent you did not collect, from publishers you have never met.
One flagged dial by one agent on one client's campaign becomes your indemnity claim.
Your exposure is not only the class action — it is what the examiner asks for afterwards.
At your scale a class action is a headline before it is a line item, and legal owns the decision.
The offer
Send us a sample of your active list. We scrub it against the full registry and return a written report: how many known litigators, attorneys, trolls and DNC complainers are in it, broken out by source. No integration, no commitment, and the report is yours whether or not you buy anything.
100K to 1M records over encrypted transfer or SFTP. Phone and name columns are enough.
Against 600K+ litigator numbers, 100K+ names via NRA, and 260M troll and DNC records.
A written report with counts by category and by lead source, plus estimated statutory exposure.
A solutions engineer will follow up within one business day.
Procurement & integration
Enterprise deals stall in vendor risk, not in sales. We come to that meeting with the documentation already assembled.
MSA, DPA and mutual NDA. Negotiated volume agreement rather than a fixed package.
Encrypted in transit and at rest. Your uploaded suppression files stay yours and are never resold.
Dedicated cluster with an uptime commitment and a named escalation path, written into the agreement.
Assigned solutions engineer through integration, then a standing quarterly compliance review.
Drops into the stack you already run
Objections, answered
The short version of the conversation you would otherwise have three calls into the evaluation.
No. The federal DNC tells you who asked not to be called. It does not tell you who has filed eleven TCPA suits in the last two years and is waiting for your dial. Those are different populations, and the second one is the one that files. Serial litigators frequently keep numbers off the federal DNC precisely so calls come through.
Same registry, different product. Enterprise adds dedicated infrastructure without a shared rate ceiling, sub-account isolation per brand or client, retained scrub records built to be produced as evidence, your own suppression files resolved in the same call, and a negotiated commercial agreement instead of a fixed package. If a single account and a shared pool cover you, our standard plans are the better buy and we will tell you so.
Court filings and dockets from 2000 to the present, demand-letter activity, and complaint records — compiled and verified by a research team, with 500 to 1,000 new numbers added each month. Critically, we compile the numbers associated with a litigator, not only the number named in a given complaint, which is where number-only lists miss.
Yes — that is the design point. Single-record scrub returns in single-digit milliseconds on dedicated infrastructure, fast enough to run in the dial path rather than as an overnight batch. Most enterprise deployments run both: inline at dial time, plus a scheduled full-file rescrub as the registry updates.
Nothing, and it does not require an integration. You send a sample file, we return the findings in writing, and you keep the report regardless of what you decide. Most conversations start here because the number of litigators already sitting in an active list tends to end the debate faster than a deck does.
Suppression is one control, not a compliance programme. It removes known litigators, trolls and complainers from your file and creates a record that you checked — it does not replace consent capture, honouring revocation, calling-hour rules or counsel. We are a data and infrastructure vendor, not your law firm.
Two ways to start
Between 500 and 1,000 new litigator numbers enter the registry each month. Some of them are already in the file your dialer will load tomorrow morning.