Best TCPA compliance software: scrubbing, reassigned numbers and calling rules
6 vendors compared10 checksVendor claims read 2026-10-22
For the owner or operations lead of a business that calls or texts customers and wants the checks done before anyone dials: do-not-call lists, litigators, reassigned numbers, line type, calling hours and the records that prove it. These are dedicated compliance tools, not texting apps or dialers. We read six vendors' own sites and documentation on 2026-10-22; every status names the page it came from.
Verdict by use case
Best overall
Contact Center Compliance (DNC.com)
Its public docs show every scrubbing row in this table, including a direct FCC reassigned-number query by consent date and calling windows with state overlays. Consent proof is the gap: pair it with a consent-capture tool.
Best for a small team checking lists
One lookup returns federal, state and DMA list status, litigator matches and line type, and a second queries the FCC reassigned-number database. It says plainly that calling hours and the internal list stay your job.
Best for enterprise rule enforcement
One pass-or-block answer per contact covers DNC lists, reassigned numbers, litigators, line type, calling windows and contact limits. The Compliance Hub keeps the evidence and exports it to GRC platforms.
Six tools, ten checks
The first three rows are the lists a caller must honour; the next three test the number itself; the last four cover hours, consent, records and timing. Most of these tools plug into the dialer or texting platform you already use, so read the table as the checks you add on top. "Our pick" marks the best-overall verdict.
| Requirement | Our pickContact Center Compliance (DNC.com) | Gryphon | PossibleNOW | RealPhoneValidation | Blacklist Alliance | ActiveProspect (TrustedForm) |
|---|---|---|---|---|---|---|
| Scrubs against the National DNC Registry | Yes | Yes | Yes | Yes | Yes | Yes |
| Scrubs state do-not-call lists | Yes | Yes | Yes | Yes | Yes | Yes |
| Keeps an internal do-not-call list for outbound calls | Yes | Check with the vendor | Yes | No | Yes | Yes |
| Screens numbers against a known-litigator list | Yes | Yes | Yes | Yes | Yes | Yes |
| Checks numbers against the FCC Reassigned Numbers Database | Yes | Yes | Yes | Yes | Check with the vendor | Yes |
| Identifies wireless, landline and VoIP numbers | Yes | Yes | Yes | Yes | Yes | Check with the vendor |
| Applies state calling-hour rules by the number's location | Yes | Yes | Yes | No | Check with the vendor | Check with the vendor |
| Captures web consent with a record of the sign-up session | Check with the vendor | Check with the vendor | Check with the vendor | No | Check with the vendor | Yes |
| Keeps a record of every check for audits | Yes | Yes | Yes | Yes | Check with the vendor | Check with the vendor |
| Checks numbers by API at the moment of contact | Yes | Yes | Yes | Yes | Yes | Yes |
- Scrubs against the National DNC Registry
- The safe harbor needs a registry copy obtained no more than 31 days before the call.47 CFR § 64.1200(c)(2)(i)(D)
- Scrubs state do-not-call lists
- Some states keep their own registries; Maine's law counts a number on the national or state registry for 3 months as off limits for sales calls.10 M.R.S. § 1499-B(6) (Maine)
- Keeps an internal do-not-call list for outbound calls
- Telemarketers must record a do-not-call request when it is made and honour it for five years.47 CFR § 64.1200(d)(3), (d)(6)
- Screens numbers against a known-litigator list
- No rule requires it and it earns no safe harbor; it lowers the odds of dialing people who sue often, and it never replaces consent.
- Checks numbers against the FCC Reassigned Numbers Database
- A database answer of "no" that turns out wrong is a safe harbor for a call to a number that changed hands after consent.47 CFR § 64.1200(m)
- Identifies wireless, landline and VoIP numbers
- Autodialed or prerecorded calls to a cell phone need the called party's prior express consent, so the line type decides which rule a number falls under.47 U.S.C. § 227(b)(1)(A)(iii)
- Applies state calling-hour rules by the number's location
- Some states set a narrower window than the federal 8 a.m. to 9 p.m.: Florida stops commercial solicitation calls at 8 p.m. in the called person's time zone.Fla. Stat. § 501.616(6)(a)
- Captures web consent with a record of the sign-up session
- Prior express written consent is a signed agreement naming the number; a session record shows what the person saw and clicked when they agreed.47 CFR § 64.1200(f)(9)
- Keeps a record of every check for audits
- The national DNC safe harbor holds only if the business maintains records documenting its scrub process.47 CFR § 64.1200(c)(2)(i)(D)
- Checks numbers by API at the moment of contact
- A list scrubbed weeks ago goes stale; a check when the call or text goes out uses the lists as they stand that day.
What each check proves
A clean result does not always mean the same thing. Two checks buy a safe harbor, three are plain duties, two are evidence, and the litigator screen protects nothing in law. Read the vendor table with this one beside it.
| Check | Rule | What it is | What a clean result gets you |
|---|---|---|---|
| National DNC scrub | 47 CFR § 64.1200(c)(2)(i) | Safe harbor | Protection for a call made in error, if all five parts are in place: written procedures, trained staff, a recorded internal list, a registry copy no more than 31 days old with records of the process, and registry data used only for compliance. |
| State DNC lists | State statutes, e.g. 10 M.R.S. § 1499-B(6) | Required | Compliance with the state's own list. Maine's defence copies the federal steps and adds a reassigned-number check before every telephone sales call. |
| Internal do-not-call list | 47 CFR § 64.1200(d)(3), (d)(6) | Required | A duty, not a shield: a request must be honoured within 10 business days and kept for 5 years. The list is also one of the safe harbor's five parts. |
| FCC reassigned-number query | 47 CFR § 64.1200(m) | Safe harbor | Protection for a call to a number that changed hands, only if you queried the FCC database with the consent date and it wrongly answered "no". |
| Litigator screen | No rule | Risk filter | Fewer calls to people who sue often. No legal protection: a call that breaks a rule is still a violation, whoever answers. |
| Line type (wireless or landline) | 47 U.S.C. § 227(b)(1)(A)(iii) | Evidence | Which numbers need prior express consent before an autodialed or prerecorded call. The flag proves nothing on its own. |
| Calling window | 47 CFR § 64.1200(c)(1); Fla. Stat. § 501.616(6)(a) | Required | No solicitation before 8 a.m. or after 9 p.m. at the called party's location, or the state's narrower window (Florida ends at 8 p.m.). |
| Consent record | 47 CFR § 64.1200(f)(9) | Evidence | The signed agreement, the number it covers and the disclosure the person saw. Consent is what makes an autodialed or prerecorded marketing call lawful, so the record has to be producible years later. |
Run the checks in order
The order matters because each step feeds the next: no consent date, no reassigned-number answer; no line type, no way to sort numbers for the dialer. The same sequence works with one vendor or three.
- 01
Store the consent date with every number
The reassigned-number safe harbor turns on a query made with the number and the date consent was obtained. A number with no consent date cannot get that answer, so the date belongs in the same row as the number, kept in a consent log or the tool that captured it (the Records guides and tools cover what that log holds).
- 02
Query the FCC database with that date
Five of the six tools document a reassigned-number check against the FCC database. Map the consent date into it: ActiveProspect's step looks back 90 days unless you do. Maine goes further and makes the check part of its telephone-solicitation law. The Reassigned Numbers Database guide covers the subscription and the three possible answers.
ActiveProspect: Reassigned Numbers Database query10 M.R.S. § 1499-B(6) (Maine)
- 03
Scrub national, state and internal lists in one pass
Use a registry copy no more than 31 days old on the day of the call, and keep the scrub receipt. State lists can carry conditions: Contact Center Compliance releases the Louisiana and Oklahoma lists only after proof of the caller's state telemarketer registration. More on the lists a seller keeps in Do Not Call rules for business.
47 CFR § 64.1200(c)(2)(i)(D)DNCScrub docs: Louisiana and Oklahoma registration
- 04
Screen litigators, then flag the line type
A litigator scrub is a business choice, not a rule. The line type is not optional in practice: a cell number needs prior express consent before an autodialed or prerecorded call, so the flag decides which numbers can go to the autodialer.
- 05
Check the clock when the call or text goes out
Calling windows depend on where the number is and on the day, so they are checked at the moment of contact, not when the list was scrubbed. Contact Center Compliance returns no window at all for a number it cannot place, and applies residential rules only. Test a time and state by hand with the quiet hours checker; the mini-TCPA state laws guide covers the stricter states.
- 06
Keep the receipts together
Scrub receipts, reassigned-number answers and consent records answer different questions in a dispute, and the DNC safe harbor holds only with records of the process. Keep them under one customer ID and walk the full list with the TCPA compliance checklist.
Vendor by vendor
Each card repeats the table's rows with the detail from the vendor's own page.
Contact Center Compliance (DNC.com)
What it is
A scrubbing platform (DNCScrub) with litigator, reassigned-number, line-type and calling-time checks, run by web upload, SFTP or a public REST API. DNC.com (Contact Center Compliance) and Blacklist Alliance are both part of Sonera, as each says on its own site (read 2026-10-22).
Who it fits
Call and text teams that want every list check and the legal calling window answered by one vendor, from a dialer or their own code.
- Scrubs against the National DNC RegistryYes
Federal and state lists in one scrub; you need your own Subscription Account Number from the FTC.
- Scrubs state do-not-call listsYes
Most state lists on every account. Louisiana and Oklahoma stay blocked until you send proof of the caller's state telemarketer registration.
- Keeps an internal do-not-call list for outbound callsYes
Internal list kept in the portal or by API, with a do-not-call policy editor.
- Screens numbers against a known-litigator listYes
Litigator Insights matches numbers against case files, by batch or REST API.
- Checks numbers against the FCC Reassigned Numbers DatabaseYes
RND Basic queries the FCC database with the number and the consent date. Reassigned Authority is a separate check built on carrier data.
- Identifies wireless, landline and VoIP numbersYes
Wireless ID and VoIP ID flags, plus a disconnect scrub.
- Applies state calling-hour rules by the number's locationYes
Returns each number's legal windows: a state curfew overlay first, the federal 8 a.m. to 9 p.m. otherwise. Residential rules only; B2B exemptions are not applied.
- Captures web consent with a record of the sign-up sessionCheck with the vendor
Express written consent can be stored as a Permission EBR record; the docs describe no recording of the sign-up session.
- Keeps a record of every check for auditsYes
User actions logged with source IP in audit reports, plus daily scrub summaries and cell-phone scrub history.
- Checks numbers by API at the moment of contactYes
One Full Scrub call covers the DNC lists, litigators, line type and calling-time rules; the reassigned check is a second call.
Gryphon
What it is
An enterprise compliance layer (Gryphon ONE) that certifies each call, text or email before it goes out, with a Compliance Hub that keeps the evidence behind every decision.
Who it fits
Large contact centres and regulated firms on Genesys, Salesforce, Pega, Google Cloud or NiCE that want one pass-or-block answer per contact.
- Scrubs against the National DNC RegistryYes
Federal and state DNC status checked before each contact.
- Scrubs state do-not-call listsYes
Named beside the federal registry in the real-time check.
- Keeps an internal do-not-call list for outbound callsCheck with the vendor
The integrations page lists checks against internal policies; an internal do-not-call list is not named.
- Screens numbers against a known-litigator listYes
Known litigators and professional plaintiffs blocked in real time; settings adjustable.
- Checks numbers against the FCC Reassigned Numbers DatabaseYes
Reassigned Number Database (RND) validation listed under TCPA and DNC compliance.
- Identifies wireless, landline and VoIP numbersYes
Wireless and ported number management.
- Applies state calling-hour rules by the number's locationYes
Enforces time zones, calling windows, contact limits and the TSR abandoned-call rate.
- Captures web consent with a record of the sign-up sessionCheck with the vendor
Consent and preference management keeps permissions in one place; a recording of the sign-up session is not described.
- Keeps a record of every check for auditsYes
Records each check, outcome and rule logic, and exports evidence to GRC platforms.
- Checks numbers by API at the moment of contactYes
REST API returns a pass-or-block decision before the call or text; API docs go to customers and qualified prospects.
PossibleNOW
What it is
DNCSolution for do-not-call scrubbing (with optional reassigned-number and litigator checks) and MyPreferences for consent and preference records. It also sells marketing data services.
Who it fits
Brands with branch or agent networks that need state rules, EBR exemptions and consent records managed centrally.
- Scrubs against the National DNC RegistryYes
Federal, state, wireless and company-specific lists, in bulk or one number at a time.
- Scrubs state do-not-call listsYes
State lists sit beside the federal, wireless and company lists in the same scrub.
- Keeps an internal do-not-call list for outbound callsYes
Company list with date stamps, upload receipts and scrub history, plus a policy wizard.
- Screens numbers against a known-litigator listYes
Optional Known Litigator List built from US federal court records.
- Checks numbers against the FCC Reassigned Numbers DatabaseYes
Optional; the reassigned-number exclusion runs inside the bulk scrub.
- Identifies wireless, landline and VoIP numbersYes
Classification services identify wireless, landline and VoIP numbers.
- Applies state calling-hour rules by the number's locationYes
Web services apply call curfews, holidays and state-of-emergency rules; a whole state can be suppressed.
- Captures web consent with a record of the sign-up sessionCheck with the vendor
Wireless e-Signature collects express written consent and MyPreferences keeps the consent language, date, time and source; a session replay is not described.
- Keeps a record of every check for auditsYes
Number Research shows the history and audit trail of any number or scrubbed list.
- Checks numbers by API at the moment of contactYes
Bulk scrubbing APIs, web services, SFTP and an agent quick check.
RealPhoneValidation
What it is
Phone-number lookups from RealValidation: a DNC Lookup that also returns litigator and line-type results, an FCC reassigned-number lookup, and validity checks, by batch file or API.
Who it fits
Small teams that want clean lists before a campaign and will run hours and the internal list themselves.
- Scrubs against the National DNC RegistryYes
National registry data updated daily; you enter your Subscription Account Number first.
- Scrubs state do-not-call listsYes
All state lists, plus the DMA's Telephone Preference Service.
- Keeps an internal do-not-call list for outbound callsNo
Its own checklist marks the internal list as caller-maintained.
- Screens numbers against a known-litigator listYes
A known-litigator scrub comes with DNC Lookup.
- Checks numbers against the FCC Reassigned Numbers DatabaseYes
Queries the FCC database with a number and the last consent date; answers yes, no or no data.
- Identifies wireless, landline and VoIP numbersYes
DNC Lookup returns the phone type: landline, VoIP or wireless.
- Applies state calling-hour rules by the number's locationNo
Consent and calling-time rules are marked as the caller's responsibility.
- Captures web consent with a record of the sign-up sessionNo
Consent sits in the caller's layer of its checklist.
- Keeps a record of every check for auditsYes
Compliance checks kept under a 4-year retention.
- Checks numbers by API at the moment of contactYes
A real-time API at the point of entry, or batch files returned by email.
Blacklist Alliance
What it is
A litigation-risk screen (the Litigation Firewall) with DNC scrubbing and line-type data, by API or batch.
Who it fits
High-volume callers and texters whose main worry is serial plaintiffs, and who want the risk threshold adjustable.
- Scrubs against the National DNC RegistryYes
Reports or suppresses registry numbers in the area codes your own registry subscription covers.
- Scrubs state do-not-call listsYes
The home page says all state lists; the Litigation Firewall page says select state registries. Confirm the states you call.
- Keeps an internal do-not-call list for outbound callsYes
The Litigation Firewall also scrubs your internal list.
- Screens numbers against a known-litigator listYes
Researchers review TCPA lawsuits; risk feeds are graded by an accuracy-versus-risk score you switch on or off.
- Checks numbers against the FCC Reassigned Numbers DatabaseCheck with the vendor
- Identifies wireless, landline and VoIP numbersYes
Carrier, line type and ported status by API.
- Applies state calling-hour rules by the number's locationCheck with the vendor
Tracks state laws such as Florida's FTSA; calling-hour enforcement is not described.
- Captures web consent with a record of the sign-up sessionCheck with the vendor
The home page says consent and call outcomes are documented; how is not described.
- Keeps a record of every check for auditsCheck with the vendor
Scrub statistics by day, month or in real time; a per-check audit export is not described.
- Checks numbers by API at the moment of contactYes
Real-time API inside a dialer or platform, or batch lists.
ActiveProspect (TrustedForm)
What it is
TrustedForm certifies web consent with a session replay; LeadConduit runs checks on each lead in real time, some built in and some as add-ons from other vendors. Jornaya is now part of ActiveProspect (read 2026-10-22): jornaya.com redirects to InfutorData, which describes itself as a division of ActiveProspect.
Who it fits
Businesses that collect consent on web forms and want the proof and the scrub in one lead flow.
- Scrubs against the National DNC RegistryYes
Through the Contact Center Compliance add-on in LeadConduit; needs a dnc.com account.
- Scrubs state do-not-call listsYes
Same add-on: national and state lists.
- Keeps an internal do-not-call list for outbound callsYes
SuppressionList checks leads against your own do-not-call or opt-out lists.
- Screens numbers against a known-litigator listYes
Add-ons from Blacklist Alliance and Contact Center Compliance.
- Checks numbers against the FCC Reassigned Numbers DatabaseYes
Queries the FCC database; you buy your own RND subscription. The look-back defaults to 90 days unless you map the consent date.
- Identifies wireless, landline and VoIP numbersCheck with the vendor
- Applies state calling-hour rules by the number's locationCheck with the vendor
The dnc.com add-on appends calling-window data; acting on it is a rule you set in the flow.
- Captures web consent with a record of the sign-up sessionYes
Session replay rebuilds the page with every click and keystroke; retained certificates are kept 5 years by default.
- Keeps a record of every check for auditsCheck with the vendor
Certificates are the consent record; a log of every scrub is not described.
- Checks numbers by API at the moment of contactYes
Retain API for certificates; LeadConduit runs each check as a step as the lead arrives.
How we read the claims
Questions buyers ask
Does a small business need TCPA compliance software?
It needs the checks, not necessarily a platform. The FCC's do-not-call and calling-hour rules apply to telemarketing texts to cell phones as well as calls (47 CFR § 64.1200(e)), and the national DNC safe harbor asks for a registry copy no more than 31 days old plus records of the process. A team sending a few campaigns a month can run its list through a lookup service before each send; a team calling all day needs the check inside the dialer.
Does a vendor's reassigned-number check give me the FCC safe harbor?
Only if it is a query of the FCC's Reassigned Numbers Database made with the date consent was obtained, and the database wrongly answered "no" (47 CFR § 64.1200(m)). A score built from carrier data is a different product: Contact Center Compliance sells both and documents them separately. ActiveProspect's database step looks back 90 days by default, so map the consent date into it.
Is a litigator scrub required?
No rule we read requires one, and it earns no safe harbor. It lowers the chance of dialing someone who sues often; the call still needs consent and a clean DNC result. Statutory damages stay at $500 per call or text, up to three times that ($1,500) if the court finds the violation willful or knowing.
How often should a calling list be scrubbed?
Against the national registry, with a copy no more than 31 days old on the day of the call. Internal do-not-call requests must be honoured within 10 business days and kept for 5 years. Checking at the moment of contact by API meets both without a schedule; a batch scrub needs one.
Which of these tools keep proof of consent?
ActiveProspect's TrustedForm records the sign-up session as a replay; a certificate expires 3 days after creation unless the form was submitted (then 90 days), and once retained it is kept 5 years by default. Contact Center Compliance can store express written consent as a Permission EBR record, and PossibleNOW's MyPreferences keeps consent language, date, time and source. Consent-certificate tools are compared side by side on our consent capture page.
Sources
- 47 CFR § 64.1200(c)(2)(i)(D)fetched 2026-10-22
- 10 M.R.S. § 1499-B(6) (Maine)fetched 2026-10-22
- 47 U.S.C. § 227(b)(1)(A)(iii)fetched 2026-10-22
- Fla. Stat. § 501.616(6)(a)fetched 2026-10-22
- ActiveProspect: Certificate expiration and retention windowfetched 2026-10-22
- DNCScrub docs: EBR and Consent Masterfetched 2026-10-22
- PossibleNOW: Consent Management Platformfetched 2026-10-22
- DNC.com: DNCScrubfetched 2026-10-22
- DNCScrub docs: Louisiana and Oklahoma registrationfetched 2026-10-22
- DNC.com: Litigator Insightsfetched 2026-10-22
- DNCScrub docs: RND Basic APIfetched 2026-10-22
- DNCScrub docs: Legal call times for datefetched 2026-10-22
- DNCScrub docs: Full Scrub API overviewfetched 2026-10-22
- Gryphon: Integrations and APIfetched 2026-10-22
- Gryphon: Compliancefetched 2026-10-22
- Gryphon: Compliance Hubfetched 2026-10-22
- PossibleNOW: DNCSolution Do Not Callfetched 2026-10-22
- PossibleNOW: TCPA Litigator Listfetched 2026-10-22
- PossibleNOW: DNCSolution 3.0fetched 2026-10-22
- PossibleNOW: Marketing Data Servicesfetched 2026-10-22
- RealPhoneValidation: Do Not Call list scrubbingfetched 2026-10-22
- RealPhoneValidation: TCPA compliance solutionsfetched 2026-10-22
- RealPhoneValidation: Reassigned Numbers Database lookupfetched 2026-10-22
- Blacklist Alliance: Data Optimizationfetched 2026-10-22
- Blacklist Alliance: TCPA and DNC compliancefetched 2026-10-22
- Blacklist Alliance: Litigation Firewallfetched 2026-10-22
- ActiveProspect: Contact Center Compliance dnc.com add-onfetched 2026-10-22
- ActiveProspect: Overview of SuppressionListfetched 2026-10-22
- ActiveProspect: Blacklist Alliance add-onsfetched 2026-10-22
- ActiveProspect: Reassigned Numbers Database queryfetched 2026-10-22
- ActiveProspect: TrustedForm session replayfetched 2026-10-22
- ActiveProspect: Retain API operationfetched 2026-10-22