Last updated 2026-07-10
TL;DR
Local presence dialing, where your dialer shows a caller ID with the same area code as the person you're calling, is legal only if the displayed number is real, provisioned to you, and able to receive callbacks. You also have to scrub the National Do Not Call Registry and get consent or a valid exemption. A fake or dead number breaks the Truth in Caller ID Act and adds up to $10,000 per call on top of TCPA damages.
What is local presence dialing and how does it work?
Local presence dialing is a strategy where your outbound dialer picks a caller ID that shares the same area code, and sometimes the same three-digit prefix, as the number you're about to call. The idea is plain. People answer local numbers far more often than they answer out-of-state or toll-free numbers. Sales engagement vendors who publish answer-rate data report lift somewhere between 30 and 400 percent, but the variance is enormous and depends on your industry and list quality. Nobody has independently audited these numbers. Almost every figure comes from the vendor selling the feature.
The mechanics are simple. Your dialer keeps a pool of phone numbers, each tied to a specific area code. Your rep dials someone with a 614 area code, the platform routes the call through a 614 number, and that 614 number shows up as the caller ID. The called party sees what looks like a neighbor calling. If they call back, that number has to route somewhere real for the whole thing to stay legitimate.
Most modern dialers offer local presence as a built-in feature, including Salesforce Dialer, RingDNA, Kixie, and PhoneBurner. The technology isn't the problem. How teams configure and use it is.
Is local presence dialing legal under the TCPA?
Yes, with conditions. The TCPA (47 U.S.C. § 227) doesn't name local presence dialing as prohibited. A few overlapping federal rules create real exposure if you do it wrong.
The Truth in Caller ID Act of 2009, codified at 47 U.S.C. § 227(e), bans transmitting misleading or inaccurate caller ID information "with the intent to defraud, cause harm, or wrongfully obtain anything of value." [1] The FCC reads this broadly. In its 2011 rules implementing the Act, the FCC said displaying a number that isn't a real, working number assigned to the caller can be a violation when it comes with deceptive intent. [2]
Here's the line. If your local presence number is real, assigned to your business, and able to receive and return calls, you're generally on the right side of the Truth in Caller ID Act. If the number is fake, non-working, or routes to a dead end, you're in dangerous territory.
The TCPA's autodialer and consent rules still apply in full. Local presence dialing creates no exemption from consent requirements, DNC scrubbing, or the rules on calling cell phones with an automatic telephone dialing system (ATDS). [3] Run local presence on a list you never scrubbed and you've got two problems at once.
What does the Truth in Caller ID Act actually require?
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." [1] That's the text of 47 U.S.C. § 227(e). The FCC's implementing rules at 47 C.F.R. § 64.1604 mirror the same language.
Two things matter. First, intent. The statute targets deceptive caller ID manipulation, not every technical mismatch between the calling party and the displayed number. A business using a local number it legitimately controls isn't spoofing in the prohibited sense. Second, the number has to be real and assigned. "Assigned" under FCC guidance means the number is actually provisioned to you through a carrier or a VoIP provider with a real North American Numbering Plan number assignment. [10]
The FCC can issue forfeitures of up to $10,000 per violation for caller ID spoofing, and the TRACED Act of 2019 raised those penalties and expanded the agency's enforcement authority. [4] Plaintiff's attorneys have started pairing Truth in Caller ID claims with TCPA claims in the same complaint, which stacks the exposure.
So the practical rule is short. Every number in your local presence pool should be provisioned through your carrier or a reputable VoIP provider, listed in your account, and able to receive inbound calls that land somewhere real, even if that's just a voicemail box or a forward to your main line.
Does the FCC have specific guidance on local presence dialing?
No. The FCC has never issued a rule that names "local presence dialing" as a distinct practice. What it has done is issue a run of orders and declaratory rulings that draw the edges of what's allowed.
The rulings that matter most are the 2011 Truth in Caller ID rules [2], the 2015 TCPA Omnibus Declaratory Ruling [5] (which clarified ATDS definitions and consent rules), and the 2021 and 2023 orders tightening robocall rules under the TRACED Act. None of them create a safe harbor for local presence dialing. None of them ban it either.
The FCC's robocall mitigation rules require voice service providers to run STIR/SHAKEN call authentication on their networks. [6] That protocol lets carriers verify whether the number in caller ID is really the number the call is coming from. If your local presence numbers aren't properly registered to your account with your carrier, your calls may get a "B" or "C" attestation level, which many carriers use to filter or label calls as possible spam. That's a business problem on top of a legal one. Even a technically legal setup gets defeated by a "Spam Risk" label on the receiving end.
To earn "full attestation" (A-level) under STIR/SHAKEN, the originating carrier has to verify you're authorized to use the number displayed. That only happens when the number is legitimately provisioned to your account. [6]
What are the TCPA consent rules that apply on top of local presence?
Local presence dialing doesn't touch the TCPA's consent framework. You follow the same rules as any other outbound call or cold call.
Calls to residential landlines using a prerecorded message need prior express consent. Calls to cell phones using an ATDS or prerecorded voice need prior express written consent. [3] Manual cold calling to cell phones without a prerecorded message sits in a grayer zone, but if your dialer has ATDS traits (predictive dialing, random or sequential number generation), the cell phone consent requirement kicks in no matter what caller ID you show.
B2B calls to business landlines carry looser consent requirements, but you're never fully exempt. The FTC's Telemarketing Sales Rule (TSR) and the National DNC Registry rules still reach many B2B telemarketing calls depending on the context.
Here's the point that trips people up. Local presence is a caller ID strategy. It does not turn a non-consented call into a consented one. Teams that use local presence to slip past caller ID screening on people who never consented are risking TCPA exposure. They're arguably using the feature in exactly the deceptive way the Truth in Caller ID Act was written to stop.
If you're not solid on the consent tiers, read the full TCPA rundown first.
Do you have to scrub local presence calls against the Do Not Call Registry?
Yes, every time. Local presence dialing changes your caller ID. It does not change your obligation to honor the National Do Not Call Registry or state DNC lists. [7]
Making telemarketing calls (calls meant to sell goods or services) means you scrub your list against the National DNC Registry before you dial. Numbers on the Registry can't be called unless you have an established business relationship (EBR) with the person, that person gave you prior written consent, or you have a personal relationship with them. The EBR exemption is narrower than most teams think. It runs out 18 months after the last transaction and 3 months after the last inquiry. [7]
State DNC lists stack another layer on top. Florida, Texas, Wyoming, Indiana, and several other states run their own lists with their own scrubbing rules and penalties. Some are stricter than the federal baseline.
You can learn how to access the federal registry on the do not call list page. If you specifically handle the mobile phone do not call list rules, read those separately, because mobile numbers on the DNC get dialed at disproportionate rates by teams that assume cell phones are a separate system.
One more thing. The do not call telemarketer list rules require you to keep your own internal DNC list of people who asked not to be called, separate from the national registry. Local presence dialing does not excuse you from honoring internal opt-outs.
What happens when called parties call back a local presence number?
This is where teams create their own trouble. A prospect sees a missed call from a local-looking number and calls it back. What happens next decides whether you have a clean program or a complaint waiting to file.
If the number hits a dead recording, a generic voicemail with no company name, or just rings forever, that's bad for your brand and potentially bad legally. The FCC has flagged displaying a non-working number as a Truth in Caller ID concern. A confused or annoyed prospect who can't tell who called is the person most likely to file a complaint with the FTC or their state AG.
The right setup routes every local presence callback to a live agent queue, an IVR that names your company, or at minimum a voicemail greeting that says who you are and how to reach you. "You've reached Sales at [Company Name], please leave a message" works. "The number you have dialed is not in service" does not.
Some teams route callbacks to a central inbound line. Others route per-rep so the original caller gets the callback. Both work, as long as someone can answer or the company's identity is clear.
If your local presence numbers start showing up as "Spam" or "Scam Likely" in recipients' apps, that's a STIR/SHAKEN attestation and carrier reputation problem. Rotating numbers too fast, using numbers for very short stretches, or pushing high call volumes through a single number will drag down your reputation score with the analytics platforms (Hiya, First Orion, TNS) that feed carrier spam labels.
How do STIR/SHAKEN and call labeling affect local presence dialing?
STIR/SHAKEN is the call authentication framework the FCC mandated under the TRACED Act. Larger carriers had to implement it by June 2021 and smaller ones by June 2023. [6] It attaches a digital certificate to each call that tells the receiving carrier whether the originating carrier can vouch for the caller ID.
There are three attestation levels:
| Attestation | Meaning | Typical outcome |
|---|---|---|
| A (Full) | Carrier confirms caller is authorized to use the displayed number | Passes cleanly |
| B (Partial) | Carrier verifies call origin but cannot verify the displayed number | May be flagged |
| C (Gateway) | Carrier can only verify entry point of call, not origin or number | Often flagged as Spam Risk |
Local presence dialing with properly provisioned numbers, where your carrier knows you're authorized to use each one, earns A-level attestation. Local presence with numbers that aren't registered to your account, or numbers routed through gateway providers that can't vouch for them, lands at B or C and shows up as "Spam Risk" on iPhones and Android phones often enough to kill your answer rate.
So a technically legal local presence setup can still get spam-labeled if your carrier relationships and provisioning aren't clean. The label doesn't create a legal violation by itself. It just defeats the entire reason you turned on local presence.
To stay clean, buy or lease your local presence numbers directly through your originating carrier, don't rotate numbers faster than the carrier's reputation system can track, and keep per-number call volumes below the levels that trip analytics thresholds. Nobody publishes those exact thresholds. The general guidance from call analytics providers is to avoid burning through numbers faster than reputation can build.
What are the real TCPA penalties if local presence dialing goes wrong?
The TCPA sets statutory damages of $500 per violation (each call) and up to $1,500 per willful or knowing violation. [3] There's no cap per plaintiff or per lawsuit, which is how TCPA class actions reach tens or hundreds of millions of dollars.
Add Truth in Caller ID Act forfeitures of up to $10,000 per call for spoofing and the math turns ugly fast. A 10-person team making 100 calls a day on bad local presence numbers for one week is 5,000 calls. At $1,500 TCPA per call plus $10,000 spoofing per call, the theoretical ceiling is $57.5 million. Real settlements run far lower, but the ceiling is real.
Actual outcomes are the better guide. The credit one tcpa settlement reached $75 million. The cash app tcpa class action settlement shows how quickly consumer finance companies draw exposure. Neither was a local presence case, but both show what TCPA class actions cost once they settle.
FCC enforcement against caller ID spoofing has grown too. The agency proposed $225 million in forfeitures in a single 2020 action against a health insurance robocall scheme, though collecting large FCC forfeitures stays inconsistent. [8]
For a small team, the real risk isn't a $57 million judgment. It's a demand letter from a plaintiff's attorney threatening a class action. Those typically settle somewhere between $50,000 and several million, depending on call volume and how clean your records are. Even the low end is a company-ending number for a small team.
Want to check your own exposure before an attorney does? The free compliance tools at LeadCompliant run your numbers against the national DNC registry and flag likely consent gaps before you dial.
How do you set up local presence dialing to stay compliant?
Here's what a legally clean local presence setup looks like in practice.
First, buy or lease your local presence numbers through your originating voice carrier, not a third-party reseller that provisions numbers in bulk with no carrier-level registration. Your account should clearly show these numbers are assigned to your business entity. That's what gets you A-level STIR/SHAKEN attestation.
Second, route every local presence number's inbound calls somewhere real. A central inbound queue is fine. A voicemail with company identification is fine. A dead line is not.
Third, scrub your list against the National DNC Registry before you dial anyone. Federal rules require scrubbing no more than 31 days before the call. [7] Scrub against your internal DNC list too, for anyone who already opted out of your calls. Calling cell phones with a predictive dialer? Get prior express written consent first.
Fourth, manage number rotation with restraint. Don't cycle through dozens of fresh numbers every few days to dodge spam labels. That's exactly the behavior analytics platforms flag. A smaller pool with consistent usage builds reputation. A large pool of disposable numbers destroys it.
Fifth, document everything. Keep your number provisioning agreements, your DNC scrub logs (with the date of each scrub), and your consent records. When a demand letter shows up, these records are the difference between a dismissal and a settlement.
The LeadCompliant compliance kit walks through the documentation checklist for a B2B or B2C outbound team, including what scrub logs need to hold up in discovery.
If you're wondering how do i get the do not call list, the FTC's online portal lets you access it by area code. Large list access needs a subscription, but individual area codes are free to check.
Are there differences in local presence rules for B2B versus B2C calls?
Yes, and the gap is real, though smaller than many B2B teams assume.
B2C calls, especially to cell phones, get the strictest treatment. TCPA consent requirements apply in full. DNC scrubbing is mandatory. Truth in Caller ID requirements apply. There's basically no exemption that makes it safe to run local presence on a cold list of consumers without written consent.
B2B calls to business landlines don't trigger the TCPA's residential line provisions directly. The FCC and courts have generally held that calls to businesses face less restrictive TCPA rules than calls to residences or personal cell phones. The FTC's Telemarketing Sales Rule covers B2B telemarketing calls to sellers or buyer-sellers in some contexts, and the Truth in Caller ID Act applies to every call regardless of B2B or B2C. [9]
So B2B local presence dialing to business landlines carries lower TCPA exposure, but it isn't risk-free. The Truth in Caller ID requirement still applies. And if a business employee's cell phone is in your list and you're dialing it with a predictive dialer, you're back in full TCPA territory no matter how commercial the context is.
The most common mistake: small teams run B2B local presence on lists that mix business landlines and mobile numbers without telling them apart. A clean B2B program needs phone number type validation, so you know which numbers are mobile before you dial.
What should you tell your sales team about using local presence ethically?
Compliance on local presence isn't only a legal question. It's a cultural one.
Reps who understand why the rules exist tend to follow them. Reps who see local presence as a trick to fool people into picking up tend to cut corners elsewhere too, like ignoring internal DNC flags, calling people who asked not to be called back, or treating the local number as a throwaway identity.
The framing that works is honest and simple. Local presence lowers the friction of an unfamiliar area code. It isn't about deceiving anyone. The call should be honest, the company should be identifiable, and the rep should be ready to tell anyone who asks exactly what number they're calling from and why.
When a prospect asks "what number is this?" or "are you calling me from [city]?", reps answer straight. Saying "I'm calling from our [City] office" when you have no office there is the kind of statement that turns a caller ID question into a fraud claim.
Train your team on three things: the callback number has to be real and identified, the call goes only to people who haven't opted out, and the rep never misrepresents the company's location or identity. That's a five-minute training, not a compliance overhaul.
Frequently asked questions
Is local presence dialing the same as caller ID spoofing?
Not legally, if you do it right. Spoofing under the Truth in Caller ID Act means transmitting misleading caller ID with intent to defraud or cause harm. Local presence dialing with a real, provisioned number you're authorized to use is not spoofing. Using a fake or non-working number dressed up with a local area code is spoofing and is illegal under 47 U.S.C. § 227(e). The whole distinction is whether you actually control and can receive calls on the displayed number.
Can I use local presence dialing to call cell phones?
Yes, but TCPA consent rules still apply in full. Using an ATDS or predictive dialer to call cell phones means you need prior express written consent, no matter what caller ID you show. Local presence only changes the number the recipient sees. It changes nothing about consent. Manual dialing to cell phones without a prerecorded message is grayer, but most counsel advises treating any list with cell phones as requiring consent verification.
How many local presence numbers do I need for a compliant setup?
There's no legally mandated minimum or maximum. Practically, you want enough numbers to cover the markets you call without cycling through them so fast that analytics platforms flag them. A common starting point is one number per area code you actively target, each handling a moderate daily volume. Your carrier or dialer vendor can advise on volume thresholds that keep your STIR/SHAKEN attestation at A-level.
Do I need to register my local presence numbers with the FCC?
You don't file a separate registration with the FCC. But the numbers must be properly provisioned through a NANP-compliant carrier that can attest to your authorization under STIR/SHAKEN. That happens through your carrier agreement, not an FCC filing. If your numbers come from a reputable VoIP or telecom provider and sit in your account, you're in the right position.
What happens if someone on my local presence call list is on the National DNC Registry?
Calling a Registry number for telemarketing is a TCPA violation regardless of the caller ID you display. Penalties start at $500 per call. You must scrub your list against the Registry within 31 days before each campaign. There's no local presence exception. If you have an established business relationship or written consent from that specific person, the DNC listing doesn't block you, but those exemptions are narrow.
Will local presence dialing get my calls labeled as spam?
It can, if your setup is wrong. Calls get spam labels through carrier analytics platforms like Hiya, First Orion, and TNS when the displayed number has high complaint rates, isn't registered to a known business, or shows abnormal calling patterns. Properly provisioned numbers with A-level STIR/SHAKEN attestation are much less likely to be labeled. Numbers that rotate rapidly, show no inbound history, or come from gateway carriers get labeled often.
Does local presence dialing violate the TRACED Act?
Not by itself. The TRACED Act of 2019 expanded FCC enforcement over illegal robocalls and caller ID spoofing and mandated STIR/SHAKEN. It doesn't create a new prohibition on local presence dialing. What it does is make running local presence with unregistered or spoofed numbers harder, because STIR/SHAKEN gives those calls low attestation levels and carriers use that to filter them.
What records do I need to keep for local presence compliance?
Keep number provisioning agreements showing each local presence number is assigned to your business. Keep dated DNC scrub logs showing the list you used, the Registry version you checked, and the scrub date. Keep consent records if you call cell phones. Keep internal DNC opt-out logs. TCPA cases often turn on whether a defendant can produce these in discovery. No records usually means no defense.
Can a class action lawsuit target local presence dialing specifically?
Yes. Plaintiff's attorneys file cases combining TCPA claims (unconsented autodialed calls) with Truth in Caller ID claims (misleading caller ID) in one complaint. The dual-claim approach is attractive because it layers two damages frameworks. Even if a defendant wins the Truth in Caller ID claim, the TCPA claim can proceed on its own. The combination also raises settlement cost because the exposure is higher.
Is local presence dialing legal in all states?
Federal law applies nationwide, but some states add call rules that interact with local presence dialing. Florida's Mini-TCPA (the Florida Telephone Solicitation Act) applies its own consent and calling rules to Florida numbers and is notably aggressive. Texas, Indiana, and others run their own DNC rules and solicitation statutes. Showing a Florida or Texas area code while calling Florida or Texas residents puts you under those states' rules. Check state law for your target geographies.
Does local presence dialing apply to text message campaigns?
Local presence dialing is mainly a voice call strategy, but the underlying idea (using a local area code number) carries over to SMS. Send texts from a local-looking number and the TCPA's text rules apply. That means prior express written consent for marketing texts to cell phones. The Truth in Caller ID Act also reaches SMS sender identity. Check the full text message marketing rules before running local presence SMS campaigns.
How do I handle callbacks to local presence numbers from people who are upset?
Treat every callback as a possible opt-out request and a possible complaint. If someone calls back and says "stop calling me," add them to your internal DNC list immediately and honor it. The FTC requires internal DNC entries to be kept for at least five years. Identify your company clearly on every callback. Document the opt-out with a timestamp and the number involved. An undocumented opt-out you then ignore is close to the worst fact pattern you can have in a TCPA case.
What dialer features should I look for to support compliant local presence use?
Look for dialers that integrate DNC scrubbing natively (or connect to a scrubbing service), support STIR/SHAKEN-compliant number provisioning through major carriers, offer inbound routing for callback numbers, keep call logs with timestamps and caller ID records, and flag numbers that recently received opt-out requests. A dialer that only handles outbound without managing inbound callback routing is half a solution for local presence compliance.
Sources
- U.S. Government Publishing Office, 47 U.S.C. § 227(e), Truth in Caller ID Act: The Truth in Caller ID Act prohibits transmitting misleading or inaccurate caller ID information with the intent to defraud, cause harm, or wrongfully obtain anything of value.
- FCC, Truth in Caller ID Act Rules, Report and Order, FCC 11-100 (2011): The FCC's 2011 Truth in Caller ID implementing rules defined prohibited caller ID manipulation and clarified that displaying a non-working number can constitute a violation.
- FCC, Telephone Consumer Protection Act, 47 U.S.C. § 227: The TCPA requires prior express written consent for autodialed or prerecorded calls to cell phones and provides statutory damages of $500 to $1,500 per violation.
- U.S. Congress, TRACED Act, Pub. L. 116-105 (2019): The TRACED Act of 2019 increased FCC civil forfeiture penalties for caller ID spoofing and mandated STIR/SHAKEN call authentication implementation.
- FCC, In the Matter of Rules and Regulations Implementing the TCPA, Declaratory Ruling and Order, FCC 15-72 (2015): The FCC's 2015 TCPA Omnibus Declaratory Ruling clarified ATDS definitions, consent rules, and confirmed that consent requirements apply regardless of caller ID presentation.
- FCC, STIR/SHAKEN Call Authentication Framework rules, 47 C.F.R. Part 64: The FCC mandated STIR/SHAKEN implementation for major carriers by June 2021 and smaller carriers by June 2023; A-level attestation requires the originating carrier to verify the caller is authorized to use the displayed number.
- FTC, National Do Not Call Registry, Telemarketing Sales Rule, 16 C.F.R. Part 310: The Telemarketing Sales Rule requires telemarketers to scrub call lists against the National DNC Registry no more than 31 days before calling; the established business relationship exemption expires 18 months after last transaction.
- FTC, Complying with the Telemarketing Sales Rule, business guidance, 16 C.F.R. Part 310: The FTC's Telemarketing Sales Rule covers certain B2B telemarketing calls and applies the Truth in Caller ID requirements to commercial calling contexts.