Is Local Presence Dialing Legal? FCC Rules

Yes, local presence dialing is legal in the United States, and the federal rule most people expect to ban it does not. 47 CFR 64.1604 only prohibits transmitting misleading caller ID information when it is done "with the intent to defraud, cause harm, or wrongfully obtain anything of value", and showing a prospect a local number you actually own is none of those. The condition that does bite sits elsewhere and almost no vendor page mentions it: under 47 CFR 64.1601(e)(1), a telemarketer that substitutes a different number must provide one that "must permit any individual to make a do-not-call request during regular business hours". A rotating pool of local numbers that rings nowhere fails that test.

This question gets asked in the wrong order. Teams ask whether local presence is legal, hear a vague yes from a vendor, switch it on, and never find out that the rule attaches a specific duty to the number they are displaying. The duty is short, it is unambiguous, and it is the part that turns a legitimate answer-rate tactic into a violation.

What is local presence dialing?

Local presence dialing, sometimes sold as local caller ID or dynamic caller ID, is a feature that picks the outbound number your call displays based on where the person you are calling lives. Dial a prospect in the 312 area code and the handset shows a 312 number instead of your headquarters number in another state.

The commercial logic is straightforward. People answer numbers that look local more often than they answer unfamiliar out-of-state numbers or toll-free prefixes. Vendors sell it hard for that reason, and they sell it separately: on Apollo, local presence sits inside an Advanced Dialer add-on billed at $119 per team per month, and Kixie packages its version as ConnectionBoost on top of an unpublished base price.

Mechanically, the platform holds a pool of DIDs (direct inward dial numbers) across many area codes and selects one at call time. Readymode, for example, includes 30 numbers per licence on its Starter tier and 75 on iQ. That pool is the thing the law has an opinion about.

Is local presence dialing legal?

Yes, as a general matter, and the reason is the intent element in the federal caller ID rule.

The Truth in Caller ID Act is implemented at 47 CFR 64.1604(a). It says that no person or entity in the United States "shall, with the intent to defraud, cause harm, or wrongfully obtain anything of value, knowingly cause, directly, or indirectly, any caller identification service to transmit or display misleading or inaccurate caller identification information".

Read the qualifier carefully, because it does the work. The prohibition is not on displaying a number other than the one the call physically originated from. It is on doing so with one of three specific intents. A sales team displaying a local number it controls, on a call it is happy to identify itself on, in order to raise the chance somebody picks up, is not defrauding anyone, not causing harm, and not wrongfully obtaining anything of value. That is why the FCC has never treated ordinary local presence dialing as illegal spoofing, and why every major dialer sells the feature openly.

Two exceptions in 64.1604(b) cover law enforcement and court-authorized activity, neither of which applies to sales. Paragraph (c) adds that blocking your own caller ID is not itself a violation of the prohibition, then immediately notes that this "does not relieve any person or entity that engages in telemarketing" of the separate duty to transmit caller ID under 64.1601(e). That pointer is the important one.

The condition almost every vendor page leaves out

Here is the rule that actually constrains how you configure local presence, quoted in full because the wording matters.

47 CFR 64.1601(e) states that any person or entity that engages in telemarketing "must transmit caller identification information", and paragraph (e)(1) continues: "It shall not be a violation of this paragraph to substitute (for the name and phone number used in, or billed for, making the call) the name of the seller on behalf of which the telemarketing call is placed and the seller's customer service telephone number. The telephone number so provided must permit any individual to make a do-not-call request during regular business hours."

Paragraph (e)(2) adds that a telemarketer "is prohibited from blocking the transmission of caller identification information".

The FTC says the same thing from its side. Under the Telemarketing Sales Rule at 16 CFR 310.4(a)(8), it is an abusive practice to fail to transmit the telephone number and, where the carrier makes it available, the name of the telemarketer, with a proviso allowing substitution of the seller's name and "the seller's or charitable organization's customer or donor service telephone number, which is answered during regular business hours".

So substitution is expressly permitted by both agencies. What both attach to it is a functional requirement about the substituted number: a person who sees it must be able to call it back during business hours and ask not to be called again. That is the sentence to hold your vendor configuration against.

Configuration	Where it stands	Why
Local DIDs you own, each routed to a staffed line or an answered queue	Compliant	Meets 64.1601(e)(1) and 310.4(a)(8): the displayed number takes a do-not-call request in business hours
Local DIDs you own, all routing back to one staffed customer service number	Compliant	The rule requires a working callback path, not a unique number per prospect
A rotating pool of local DIDs that ring busy, dead or to an unmonitored voicemail	Not compliant	The displayed number does not permit a do-not-call request during regular business hours
Displaying a number your business does not control	Not compliant, and potentially unlawful spoofing	You cannot answer callbacks on it, and misuse of somebody else's number invites the 64.1604 intent analysis
Blocking or withholding caller ID on a telemarketing call	Prohibited outright	64.1601(e)(2) bars telemarketers from blocking caller ID transmission
Local presence used to disguise who is calling after a do-not-call request	Not compliant	Evading a suppression request is exactly the conduct the intent element in 64.1604(a) is written for

Is local presence dialing the same as spoofing?

No, though the two get used interchangeably and that is where the confusion starts.

Spoofing, in the sense the FCC enforces against, means transmitting caller ID information that is misleading or inaccurate with the intent to defraud, cause harm, or wrongfully obtain something of value. The intent is the offense. Neighbor spoofing, where a scammer mimics the first six digits of the target's own number to impersonate a local resident, sits squarely inside that. So does a debt collector displaying a number belonging to somebody else.

Local presence dialing, done properly, is the opposite posture. You display a number you registered, that you answer, that identifies your business when someone calls it back. Nothing about it is inaccurate in the sense the rule cares about: the call really is coming from your business, and the number really does reach your business.

The line between them is ownership and reachability, not geography. If you can answer it and you would be happy for the prospect to call it, you are on the right side.

Does local presence dialing still work?

Less well than it did, and the reason is technical rather than legal.

Carriers now authenticate calls using STIR/SHAKEN, which attaches an attestation level indicating how confident the originating provider is that the caller is entitled to use the number displayed. Analytics engines on the terminating side combine that signal with call patterns, answer rates and consumer complaints to decide whether to label a call. Numbers that make a high volume of short, unanswered calls get flagged, whatever their area code.

You can see the market pricing this problem. Readymode reserves DID reputation monitoring, managed spam remediation and an Autopilot feature that automatically cycles clean numbers for its iQ tier, and gives its Starter tier none of them. PhoneBurner sells ARMOR, its number monitoring and spam flag remediation service, as a paid add-on on all three of its plans. That tooling exists because rotating numbers to escape labels is now a running operational cost rather than a one-time setup step.

The practical read: local presence still raises answer rates, but a big pool of thinly-used numbers burns reputation faster than a small pool of well-behaved ones, and burned numbers do not recover quickly. The tactics that help and the ones that quietly backfire are covered in how to avoid spam likely on outbound calls.

What else applies to the call itself?

Caller ID is one duty among several, and the others do not go away because your display number is configured correctly.

Residential calls are confined to 8:00 a.m. to 9:00 p.m. local time at the called party's location under 16 CFR 310.4(c). Numbers must be scrubbed against the National Do Not Call Registry and your own internal suppression list, which is set out in Do Not Call list rules for businesses. Under 16 CFR 310.5(a), records have to be kept for five years, and the required per-call record explicitly includes the caller ID number and name transmitted plus proof of authorization to use them. That last item is worth noting: the regulation already assumes you may be substituting a number, and requires you to be able to show you were entitled to.

Since April 11, 2025, under 47 CFR 64.1200(a)(10), a called party may revoke consent by any reasonable method, callers may not designate an exclusive means of doing so, and a revocation must be honored within a reasonable time not exceeding ten business days from receipt. An automated key-press or voice opt-out on the call itself is one of the per se reasonable methods listed in the rule. The broader element requiring revocation to apply across all of a caller's messaging was delayed by FCC order of January 6, 2026 to January 31, 2027, but the rest of the rule has been in force since 2025, and vendors get that distinction wrong in both directions.

Because these obligations move, the teams that stay out of trouble tend to be the ones treating them as a monitored control set rather than a one-off setup task, which is the same discipline behind any system that tracks regulatory changes against the obligations you already have. The AI-specific requirements, including disclosure, are on our TCPA compliant AI calling page.

A configuration checklist before you switch it on

• Confirm every DID in the local presence pool is registered to your business and appears in your carrier records.
• Route all of them to a line that a person answers during your stated business hours, or to a queue that reliably reaches one.
• Make sure a caller reaching that line can be recorded on your internal do-not-call list on the spot, without being transferred or asked to call another number.
• Keep proof of authorization to use each number, since 16 CFR 310.5 requires it in the five-year record.
• Never block or withhold caller ID on a telemarketing call. That is prohibited outright by 64.1601(e)(2).
• Monitor the pool for spam labeling and retire numbers that get flagged rather than dialing through the label.
• Size the pool to your actual dial volume. More numbers is not safer if each one is used too thinly to build a reputation.

The short version

Local presence dialing is lawful. The Truth in Caller ID rule requires intent to defraud, cause harm, or wrongfully obtain value, and ordinary sales use has none of those. What both the FCC and the FTC require is that the number you put on the screen is one a person can call back during regular business hours to ask you to stop calling. Own your numbers, answer them, log the requests, and keep the records.

If you are choosing the platform that will run this, the seat minimums, dialer add-ons and number reputation tooling vary far more than the headline per-seat prices suggest. We priced fifteen of them for a five-person US sales team on outbound calling software, and compared the dialing modes and their line ceilings on parallel dialer software and power dialer software.