97% of US adults own a smartphone. The decision-makers your SDRs are calling carry their phone everywhere — to meetings, to lunch, to airports, to the office. Cold calling cell phones isn’t optional in 2026; it’s the default. But the federal TCPA was written in 1991 to protect consumers from intrusive cell phone calls, and it treats every wireless number as residential, regardless of business use.
This guide breaks down what’s actually legal when cold calling cell phones in B2B, where the real TCPA traps live, and how to dial mobile-first prospects without writing checks to plaintiffs’ attorneys.
Under the TCPA, a CEO’s iPhone is residential. A business landline is business. The number type — not the person on the other end — is what determines your liability.
Why cell phones have become the default channel in B2B
It’s worth restating just how dominant mobile is in 2026:
- 97% of US adults own a smartphone (Pew Research)
- 78% of business decision-makers prefer to be reached on mobile, not desk phone
- Hybrid work has collapsed the desk phone — most office switchboards see 40-60% lower call volume than 2019
- ZoomInfo, Apollo, Cognism, and Lusha all sell verified mobile numbers as their highest-value SKU
If your SDRs aren’t dialing cell phones, they’re dialing dead lines. The question isn’t whether to call mobile numbers. The question is how to do it without triggering the TCPA.
What the TCPA actually says about cell phones
The Telephone Consumer Protection Act has two distinct tracks: one for landlines, one for wireless. The wireless track is much stricter.
Wireless restrictions under TCPA
| Provision | What it means |
|---|---|
| Auto-dialed calls | Require prior express written consent for marketing calls |
| Pre-recorded / artificial voice | Require prior express written consent |
| Manually-dialed marketing calls | Generally allowed during legal hours (8 AM - 9 PM local) |
| Calling hours | 8 AM - 9 PM in the recipient’s local time zone |
| ATDS test | Federal: Facebook v. Duguid 2021 narrow definition. State: broader |
The two questions that determine your TCPA exposure
When you dial a cell phone, your liability depends on the answers to two questions:
-
Is it manually dialed or auto-dialed? If a human presses a button to dial each call, you’re in the safer “manual dial” lane. If any system queues, batches, or routes calls automatically, you’re potentially in ATDS territory.
-
Did the prospect give prior express written consent? If yes, you’re cleared for auto-dialed calls. If no, manual dial only.
That’s it. Everything else (B2B vs B2C, intent, business purpose) is secondary to these two questions.
What “ATDS” actually means in 2026
The Automatic Telephone Dialing System definition is the entire battleground of TCPA litigation. It used to be enormously broad. Then Facebook v. Duguid narrowed it. Then the states re-expanded it.
Federal definition (Facebook v. Duguid, 2021)
To qualify as an ATDS, a system must use “a random or sequential number generator” to store or produce telephone numbers. Most modern sales dialers don’t qualify under this definition because they pull from pre-loaded contact lists, not random generators.
Practical impact: at the federal level, most B2B power dialers and parallel dialers are not ATDSs, which means they’re not subject to the prior consent rule for cell phone calls — as long as the calls are placed during legal hours and the rep is making the connection decisions.
State definitions (Florida, Oklahoma, Washington)
Florida’s FTSA and Oklahoma’s OTSA both define autodialer much more broadly than the federal Duguid standard. Almost any electronic dialing tool can qualify in these states. If you’re dialing into Florida or Oklahoma cell phones with any kind of automated platform, treat the consent requirement as binding — federal preemption doesn’t help you here.
McLaughlin v. McKesson (June 2025)
The Supreme Court ruled that district courts no longer have to defer to FCC interpretations of the TCPA. That means the same dialer can be ruled an ATDS in one circuit and not in another. National outbound teams need to monitor circuit-level case law, not just FCC guidance.
The “personal use” trap
Here’s the single most dangerous gray area in B2B cell phone outreach: a personal cell number that the prospect uses for both personal and business purposes.
The TCPA does not have a “business use” carve-out for wireless numbers. The number is wireless. The number is the regulated entity. Whether the recipient uses it for business is legally irrelevant at the federal level.
That said, courts have been more lenient when:
- The number was obtained from a reputable B2B data provider
- The call is manually dialed
- The call occurs during business hours and on a business day
- The opener identifies the company purpose immediately
- The rep stops dialing after the first opt-out
If you’re going to dial personal cells in B2B, do it manually, do it cleanly, and document the source.
What is “prior express written consent”?
This is a specific legal standard. It’s not just an opt-in checkbox. To meet the TCPA standard, the consent must:
- Be in writing (digital signature or checked box is fine)
- Clearly disclose that the prospect agrees to receive marketing calls or texts via auto-dialer or pre-recorded message
- Identify the specific seller by name
- Not be conditioned on the purchase of any product or service
- Be stored and retrievable for the duration of the relationship plus statute of limitations
The standard format: a check box on a web form with disclosure language directly above the checkbox, not buried in a privacy policy. Pre-checked boxes don’t count.
How to identify cell vs landline before you dial
Treating every call as cell phone is overly cautious. Treating every call as landline is dangerous. The smart move: identify the line type before the dial.
Methods to identify cell phones
| Method | Cost | Accuracy | Use case |
|---|---|---|---|
| HLR lookup (real-time) | $0.001-0.005/lookup | 99%+ | High-volume outbound at scale |
| Data provider line type field | Included in ZoomInfo, Apollo, Cognism, Lusha | 95%+ | Standard for prepared lists |
| Carrier API integration | $0.005-0.01/call | 99%+ | Real-time routing decisions |
| Dialer-native detection | Included with most modern dialers | 95-99% | Automatic, no extra step |
Routing logic by line type
Once you know whether a number is mobile or landline, route accordingly:
- Landline: standard automated workflows are fine (subject to DNC scrub)
- Mobile, with prior consent on file: standard automated workflows are fine
- Mobile, no prior consent: manual dial only, during legal hours, with rep judgment
Skipcall builds this routing into the platform — every contact is auto-tagged by line type, and you can configure separate workflows per type.
The 7 best practices for B2B cell phone cold calling
Identify line type before adding a contact to a cadence
Use your data provider’s line type field or a real-time HLR lookup. Tag every contact as cell or landline at ingestion. Don’t discover it mid-cadence.
Route mobile contacts through manual-dial workflows
For cell phones without prior express written consent, the only TCPA-safe path is manual dialing during legal hours. Don’t auto-dial cells unless you have documented consent.
Calculate calling windows by recipient timezone, not yours
8 AM - 9 PM is in the recipient’s local timezone. Florida is 8 AM - 8 PM. Build that logic into the dialer, not into rep memory.
Cap attempts at 3 per 24 hours when calling FL or OK
Florida and Oklahoma both cap contacts at 3 attempts per recipient per rolling 24 hours. Configure your dialer to enforce this per-state.
Always disclose call recording at the start of the call
11 states require all-party consent to record. Even in one-party states, opening with “this call may be recorded” costs nothing and prevents any cross-state issues.
Honor opt-outs within 10 business days, forever
Maintain an internal DNC list shared across all campaigns. Once a prospect says “stop calling me,” they’re permanently suppressed — no exceptions, no “6 months from now.”
Capture consent on every web form to expand your auto-dial pool
Add a TCPA-compliant consent checkbox to every demo request, content download, and contact form. Every consent you collect is one more contact you can put in your auto-dialed cadences without legal risk.
The cost of getting it wrong
To put the stakes in perspective, here’s what TCPA cell phone violations actually cost:
| Violation type | Per-call penalty | Real-world settlement examples |
|---|---|---|
| Non-willful TCPA violation | $500 | $7M (Domino’s), $5M (Sirius XM) |
| Willful TCPA violation | $1,500 | $32M (Bumble), $40M (Caribbean Cruise Line) |
| Florida FTSA violation | $500 / $1,500 | Multiple class actions in 2024-2025 |
| Oklahoma OTSA violation | $500 / $1,500 | Growing case volume since 2023 |
A single 1,000-contact cell phone campaign run with non-compliant auto-dialing can produce TCPA exposure of $500,000 minimum if even 10% of recipients sue. The math is brutal precisely because plaintiffs’ attorneys have figured out how to monetize it.
How Skipcall is built for compliant cell phone outreach
Skipcall is built around the assumption that you’re dialing mobile-first in 2026. Compliance features that ship in the platform:
- Automatic line-type detection: every contact is tagged cell or landline before any dial occurs
- Workflow routing by line type: route mobiles through manual-dial flows, landlines through automated cadences
- Timezone-aware calling windows: enforces 8 AM - 9 PM (or 8 PM in Florida) by recipient timezone
- State-by-state attempt caps: Florida and Oklahoma’s 3-per-24-hour rules enforced per contact
- Internal DNC suppression: opt-outs propagated across every campaign instantly
- Consent tracking: stores prior express written consent with timestamps and source for audit trail
- Manual dial mode: clean rep-driven calling that stays out of the ATDS argument entirely
Compliance and productivity aren’t trade-offs. They’re the same problem solved by the same tooling.
This article is general information, not legal advice. TCPA compliance depends on your specific use case, your dialer configuration, and the jurisdictions you call into. When the stakes are real, consult a TCPA-specialized attorney.