Dispute or correct a number

Where our assessments come from

ScamVerify™ builds each assessment from public and licensed data, then has Ava, our AI analyst, explain it in plain English. The sources include:

• FTC and FCC consumer-complaint records filed against a number
• Carrier and line-type information, and caller-ID (CNAM) data
• Robocall and threat-intelligence databases
• Community reports submitted by people who received a call or message

These records attach to a phone number, not to a person. That is the heart of why an assessment can be out of date or about a previous holder.

Why an assessment can be wrong about you

Phone numbers move and get faked, so the current holder of a number is often not the person behind any past activity:

• Reassignment. Carriers recycle disconnected numbers to new customers. You can inherit a number that has an older complaint history that has nothing to do with you.
• Spoofing. Scammers can forge a number on caller ID without ever controlling the line. If your number is being spoofed, complaints can pile up against a number you own but never misused.

Both are exactly the situations the dispute process is built to fix.

How we verify - and why

We cannot change an assessment on someone's word alone - that would let a bad actor hide their own number. Instead we confirm who is actually asking:

• Control of the number. We send a one-time 6-digit code to the number itself, by text or by a voice call for a landline. Reading it back proves you control the line today. A spoofer who only forges your number cannot pass this; the real owner can.
• Business identity (for business claims). We also confirm your connection to the business - for example a code to an email on the business's domain, plus a cross-check against the number published on the official site - and a person reviews it.

Verifying control is what protects a reassigned or spoofed owner. It is the same step that keeps the process from being abused.

What we can and can't do

• We can re-weight stale complaints once you verify control, add context (for example, noting that the current holder has verified the number, or that the owner reports spoofing), and update the assessment to reflect the current holder.
• We don't delete the underlying public records. The FTC and FCC complaint records are factual and sourced, so we do not erase them. We change how the assessment weighs them - we do not pretend they never happened.
• Verified control is not a clean bill of health. It earns context, not a guarantee. A verified number is moved out of a high-risk verdict, but anyone checking it is still told to verify requests directly.

What we won't do

We do not change an assessment simply because someone disagrees with it. Corrections are based on verified facts - who controls the number, whether it was reassigned or spoofed, and what the underlying records actually show - not on disagreement. This keeps the process fair to the people the assessments are meant to protect.

Two ways to dispute

• In the app, with Ava (fastest). Tell Ava "this is my number," "this is my business," or "my number is being spoofed." She opens a case, verifies control with a one-time code, and either updates the assessment or escalates it to a person.
• Through our contact form. Businesses, representatives, or anyone making a formal request can use the contact form and choose the Legal category. Include the number, your relationship to it, and what is incorrect.

Timeline

We aim to resolve disputes within 5 business days. Legal requests are prioritized. We will tell you the outcome and the reasoning, and if new activity appears on a number later, the assessment is re-evaluated from current data.

It's free

We never charge to change, improve, or influence an assessment, and there is no way to pay for a better verdict. Corrections are based only on verified facts.

Learn more

For how we generate assessments and use data, see our Terms of Use and Privacy Policy. To start a dispute or ask a question, use the contact form (choose the Legal category for formal requests).