Skip to content

Security Independently confirmed2 publishers 3 min read Published Updated

FCC wants carriers scored on how often they block legitimate calls

The commission's notice asks for outcome metrics instead of compliance filings, including a count of wrongly blocked calls, while insisting it creates no new requirements and naming no data set that holds that number.

The Watch · Security desk

Send a correction

Illustration accompanying FCC wants carriers scored on how often they block legitimate calls
Generated illustration

What happened

  • The FCC said in a public notice Wednesday that it wants a scorecard letting consumers rate their telecom's ability to prevent unwanted robocalls, and that it intends to publish the results.
  • Coverage would be limited to domestic voice providers with retail customers, spanning wireless, wireline, VoIP and hybrid networks.
  • The FCC characterized the project as a consumer tool rather than a rulemaking, saying it will not result in new rules or requirements for voice service providers.

Why it matters

  • Who's exposed exposure A published per-provider false-positive rate would make blocking accuracy comparable between carriers, and give organizations whose legitimate calls get filtered a figure to cite instead of anecdotes.
  • What it limits constraint With no rulemaking behind it, the commission can only score what providers choose to hand over, so the column operators most want, the false-positive rate, is the one the FCC has the least power to require.
  • What it sets up precedent Hyun's DOT dashboard comparison points to a route regulators can take while their enforcement powers are contested: publish comparative outcomes and let public ranking do the work of a rule.
  • Who has to decide decision Scope is settled in this comment round, so any carrier that wants small and regional networks left out of the scoring has to make that argument now rather than after the first publication.

No federal system currently holds the metric that makes this notice worth reading. The FCC named five data sets it considers best suited to scoring providers: Robocall Mitigation Database filings, its own Consumer Complaints Center data, its enforcement action records, Industry Traceback Group data, and Federal Trade Commission complaints [5]. Three of the five are FCC-run; two come from outside the agency [14]. Each of them records a call that got through, a complaint about one, or the paperwork and enforcement around it. A record of a legitimate call wrongly blocked is a different kind of data point entirely, and none of the five capture it [15].

So the composite the FCC describes, operational practices plus measurable outcomes including how often legitimate calls are blocked [2], has one leg resting on data providers hold themselves. The agency also says this is not a rulemaking and will produce no new rules or requirements for voice service providers [11], which means a blocking-accuracy figure would arrive voluntarily [16]. The notice's own goals supply the lever: it wants the public guide to cover how transparent providers are with their metrics, and it does not prescribe technical systems for any of it [10]. A provider that declines to publish its false-positive rate becomes part of the score simply by declining.

The database removal process the scorecard is meant to move beyond still carries the harder consequence. The same day the notice appeared, the FCC removed 14 providers from the Robocall Mitigation Database after they failed to act on certifications the agency had flagged as out of compliance [6][8]. Removal effectively cuts a company off from connecting to US telecom networks, and FCC rules give other US providers two days to block all traffic from violators [7]. Chair Brendan Carr said the action pushes more than a dozen providers off US networks [9]. The scorecard's mechanism is comparison on a publishing schedule, not a cutoff date.

Peter Hyun, the FCC's former acting enforcement chief, endorsed the approach to CyberScoop and likened it to the Department of Transportation's 2024 airline customer service dashboard, saying that transparency "helped foster adoption of improved practices and a strong focus on better outcomes for consumers" [12][13]. Hyun also placed it in context, telling CyberScoop that with recent legal and policy fights over FCC enforcement, this is a creative effort to use other tools [13]. Set that next to the agency's insistence that no requirements follow, and the scorecard reads as pressure the commission can apply without defending a new rule.

For any organization whose outbound calls are the traffic being mislabeled, the useful output is narrow and specific: a per-provider false-positive rate, published, citable in a dispute. The notice asks for that number and leaves both the scope of who gets measured and the source of the count to the comment round [10][4].

What to watch

  • Comment deadlines, and whether large carriers argue for excluding small and regional networks from scoring.
  • Whether the final scorecard design keeps a provider-reported blocking-accuracy metric or falls back on complaint counts.
  • Whether other US providers actually block traffic from the 14 removed companies inside the two-day window.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence50
Adoption
Not scored
Hype gap+15
Incentives35
Confidence55
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    The FCC said in a Wednesday public notice that it wants to set up a new scorecard system allowing consumers to rate their telecoms' ability to prevent or deter unwanted robocalls, and that it intends to publish the results.

    Reported SupportedView cited source
  2. [2]

    The FCC said it wants more than "a simple administrative checklist," such as whether a provider offered the right tools or filed the right paperwork, but rather "a composite set of metrics that reflects both operational practices and measurable outcomes, including how often legitimate calls are blocked."

    Reported SupportedView cited source
  3. [3]

    The scorecard would apply only to domestic voice service providers with retail customers, including wireless, wireline, VoIP providers and hybrid networks.

    Reported SupportedView cited source
  4. [4]

    The FCC is seeking comment from the public on whether to focus on larger providers, exclude small or regional networks, and other questions around who would be evaluated.

    Reported SupportedView cited source
  5. [5]

    The notice flags data systems the agency believes would be "best" for evaluating companies: Robocall Mitigation Database filings, FCC Consumer Complaints Center data, and FCC enforcement action data, along with third-party or industry sources including Industry Traceback Group data and Federal Trade Commission complaint data.

    Reported SupportedView cited source
  6. [6]

    On the same day the scorecard was unveiled, the FCC announced it had removed 14 telecommunications providers from the Robocall Mitigation Database.

    Reported SupportedView cited source
  7. [7]

    Removing a company from the Robocall Mitigation Database effectively cuts it off from connecting to U.S. telecom networks, and FCC regulations give other U.S. providers two days to block all traffic coming from violators.

    Reported SupportedView cited source
  8. [8]

    According to the FCC, the 14 companies failed to take necessary steps when informed that their database certifications were out of compliance; the list includes Apps Communications, CFX Business Solutions, Conference America, Convergence Technology Solutions, CSB Technologies, Digital Division, Dixie Net Communications, HighComm, Inatech Solutions, makrodepot, Opex Communications, ReachME, SECURE, and SkyCom Healthcare.

    Reported SupportedView cited source
  9. [9]

    FCC Chair Brendan Carr said "Today's action pushes more than a dozen providers off of U.S. networks for failing to abide by our robocall rules."

    Reported Supported Source: FCC Chair Brendan CarrView cited source
  10. [10]

    The notice does not prescribe or define technical solutions or systems for the scorecard, instead laying out broad goals including a public guide for evaluating how well providers prevent robocalls and how transparent they are with their metrics.

    Reported SupportedView cited source
  11. [11]

    The FCC said it intends to publish the scorecard results but characterized the effort as a consumer tool and "not a rulemaking that will result in new rules or requirements for voice service providers."

    Reported SupportedView cited source
  12. [12]

    Peter Hyun, former acting head of enforcement at the FCC, endorsed the scorecard idea and likened it to the Department of Transportation's creation of an airline customer service dashboard in 2024.

    Reported Supported Source: Peter Hyun, former acting FCC enforcement chief, to CyberScoopView cited source
  13. [13]

    Hyun told CyberScoop by text that transparency "helped foster adoption of improved practices and a strong focus on better outcomes for consumers" and that "with recent legal and policy fights over FCC enforcement, this is a creative effort to use other tools to combat what is an ever-tormenting issue for consumers: illegal calls."

    Reported Supported Source: Peter Hyun to CyberScoopView cited source
  14. [14]

    Of the five data sources the notice names as best suited to evaluating providers, three are operated by the FCC (Robocall Mitigation Database filings, Consumer Complaints Center data, enforcement action data) and two come from outside the agency (Industry Traceback Group data, FTC complaint data).

    Derived Supported
  15. [15]

    None of the five data sources named in the notice is a record of legitimate calls that were blocked; they consist of compliance filings, consumer and FTC complaints about calls that connected, traceback data and enforcement actions.

    Derived Supported
  16. [16]

    Because the FCC says the scorecard creates no new rules or requirements, and no named federal data set holds a count of wrongly blocked calls, a per-provider false-positive rate would depend on voluntary disclosure by providers.

    Derived Insufficient

Sources

2 independent publishers whose own reporting we read for this story.

  1. cyberscoop.com

    1 article · September 2, 2026

    The FCC wants consumers to rate their telecom’s anti-robocall protections
  2. scworld.com

    1 article · September 3, 2026

    FCC proposes consumer scorecard for telecom robocall prevention efforts

Topics and entities

Topics

  • Robocall Mitigation
  • Telecom regulation

Entities