Business Calls Labeled ‘Scam Likely’: FCC Blocking and Redress Rules
A business whose calls are blocked can file a dispute with the carrier, get a status update within 24 hours, and have the blocking stopped once the carrier agrees it was wrong. A business whose calls are only labeled “Scam Likely” has no matching rule, because the FCC chose in 2020 not to extend its redress requirements to labels. Neither one decides whether the calls comply with the TCPA, and that’s where a company’s real legal exposure sits.
Is a “Scam Likely” label the same thing as a blocked call?
No, because a labeled call still rings while a blocked call never reaches the phone.
The FCC’s call-blocking rules in 47 C.F.R. § 64.1200(k) govern when a carrier may stop a call, what it must tell the caller, and how the caller can get it fixed. Labels come out of the same carrier analytics, but a label is a warning on the screen, not a refusal to connect.
In its Fourth Report and Order (FCC 20-187, released December 30, 2020), the FCC wrote: “We decline to extend redress mechanisms to erroneous call labeling at this time.” The order’s reasoning was that, with a label, “the call reaches the called party, who can see the label and decide whether to answer,” and a caller who isn’t picked up can still leave a voicemail. Callers asked for more, and the Commission said no. That’s a frustrating answer for a company whose fraud-alert or appointment calls go unanswered, but it’s the rule.
What rules apply when a carrier blocks your calls?
Section 10(b) of the TRACED Act, codified at 47 U.S.C. § 227(j), told the FCC to make sure that opt-in and opt-out blocking services “are provided with transparency and effective redress options for both” consumers and callers, with “no additional charge to callers for resolving complaints related to erroneously blocked calls.” The FCC carried that out in two orders, its Third Report and Order (FCC 20-96, July 2020) and the Fourth Report and Order five months later.
Under § 64.1200(k)(3), a terminating carrier, meaning the one serving the person being called, may block calls its analytics flag as unwanted, so long as the customer can opt out of the blocking and the carrier offers the redress in § 64.1200(k)(8). Under § 64.1200(k)(11), it may block calls without an opt-out when its analytics show they’re part of a pattern “highly likely to be illegal,” with human oversight of the program. That second safe harbor carries a built-in exit: the carrier must stop blocking the pattern “as soon as the provider has actual knowledge that the blocked calls are likely lawful,” under § 64.1200(k)(11)(iii).
Section 64.1200(k)(2) lets carriers block, with no analytics at all, calls that appear to come from invalid, unallocated, or unused numbers. A dialer that displays a number the business doesn’t hold can lose calls this way without warning. The separate caller ID and spoofing rules for businesses explain which numbers a company may display.
How does a business dispute a blocked call?
A blocked-call dispute is filed with the carrier’s designated point of contact, which § 64.1200(k)(8) requires every terminating carrier that blocks to publish on its public website.
Under § 64.1200(k)(8), the carrier must resolve disputes “within a reasonable time and, at a minimum, provide a status update within 24 hours.” When a caller makes a credible claim of erroneous blocking and the carrier agrees, the carrier “must promptly cease the call treatment for that number unless circumstances change.” And it “may not impose any charge on callers for reporting, investigating, or resolving either category of complaints, so long as the complaint is made in good faith.”
Customer-chosen blocking works differently under FCC 20-96. When blocking runs on the customer’s own opt-in or opt-out choice, a lawful call can still be blocked if it falls in a category the customer chose, and the order says “terminating voice service providers are not obliged to cease blocking such calls merely because the caller claims they are legal.” Proving the calls are lawful isn’t enough. The dispute has to show they don’t fit the category.
The Fourth Report and Order leaves out apps the consumer picks, saying “a voice service provider is not responsible for blocking done by a blocking service chosen by the consumer such as a blocking app.” A carrier that hires an analytics vendor stays responsible for that vendor, but a consumer’s own app falls outside the rule.
Section 64.1200(k)(8) also sends complaints about caller ID authentication to the same point of contact. That’s the STIR/SHAKEN score telling the receiving carrier how confident the originating carrier is in the displayed number, and the rule covers a terminating carrier that uses it to decide how to deliver calls, so a label driven by a low score may have a path to the carrier. It’s a narrow path. The Fourth Report and Order notes that the terminating carrier isn’t the entity that typically attests to caller ID, so the fix often runs back through the business’s own carrier.
How will you know your calls were blocked?
Under § 64.1200(k)(9), the answer arrives as a code: a terminating carrier that blocks on analytics “must immediately return, and all voice service providers in the call path must transmit, an appropriate response code to the origination point of the call.” Today that means SIP code 603, 607, or 608 on internet-based networks, or ISUP code 21 on older networks.
On March 25, 2026, that changes. In FCC 25-15, published in the Federal Register on March 24, 2025, the FCC required a single code for analytics-based blocking, SIP 603+, effective on that date. The Commission said “This will ensure that callers learn when and why their calls are blocked based on reasonable analytics, which in turn will allow these callers to access redress when blocking errors occur.” The new code’s reason header flags the block as analytics-based and carries contact information for redress.
The Fourth Report and Order put receiving the code on the caller, warning that “callers may need to make software upgrades or configuration changes to ensure that they receive and process these codes.” A dialer that can’t see them leaves the company guessing which carrier to call.
Under § 64.1200(k)(10), consumers get a tool too: a carrier blocking under an opt-in or opt-out program must give the subscriber, within three business days of a request, a list of calls it blocked to that number in the prior 28 days.
Blocking and labeling rules at a glance
| What happened to the call | Rule in effect | What the carrier owes the caller | Time frame |
|---|---|---|---|
| Blocked by opt-in or opt-out analytics | 47 C.F.R. § 64.1200(k)(3), (k)(8) | Point of contact, no-charge dispute, stop blocking once it agrees the block was wrong | Status update within 24 hours |
| Blocked by network analytics without opt-out | § 64.1200(k)(11) | Same redress, plus a duty to stop once it knows the calls are likely lawful | Status update within 24 hours |
| Blocked because the number is invalid or unallocated | § 64.1200(k)(2), (k)(8) | Same point of contact, though the usual fix is displaying a valid, assigned number | Status update within 24 hours |
| Any analytics-based block | § 64.1200(k)(9) | A response code sent back to the caller | Immediate; SIP 603+ from March 25, 2026 |
| Labeled “Scam Likely” or “Spam Likely” | No rule (FCC 20-187) | Nothing required. The FCC encourages good-faith cooperation | None |
Does a spam label matter in a TCPA lawsuit?
A label plays no direct part in a Telephone Consumer Protection Act (TCPA) claim, because it isn’t a finding that a call broke the law. The statute asks other questions, such as whether the business had consent and whether the number was on the National Do Not Call Registry, the federal list of numbers whose owners have opted out of telemarketing. Labeled calls that ring carry the same exposure as any other call: up to $500 per violation, or up to $1,500 if a court finds the violation willful or knowing.
The FCC’s 2019 declaratory ruling (FCC 19-51) shows where the patterns that draw labels overlap with TCPA risk. It listed factors a reasonable blocking program might weigh, starting with “large bursts of calls in a short timeframe” and including “patterns that indicate TCPA or other contract violations.” Carrier analytics, in other words, were invited to look for the same conduct plaintiffs’ lawyers look for. Heavy dialer pacing raises the FCC’s 3 percent abandoned-call limit, and the problems with rotating local numbers to dodge spam labels run deeper than lost answer rates. A label is often the earliest outside signal that a calling program has a problem worth fixing before a demand letter arrives.
Blocked calls give the defense an underused argument, because a Do Not Call plaintiff must have “received more than one telephone call within any 12-month period” under § 227(c)(5). A blocked attempt never rang, and the carrier’s response code records that, so those codes can cut the count of calls the plaintiff actually received. They also bear on who has standing to sue over a call, since a call that never reached the phone is a weak basis for a claim by anyone. Companies that throw the codes away give up that argument.
The 2019 ruling also lists “a large volume of complaints related to a suspect line” as a blocking factor, so a business seeing labels should be ready for how to answer an FCC consumer complaint about the same calls.
Is the FCC changing how labels work?
Only by proposal so far, in a notice adopted October 28, 2025 (FCC 25-76). The FCC proposed requiring terminating carriers to transmit a verified caller name whenever they show that a call received the highest attestation. The Federal Register summary says verified caller identity would give carriers more information for their analytics, “potentially making the analytics more accurate and thus addressing concerns about calls being labeled inaccurately.” Reply comments were due February 3, 2026. For now, it’s a proposal, and labels remain outside the redress rules.
What to collect when your numbers get labeled or blocked
- Preserve the call records under a litigation hold once any claim surfaces: dialer logs, carrier detail records, the consent behind each number called, and the SIP or ISUP response codes for every attempt.
- Export the internal do-not-call list and opt-out history with dates, since a number that asked to stop and kept getting calls is a risk for both labels and claims.
- Keep the National Do Not Call Registry scrub files and the version dates used for each campaign.
- Gather the carrier and dialer-vendor contracts, the number inventory with assignment records, call scripts, and any recorded or AI-voice message files, along with every dispute filed with a carrier and its response.
- Talk to a lawyer before answering a demand letter, calling the claimant back, or offering a payment to make a complaint go away.
The firm’s page on defending TCPA class actions in California explains how demand letters and class claims over calling programs move through state and federal court.
Questions businesses ask about spam labels and blocking
Can a carrier label our calls “Scam Likely” without telling us?
Yes, and no Commission rule requires a carrier to notify a business before or after labeling its calls. The FCC declined in 2020 to require any redress process for labels. The Commission did encourage carriers and their analytics partners to work with callers in good faith to avoid erroneous labels. Any review a carrier offers is voluntary, though, so the terms vary from carrier to carrier.
How fast must a carrier respond to a blocked-call dispute?
Within 24 hours, with at least a status update. The rule requires the terminating carrier to resolve the dispute within a reasonable time and to give that update within 24 hours. It can’t charge a caller who files in good faith. If the carrier decides the calls shouldn’t have been blocked, it must promptly stop blocking that number unless circumstances change.
Does the blocking redress process cover text messages?
Partly, through § 64.1200(r), a separate rule. It requires mobile carriers to provide a point of contact for message senders who can document that their texts were blocked. The 24-hour status update and the response-code rules are written for voice calls, so text senders get a contact point without those specific deadlines.
If your calling program is the subject of a claim
If your company has been sued or received a demand letter over calls that carriers flagged or blocked, the response codes and dialer records you keep now may decide how many calls the plaintiff can actually count. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving high-volume calling programs and Do Not Call compliance. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227, including subsection (j), added by section 10(b) of the TRACED Act. The FCC’s call-blocking rules are at 47 C.F.R. § 64.1200(k), in the version in effect on February 24, 2026.
The FCC documents are the 2019 Declaratory Ruling (FCC 19-51, released June 7, 2019) and the Third Report and Order (FCC 20-96, released July 17, 2020). The redress and labeling decisions are in the Fourth Report and Order (FCC 20-187, released December 30, 2020). The response-code change is the SIP code 603+ order (FCC 25-15, 90 Fed. Reg. 13416, March 24, 2025), and the pending proposal is the caller identity notice (FCC 25-76, 90 Fed. Reg. 56101, December 5, 2025).
This post is general information about the Telephone Consumer Protection Act and related laws as of February 24, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.