Phone Compliance Before the Dial: What a TCPA Check Should Report

A phone number TCPA check is a screen you run on a US number before a rep dials it. A complete check reports four things: the line type, every federal and state Do Not Call list the number sits on, whether the number matches a known TCPA litigator, and whether it belongs to a known complainer. It reports what it found. It does not tell you whether to dial, because no check can know your consent history or your state-law obligations. That last sentence is the whole point of this post. A "DNC scrub" that hands back a green tick is hiding the checks it skipped, and the checks it skipped are where the $500-per-call lawsuits live.

Key takeaways

• Four checks, reported by name. Line type, federal and state DNC hits, TCPA-litigator match, known-complainer status. If a tool reports fewer, ask which ones it left out.
• A check reports; it never rules. Consent, established business relationships and state calling rules sit outside the data. A tool that says "safe" is guessing about you.
• An incomplete check is not a pass. When one check cannot complete, the row should say so and stay gray. Never clear.
• Freshness has a legal definition. The federal safe harbor requires a DNC registry version no more than 31 days old.

Why the check matters before the dial

The Telephone Consumer Protection Act is the reason phone compliance is a numbers game and not a judgment call. Under 47 U.S.C. § 227, a person can recover actual loss or $500 for each violation, whichever is greater. A court can raise that to three times the amount, $1,500 per call, for a violation it finds willful or knowing. There is no cap. The math on a campaign of a few hundred dials is not hard.

The registry itself keeps growing. The FTC's Do Not Call data book for fiscal year 2025 reports over 258 million active registrations and over 2.6 million Do Not Call complaints in the year. That is the population your reps are dialing into. Whether your B2B outreach is even covered is a question with a longer answer, which our TCPA compliance guide for sales teams walks through; the short version is that "we sell to businesses" is not the exemption people think it is, because a mobile number is a mobile number regardless of who answers it.

So the check has to run before the dial, per number. The result has to be readable by the rep in the two seconds before they pick up the phone. Here is what it has to contain.

The four things a complete check reports

1. Line type

Is the number a landline, a mobile or a VoIP line? This is the first field because the rules split on it. Calls and texts to mobile numbers carry the strictest consent requirements in the statute. A rep who knows the line is a mobile can decide to dial by hand, which is what our campaign classification is for. A rep who does not know cannot make that decision.

2. Federal and state Do Not Call hits, by list

The federal registry is one list. Most states keep their own, several with different rules on what counts as a solicitation, which our guide to state mini-TCPA laws covers. A check that says "on DNC" without naming which list is giving you half a fact. The report should name every list the number hit.

Freshness is part of this check. The FCC's rules at 47 CFR § 64.1200(c)(2) say a registration on the national registry must be honored indefinitely, and the safe harbor for an accidental call requires, among other things, that you used a version of the registry obtained no more than 31 days before the call. A DNC scrub from last quarter is not a scrub. The check should be run at the time of use, and the report should carry the date it ran.

3. TCPA-litigator match

Some people file TCPA suits as a practice. A number that matches a known TCPA litigator is not illegal to call, but a rep should know before dialing that a mistake on this number is likelier to end in a complaint than a hang-up. Most "DNC scrub" services do not run this check, because it is not a DNC question. It is a risk question, and it belongs in the same report.

4. Known-complainer status

Separate from the litigators are the people who file Do Not Call complaints with regulators. Those 2.6 million complaints in FY2025 came from somewhere. A number tied to a known complainer means the margin for error on this dial is thin.

What a check must never say

Everything above is data. Here is what is not in the data: whether this person gave you prior express consent, whether you have an established business relationship with them, whether they asked your company to stop calling last year, and what your state's calling hours and disclosure rules require of you today. All of that lives in your CRM, your internal Do Not Call list and your counsel's memo. None of it is visible to a number lookup.

That is why a check that stamps a number "safe" is making a claim it cannot support. The number could be clean on every list and still be someone who told your rep to stop calling in March. The rules at 47 CFR § 64.1200(d) require you to honor that kind of request within ten business days and keep it on your own list, which is a separate discipline our post on managing an internal Do Not Call list covers. No vendor can see that list for you.

The right output is a report of the checks that ran, per number, in words a rep can act on: line type named, each DNC list hit named, litigator match yes or no, complainer status yes or no, with the date. Then the decision to dial belongs to a person who also knows the consent history. That is the honest boundary of what a lookup knows.

The incomplete check rule

Lookups fail. A state list is unreachable for an hour, a number is malformed, a source times out. What the tool does in that moment tells you whether to trust it.

An incomplete check must never be shown as clear. The row should say "one or more checks could not be completed" and stay visibly unresolved, and every exported row should carry a note that this is not a complete compliance determination. A tool that defaults a failed lookup to green has decided that your reps should dial a number nobody checked, and it has hidden that decision behind a color.

The same honesty applies to reassigned numbers. A number your customer gave you two years ago may belong to a stranger today. The FCC's Reassigned Numbers Database safe harbor at § 64.1200(m) protects callers who query that database before calling a number they once had consent for. That is a different check, and a four-check TCPA report should not pretend to replace it.

How AvairAI's Phone TCPA Check reports

We built Phone TCPA Check around exactly this spec, as one of the four standalone Tools that run without a campaign. Give it a US number, or on paid plans a CSV of up to 200. For each unique valid number it reports the line type, federal and state Do Not Call hits, whether the number matches a known TCPA litigator, and known-complainer status. It costs 2 credits per unique valid number, drawn from the Tools credits included in every plan, and invalid or duplicate rows cost nothing.

It reports the checks it ran and does not issue a calling verdict. When one or more checks could not be completed, the row says so and is never shown as clear. Every export carries the note that this is not a complete compliance determination: consent and state-law obligations stay with you.

Inside a campaign, the same screening runs on every contact before a call task reaches a rep. The standalone check is for the numbers that come from somewhere else: a list a rep built, an event export, the phone column in a CRM nobody has scrubbed since it was imported.

Frequently asked questions

What is a phone number TCPA check?

A screen run on a US phone number before a rep dials it. A complete check reports the line type, every federal and state Do Not Call list the number sits on, whether the number matches a known TCPA litigator, and known-complainer status. It reports what it found and does not issue a calling verdict, because consent history and state-law obligations are not visible to a number lookup.

What is a DNC scrub, and is it enough?

A DNC scrub compares a list of numbers against the national Do Not Call registry and removes or flags the matches. It is one of the four checks a complete TCPA screen runs, not the whole screen. A scrub does not report line type, litigator matches or complainer status, and it cannot see your consent records or your internal Do Not Call list.

How often does a Do Not Call list need to be checked?

At the time of use. The federal safe harbor in 47 CFR § 64.1200(c)(2) requires that you used a version of the national registry obtained no more than 31 days before the call, and a registration must be honored indefinitely. A scrub run last quarter does not meet that standard.

What should a TCPA check do when it cannot complete?

Say so, and stay unresolved. The row should read "one or more checks could not be completed" and never be shown as clear, and any export should note that the result is not a complete compliance determination. Defaulting a failed lookup to a pass is the failure mode to screen a vendor for.

Does a clean TCPA check mean I can dial the number?

No. A clean report means the number was not found on the lists checked and did not match a known litigator or complainer. It says nothing about whether the person gave you consent, whether they asked your company to stop calling or what your state's rules require. That decision belongs to the person dialing, with the report in front of them.

Ask the vendor which checks it skipped

If you are evaluating a phone compliance tool, ask for a sample report and count the checks. Four, named and dated, with a visible state for the ones that failed. If the report is a single color per row, ask what it does when a lookup fails.

Then run the numbers your reps are dialing this week through Phone TCPA Check. You will get the four checks, by name, per number. The decision stays where it belongs: with a rep who also knows what your CRM says. Compliance built in is not the same as compliance decided for you. We only claim the first.