Local Presence Dialing and Number Rotation: Caller ID Risk

Under the Truth in Caller ID Act, a business may show a local area code on sales calls when it holds each number and each one rings back to it. The FCC said in its 2011 order that a local number display “is not in and of itself a violation of the Act.” Trouble starts with numbers the caller doesn’t hold and numbers cycled fast enough to look like a robocall operation. A company with a clean number inventory usually has a strong answer to a spoofing claim.

Is local presence dialing legal for a business?

Federal law permits local presence dialing in most setups, because the Truth in Caller ID Act depends on intent, not on geography. Local presence dialing means placing a call with a caller ID number whose area code matches the person being called, usually drawn from a pool of numbers the dialer or a vendor supplies.

The statute makes it unlawful “to cause any caller identification service to knowingly transmit misleading or inaccurate caller identification information with the intent to defraud, cause harm, or wrongfully obtain anything of value,” under 47 U.S.C. § 227(e)(1). The FCC’s version of the rule, 47 C.F.R. § 64.1604, reaches anyone who causes such a display “in connection with any voice service or text messaging service.”

Call-management vendors asked the FCC in 2011 to exempt local presence outright. The FCC refused the exemption but answered the underlying question in a footnote to its Truth in Caller ID Report and Order: “We agree that such a practice is not in and of itself a violation of the Act.” The same footnote warned that if a spoofed local number “is done as part of a scheme to defraud, cause harm, or wrongfully obtain anything of value,” the scheme violates the Act.

In its 2003 TCPA order, the agency said the calling number “can include any number associated with the telemarketer or party on whose behalf the call is made, that allows the consumer to identify the caller.” A local number the business leases from its carrier fits that description. A random local number belonging to a stranger doesn’t.

Where does a local number cross into spoofing?

A local number crosses into spoofing under § 227(e) when the caller displays numbers it has no right to use, most of all in a campaign that is already breaking the calling rules. Intent is the element regulators fight over, and the FCC reads it broadly.

The clearest example is the FCC’s 2021 forfeiture order against Rising Eagle, which assessed a $225,000,000 forfeiture over spoofed health insurance robocalls. The order states that “every Rising Eagle caller ID number was either unassigned or assigned to a third party unaffiliated with Rising Eagle or its clients.” The FCC found intent to harm the people who actually held those numbers, noting that “Consumers frequently redial the spoofed number to determine who called or to express outrage.” It also rejected the defense that a client had told the company to use unlisted numbers.

The Commission applies intent to harm where the harm was “substantially certain,” not only where someone wanted it, according to the Rising Eagle order. The order also treats spoofing combined with an unlawful calling campaign as evidence of that intent. A business calling with consent and scrubbed lists is in a very different spot from a campaign with neither.

In its 2017 call blocking order, which first let carriers block calls from unassigned numbers, the FCC said “Use of an unassigned number provides a strong indication that the calling party is spoofing the Caller ID to potentially defraud and harm a voice service subscriber.” A local presence vendor that fills its pool by generating plausible-looking numbers, instead of acquiring real ones, is selling exactly that risk.

Every number on the display should be assigned to the business or its calling vendor, answered by the business, and tied to the same company name. The firm’s earlier guide to caller ID rules and STIR/SHAKEN call signing covers neighbor spoofing and the enforcement record in more depth.

Does every local number have to ring back to your company?

For telemarketing calls, the rule at 47 C.F.R. § 64.1601(e) requires it in practice. Telemarketers must send caller ID, and “The telephone number so provided must permit any individual to make a do-not-call request during regular business hours.” The FCC’s 2003 TCPA order added a time element: “Any number supplied must permit an individual to make a do-not-call request during regular business hours for the duration of the telemarketing campaign.”

A number that answered last week and rings to a dead line today fails that 2003 standard, which is where rotation runs into trouble. The FTC’s Telemarketing Sales Rule has a parallel requirement, letting a seller substitute its customer service number only if that number is one “which is answered during regular business hours,” under 16 C.F.R. § 310.4(a)(8).

Florida’s telephone solicitation statute, section 501.059 of the Florida Statutes, goes further and puts a private claim behind the callback rule. The solicitor “must ensure that telephone number is capable of receiving telephone calls and must connect the original call recipient, upon calling such number, to the telephone solicitor or to the seller on behalf of which a telephonic sales call was placed.” The same section lets an aggrieved called party recover “actual damages or $500, whichever is greater,” and a court may triple that for a willful or knowing violation.

A consumer who dials a local number back to ask the business to stop calling has made a request the business must honor within ten business days under § 64.1200(d)(3), no matter which of 200 numbers the consumer happened to call. That request belongs to the seller, so it has to reach the seller’s master suppression list, a point the firm’s piece on what an internal do-not-call policy must include develops. Many local presence calls land on cell phones. The firm’s post on whether cell phones count as residential lines covers how that question plays out in Do Not Call cases.

Why do rotated numbers get blocked or labeled “Spam Likely”?

Rotated numbers draw blocks and labels because they produce the pattern carrier analytics look for, as the FCC’s 2019 declaratory ruling shows. The ruling lists factors a reasonable blocking program might weigh, including “invalid numbers placing a large volume of calls” and “common Caller ID Name (CNAM) values across voice service providers.” Hundreds of fresh numbers carrying one company name, each making a burst of short calls, is a close match.

Carriers may also block outright, without any analytics, calls that purport to come from a number that isn’t valid or “is not allocated to a provider,” under § 64.1200(k)(2). A vendor pool padded with unallocated numbers will see those calls disappear, and the business may never get a signal that it happened.

The FCC’s October 2025 caller ID notice explains a second filter, STIR/SHAKEN call authentication, in which the provider placing a call on the network signs it with an attestation level. A provider may give full “A” attestation only when it, among other things, “has established a verified association between its customer and the telephone number used for the call.” Numbers leased from a local presence vendor and sent out through a different carrier can fall short of that and get partial “B” attestation. Blocking analytics count too, since a terminating carrier’s safe harbor requires that “Those analytics include consideration of caller ID authentication information where available,” under § 64.1200(k)(3)(ii).

Rotation to escape a “Spam Likely” label is a losing trade. A burned number gets replaced by one with no history, which analytics treat with suspicion, and the dead number now fails the callback rule. The better fix is fewer numbers, each registered to the business’s name, signed by the carrier that assigned it, and kept live through the whole campaign. Blocked callers do have a remedy: a carrier that blocks must offer a point of contact, and once it agrees the blocking was wrong it “must promptly cease the call treatment for that number unless circumstances change,” under § 64.1200(k)(8). The FCC’s December 2020 order declined to extend that redress to labels, so a mislabeled number has a weaker path.

The October 2025 notice is a proposal, not a rule. It asks whether carriers should verify the caller’s name before transmitting it and whether that verification should be a condition of A attestation. A business with a tidy, registered number inventory is positioned for either outcome.

What exposure does local caller ID create?

Claim theory Where it comes from Exposure Defenses that answer it
Spoofing (misleading caller ID) 47 U.S.C. § 227(e); 47 C.F.R. § 64.1604 FCC forfeitures (inflation-adjusted to $14,432 per violation), criminal fines, and state attorney general suits Numbers assigned to the business, no intent to defraud, cause harm, or wrongfully obtain value, caller ID that wasn’t misleading
Caller ID that can’t take a do-not-call request 47 C.F.R. § 64.1601(e) FCC enforcement, plus a private claim under § 227(c)(5) where a court allows one Number answered during business hours throughout the campaign, calls weren’t telemarketing
Calls to Registry numbers or after a stop request 47 C.F.R. § 64.1200(c)(2), (d)(3); 47 U.S.C. § 227(c)(5) Up to $500 per violation, or up to $1,500 if willful or knowing Consent, established business relationship, one call in 12 months, reasonable-procedures defense
Florida callback rule Fla. Stat. § 501.059(8)(b), (10) Actual damages or $500, whichever is greater, up to triple if willful or knowing Number rang through to the seller, call wasn’t a telephonic sales call

Spoofing under § 227(e) is a government case. The statute lists FCC forfeitures, criminal fines, and suits by state attorneys general, and the FCC’s inflation-adjusted figures appear in 47 C.F.R. § 1.80. Those inquiries often begin with a carrier traceback request, which the firm’s article on answering robocall tracebacks and state AG inquiries explains. The private-suit risk sits in the Do Not Call claims, and local presence does nothing to cure a consent or Registry problem.

What to pull together when a caller ID claim arrives

  1. Put a litigation hold on call logs, dialer and platform records, and the consent records for the numbers named in the claim, including which caller ID number went out on each call.
  2. Pull the internal do-not-call and opt-out records, with the date each request arrived and the date it was suppressed, including requests made by calling back a local number.
  3. Pull the National Do Not Call Registry scrub records and the version dates used for each campaign.
  4. Collect the number inventory with assignment records for each number, the local presence vendor and carrier contracts, caller name registrations, and any correspondence about attestation, blocking, or labels.
  5. Talk to a lawyer before responding to a demand letter, calling the claimant back, or offering anything to settle.

Number assignment records from the carrier, often obtained by a Rule 45 subpoena, are the backbone of a spoofing defense. The firm’s article on subpoenaing carriers for number ownership records covers how to get them. The firm’s TCPA defense lawyers page describes how demand letters and class actions over calling practices move through state and federal court.

Questions businesses ask about local caller ID

Can our dialer show a different local number for each state we call?

Under the Truth in Caller ID Act, generally yes, if the business or its calling vendor holds each number and each one reaches someone who can take a do-not-call request during business hours. The FCC has said a local number display isn’t a spoofing violation by itself. The risk comes from numbers the caller doesn’t hold, numbers that go dead mid-campaign, and calls that break the consent or Registry rules.

Is rotating numbers to avoid spam labels illegal?

The Commission’s rules don’t ban number rotation by name, but rotation still causes problems. A retired number that no longer answers fails the callback requirement for telemarketing, and pools padded with unassigned numbers look like spoofing to the FCC and to carrier analytics. Heavy rotation also invites the blocking and labeling it’s meant to avoid. Keeping a smaller set of registered numbers is safer.

Does the Truth in Caller ID Act cover text messages?

Yes, Section 227(e) reaches misleading caller ID “in connection with any voice service or text messaging service.” A business sending marketing texts from a pool of local long codes should apply the same test it uses for calls: it holds every number, and a reply or callback reaches the business.

Can a consumer sue a company for spoofing a local number?

Section 227(e) gives consumers no damages claim, because the statute leaves spoofing enforcement to government agencies and state attorneys general. Consumers still sue over the same calls under the Do Not Call rules. Florida also gives a private claim when a displayed number doesn’t connect back to the seller.

If your company’s caller ID is part of the claim

If your company is accused of spoofing or of calling from local numbers that don’t ring back, the number assignment records and carrier contracts you keep now will shape the defense. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving local presence caller ID 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, including the Truth in Caller ID Act, at 47 U.S.C. § 227. The FCC’s rules are 47 C.F.R. § 64.1601, § 64.1604, § 64.1200, and § 1.80. The FTC’s rule is 16 C.F.R. § 310.4. Florida’s statute is Fla. Stat. § 501.059.

The FCC documents are the 2003 TCPA Report and Order (FCC 03-153); the Truth in Caller ID Report and Order (FCC 11-100); the 2017 Call Blocking Report and Order (FCC 17-151); the 2019 Declaratory Ruling (FCC 19-51); the Fourth Report and Order on call blocking (FCC 20-187); the Rising Eagle Forfeiture Order (FCC 21-35); and the Ninth Further Notice of Proposed Rulemaking (FCC 25-76).

This post is general information about the Telephone Consumer Protection Act and related laws as of January 3, 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.

← Back to Blog

Let’s Talk.