Spam Calls and Robocalls: Why “Potential Spam” Still Interrupts Users

Evaluation scope

PRIMARY CURRENT SYSTEMS
• Spectrum Mobile Call Guard: reputation scoring, Potential Spam labeling, malicious-call blocking, and user control over what happens after classification.
• Apple iPhone Phone: Ask Reason for Calling, Silence Unknown Callers, Call Blocking & Identification, carrier-identified spam filtering, defaults, adversarial resilience, and recovery from false positives.

HISTORICAL / CURRENT COMPARATOR
• Verizon Call Filter / Call Filter Plus: contributor's historical carrier context plus current documented controls. Current Verizon materials describe selectable auto-blocking by spam-risk level and voicemail/termination routing. The contributor's historical experience is not assumed to reflect the current implementation.

BETTER-PRACTICE / FEASIBILITY COMPARATORS
• AT&T ActiveArmor: allow, block, or send Spam Risk calls to voicemail.
• T-Mobile Scam Shield: optional network-level Scam Block for Scam Likely calls with an explicit wanted-call warning.
• Google Phone: optional Filter spam calls control, reviewable call history/voicemail, and Not spam correction.
• Samsung Smart Call: user choice between blocking all identified spam/scam calls or only high-risk scam calls.
These comparators show that user-selected action on a risk classification is already implemented in major phone/carrier ecosystems.

SYSTEM CONTEXT
FTC/FCC consumer protection and robocall-mitigation material; Do Not Call limitations; STIR/SHAKEN caller-ID authentication; caller-reputation analytics; Industry Traceback Group activity; public community reports; industry surveys; academic robocall research; consumer-advocacy benchmarks; legitimate-caller false-positive recovery; and adversarial adaptation to filtering/screening.

COMMON SEARCH / USER TERMINOLOGY
spam calls; spam phone calls; robocalls; scam calls; nuisance calls; telemarketing calls; unwanted calls; telephone spam; voice spam; spam call blocker; robocall blocker; spam call blocking; call filtering; call blocking; call screening; Potential Spam; calls labeled Potential Spam; Potential Spam still rings; Potential Spam calls still ring; why does Potential Spam still ring; why do spam calls still ring; Suspected Spam; Spam Risk; Scam Likely; caller ID spam; caller ID spoofing; neighbor spoofing; local number spoofing; same area code spam calls; spoofed local calls; unknown callers; Silence Unknown Callers; Silence Junk Callers; Silence Junk Callers not working; Ask Reason for Calling; call screening bypass; robocalls getting through call screening; spam calls bypassing call screening; Call Guard; Call Filter; Call Filter Plus; Call Filter doesn't work; Scam Shield; Scam Shield doesn't work; Scam Block; ActiveArmor; Filter spam calls; block all spam and scam calls; block high-risk scam calls; send spam to voicemail; spam voicemail; unwanted voicemail; caller reputation; reputation-based blocking; false positive; false negative; legitimate call marked spam; legitimate calls blocked; missed legitimate calls; missed business call because of spam; spam calls after changing phone number; spam calls after switching carriers; paid spam blocker; spam blocker not working; spam calls every day; 5-10 spam calls a day; Do Not Call Registry; donotcall.gov; STIR/SHAKEN; caller ID authentication; robocall mitigation; spam call quarantine; why won't spam calls stop.

Question being evaluated

When a mobile carrier or phone platform has already classified an incoming call as suspicious, does the system let the subscriber choose the post-classification disposition of that category—such as ring, screen, silence, voicemail, quarantine or block—while making false-positive risk explicit and recoverable? Or does classification without actionable control leave the user to absorb repeated interruption, triage and trust costs, encouraging broader defensive avoidance of unfamiliar calls and making legitimate first-contact callers collateral damage?

Current findings

What works well or deserves recognition

Spectrum Mobile provides Call Guard without a separate charge and documents reputation scoring that can completely block its highest-risk known malicious category while labeling other suspicious calls. Apple provides multiple call-screening and unknown-caller options, including Ask Reason for Calling and Silence, and documents carrier-identified spam filtering on supported configurations.

Current competitor and platform controls strongly support feasibility of the requested reform. Verizon documents user-selectable spam-risk blocking up to All spam calls plus voicemail or call termination. AT&T ActiveArmor documents allow/block/voicemail choices for Spam Risk calls. T-Mobile Scam Shield documents optional network-level Scam Block with a warning that wanted calls may be blocked. Google Phone documents an optional Filter spam calls control, keeps filtered calls reviewable, preserves voicemail access, and supports Not spam correction. Samsung Smart Call documents a choice between blocking all identified spam/scam calls and blocking only high-risk scam calls.

These implementations demonstrate that the false-positive tradeoff does not have to be made entirely by the provider. A subscriber can be warned, choose an aggressiveness level, accept the risk, and retain recovery/review mechanisms. Public reports also include users who say Apple screening and carrier filters work extremely well, which is preserved as counterevidence against a universal-failure claim.

Difficulties and opportunities to improve

Spectrum's current documentation states that -2 and -3 calls are labeled Potential Spam and presented to the user, while only -4 known malicious calls are blocked. The contributor and public community reports describe classified or suspected spam continuing to create ringing, vibration or other interruption, leaving the subscriber with recurring attention switching and triage after the system has already identified elevated risk. The contributor's current Spectrum/iPhone screenshots do not show a visible carrier Spam suppression control on the screens reviewed, despite Apple documentation describing such a control when supported.

The contributor reports years of settings changes, support calls, Do Not Call registration, paid carrier filtering, paid third-party apps, a number change and Apple screening without durable relief. The burden is not limited to missed calls: it includes repeated interruption, manual classification, decision labor, support/configuration work, mitigation spending and reduced trust in unfamiliar and local-looking caller ID. In this contributor's case, that reduced trust has also contributed to missed legitimate business calls.

HXR treats avoidance of unfamiliar calls as potentially adaptive behavior under repeated unwanted-call exposure, not simply as user error. The current causal chain has different evidence strengths: Spectrum documentation establishes labeling/presentation policy; contributor and community evidence supports continued interruption and repeated triage; industry survey evidence supports unknown-call avoidance; and academic research plus the connected Incident support legitimate first-contact calls becoming collateral damage. These sources corroborate a pattern but do not establish population prevalence or one technical cause.

Mixed findings and limits

False positives are a real system risk: legitimate healthcare, financial, business, government, delivery, school, family and first-contact callers can be mislabeled or blocked. Stronger filtering therefore should not be framed as mandatory universal blocking. User choice, clear warnings, allowlists, voicemail, reviewable quarantine, one-tap Not Spam correction and durable recovery are central to the proposed reform.

The evidence also shows a continuing adversarial system rather than a one-time engineering problem. Community accounts describe rotating caller IDs, local-number spoofing, label changes and screening bypass or adaptation. Academic robocall work studies adversarial screening and user-defined call acceptance policies. STIR/SHAKEN improves caller-ID authentication but does not itself determine whether a call is wanted or trustworthy.

Public outcomes remain heterogeneous: some users report excellent results from Apple Ask Reason for Calling, Verizon Call Filter, carrier spam blocking or other protections, and Spectrum received strong marks in U.S. PIRG's broader carrier-protection review. HXR therefore treats broader voice-channel trust erosion as an evidence-backed pattern and risk under study, not as a prevalence claim or a conclusion that voice telephony generally has failed. The narrower mechanism remains whether subscribers can control what happens after a call is already classified as suspicious.

Organization information and response status

No organization has responded to HXR about this evaluation. Spectrum, Apple and Verizon public documentation is treated as organization-authored evidence, not as a response to the HXR findings. The contributor reports repeated historical support interactions with all three organizations, but those records are not yet independently preserved in this evaluation.

How HXR would test performance

A carrier/phone combination passes the proposed benchmark when the subscriber can set a clearly explained, persistent post-classification disposition for calls the system already marks as Potential Spam, Spam Risk, Scam Likely or an equivalent suspicious category. The implementation may offer silence, voicemail/quarantine, blocking or other user-selected handling; at minimum, a user-selected non-interruptive mode must prevent ring, haptic and interruptive incoming-call banners while keeping the call reviewable. Unknown calls that are not classified as suspicious should continue to follow the user's separate unknown-caller setting. Known or allowlisted callers and numbers corrected as Not Spam must be restored. Before stronger suppression is enabled, the system must explain false-positive risk and provide practical review and recovery. A screening response alone should not automatically override an existing high-risk classification or an explicit user suppression preference. HXR should verify both spam-suppression performance and legitimate-call reachability. A control named “Silence Potential Spam” is one possible implementation, not the only acceptable design.

Evidence coverage and limits

DIRECT HXR / CONTRIBUTOR EVIDENCE
Current iPhone settings screenshots document call-screening and filtering configuration; contributor testimony documents multi-year recurrence, cross-carrier experience, multiple phone numbers, paid mitigation, support history, screening adaptation, local-looking caller distrust, and missed legitimate business calls. Historical billing/support records have not yet been collected, so the exact paid Verizon product, historical price, and dates remain contributor-reported.

OFFICIAL ORGANIZATION EVIDENCE
Spectrum Call Guard documentation establishes that -2/-3 calls are labeled Potential Spam and presented while -4 known malicious callers are blocked. Apple documents Ask Reason for Calling, Silence, and provider-identified Spam filtering. Current Verizon documentation establishes selectable risk-level blocking plus voicemail/terminate routing. AT&T ActiveArmor establishes allow/block/voicemail control for Spam Risk calls. T-Mobile Scam Shield establishes opt-in network-level Scam Likely blocking and explicitly warns that wanted calls may be blocked. Google Phone establishes a Filter spam calls control with review/correction paths. Samsung Smart Call establishes user-selectable all-spam versus high-risk-only blocking.

GOVERNMENT / PUBLIC RECORD CONTEXT
FTC and FCC sources establish Do Not Call limitations, spam/scam labeling, spoofing, complaint scale, blocking-versus-labeling distinctions, false-positive recovery concerns, and ongoing robocall-mitigation work. FTC's FY2025 data reports more than 258 million active Do Not Call registrations and more than 2.6 million complaints while explicitly cautioning that complaints are unverified and are not a prevalence survey.

ACADEMIC / TECHNICAL RESEARCH
USENIX Security research on UCBlocker explicitly describes the problem in which users ignore or block unknown callers to avoid spam and consequently miss legitimate new callers, then proposes user-defined call acceptance policies. RoboHalt research treats avoiding unwanted interruption as a design goal by vetting unknown calls before ringing the user and includes adversarial testing. NC State / Robocall Science research documents adaptation to STIR/SHAKEN and other mitigations.

PUBLIC COMMUNITY PATTERN CORROBORATION
Reddit, Verizon Community, Spectrum Community, Xfinity Community, Google Voice Community, Apple/iOS discussions, and other technology forums contain materially similar accounts over multiple years: Potential Spam still rings; Silence Junk Callers appears ineffective in some configurations; 5–10 or more spam calls per day; rotating/spoofed numbers; paid-filter dissatisfaction; spam after carrier/number changes; call-screening bypass; and legitimate-call false positives. Community reports corroborate patterns but do not establish national prevalence or the truth of every individual interpretation.

FACEBOOK COMMUNITY ARTIFACT — OCTOBER 1, 2026
Contributor-supplied screenshots of a public HuffPost Facebook thread provide unusually direct corroboration of the evaluation's core distinction. One commenter reports 6–12 spam calls every day and objects that calls marked as spam still ring and still require checking. Another says spam labeling did not reduce call frequency and the phone still vibrated. Other comments include “they still call,” a preference for preventing the call from coming through at all, and a positive report that the setting works well. HXR treats this as anecdotal pattern corroboration with built-in counterevidence, not prevalence measurement.

INDUSTRY / MARKET CONTEXT
Hiya's State of the Call 2026 reports that most unknown calls go unanswered in its multinational survey and describes eroding voice-channel trust. Truecaller's 2022 U.S. Harris Poll reported substantial unknown-call avoidance and missed legitimate calls. YouMail estimated about 4.3 billion U.S. robocalls in July 2026. USTelecom describes analytics-based blocking/labeling, STIR/SHAKEN, and traceback as parallel mitigation layers. TNS reports high STIR/SHAKEN coverage among top providers but much lower coverage among non-tier-1 origins. These are commercial/industry sources and are labeled accordingly.

CONSUMER-ADVOCACY COUNTERPOINT
U.S. PIRG's 2025 carrier-protection review gave Charter/Spectrum an A for services and an A overall. HXR therefore does not characterize Spectrum as generally weak at robocall protection; the present question is narrower: whether subscribers receive actionable control over an already-detected Potential Spam category.

KEY LIMITATIONS
HXR does not currently claim that every phone user experiences the contributor's 5–10 unwanted calls per day; that every spam label is correct; that carriers deliberately allow spam to profit from mitigation products; that any single carrier/platform can independently eliminate illegal unwanted calling; or that community descriptions of attacker adaptation establish the underlying technical mechanism.

Connected HXR Incident reports

• Supports: HXR-2026-0929-0001 — Spam Calls and “Potential Spam” Labels Trained a Business Owner to Ignore Legitimate Calls

1 public HXR Incident report is connected to this Evaluation. Canonical roles: 1 supports; 0 partially supports; 0 narrows; 0 context only; 0 challenges. Connections are not votes and do not establish prevalence.

Next observation or verification

EVIDENCE NEXT STEPS
• Preserve a direct example of a call visibly labeled Potential Spam or equivalent that still produces an interruption on the current Spectrum/iPhone configuration.
• Collect several days of call-log counts with personal numbers redacted and distinguish labeled spam, suspected/unlabeled spam, unknown/uncertain calls, and known legitimate calls.
• Identify the historical Verizon paid-filter product and dates from billing/email records if available.
• Test whether any Spectrum-side or iOS control can suppress only the carrier's Potential Spam category without silencing all unknown callers.
• Where practical, compare the same acceptance test against current Verizon Call Filter, AT&T ActiveArmor, T-Mobile Scam Shield, Google Phone, and Samsung Smart Call.

OUTREACH / LINK CANDIDATES — RESEARCHED, NOT CONTACTED
Responsible/platform organizations: Spectrum Mobile / Charter Communications; Apple; Verizon; AT&T; T-Mobile; Google Phone / Pixel; Samsung.
Call-reputation / mitigation ecosystem: Hiya; YouMail; Truecaller; Transaction Network Services (TNS); First Orion; RoboKiller / Teltech; Nomorobo; USTelecom / Industry Traceback Group; CTIA; ATIS / SIP Forum.
Consumer advocacy / public-interest: U.S. PIRG; Consumer Reports; AARP Fraud Watch Network; National Consumer Law Center; Public Knowledge; Consumer Federation of America.
Government / policy audiences: FCC Consumer & Governmental Affairs Bureau / Robocall Response Team; FTC Do Not Call / unwanted-calls program.
Academic researchers: NC State Robocall Science / Brad Reaves and collaborators; UCBlocker authors (Virginia Tech and collaborators); RoboHalt authors (University of Georgia / Georgia Tech and collaborators).
Communities for evidence solicitation after publication and subject to self-promotion rules: Reddit r/iphone, r/ios, r/SpectrumMobile, r/verizon, r/tmobile, r/ATT, r/scams, r/GooglePixel, r/GoogleVoice; Apple Support Communities; Spectrum Community; Verizon Community; Xfinity Community; Google Voice Community.
Facebook: public web indexing did not expose enough reliable group-level results to name specific groups responsibly. Before outreach, verify current iPhone, carrier-customer, small-business, consumer-fraud/scam, and local community/business groups inside Facebook and review each group's link/self-promotion rules.

PROPOSED OUTREACH ASK
When outreach is authorized, ask recipients to review the documented user-control gap, link/share it if useful, provide correction or counterevidence, explain current product behavior, and contribute examples of false positives, false negatives, high-volume spam, and missed legitimate calls. Do not ask communities merely to amplify an allegation.