The Federal Floor This Guide Builds Past
This site already covers the federal TCPA framework in full elsewhere: per dnc.com, B2B calls and texts are not exempt, an autodialed or prerecorded contact to a wireless number requires prior express written consent regardless of B2B status, and penalties run $500 per call for a negligent violation up to $1,500 for a willful one, with the FTC’s Telemarketing Sales Rule adding up to $51,744 per violation on top. None of that gets restated here. What this guide covers is the layer most agencies never budget for: individual states running their own telemarketing statutes on top of the federal floor, with Florida’s FTSA as the one confirmed, citable example.
Florida’s FTSA: A State Penalty Layered on Top of Federal Exposure
The Florida Telephone Solicitation Act, codified at Fla. Stat. Section 501.059, adds $500 to $1,500 in penalty exposure per call or text on top of whatever federal TCPA exposure already applies to the same contact, per LeadCompliant. The number is not a typo of the federal figure, it is a separate, additive state penalty. The FTSA also carries a private right of action, which changes the practical risk profile meaningfully: a federal TCPA violation is typically pursued by the FCC or through a class action that has to organize itself, while an FTSA violation gives an individual recipient standing to sue directly, on their own, without waiting for a regulator to act first.
Why “We Don’t Have a Florida Office” Doesn’t Help
The FTSA’s trigger is the phone number, not the agency’s location. It applies to any number assigned to a Florida resident or business, regardless of where the agency sending the text is headquartered or where its BD team is sitting when the message goes out. An agency in Austin texting a Florida area code is squarely inside the statute’s reach the same way a Florida-based agency would be. That is a meaningfully different rule than most agencies assume when they think about “state law” risk as a function of their own office address rather than the recipient’s.
Other States Run Their Own Statutes Too, Starting With Oklahoma
Florida is not the only state with its own telemarketing act, and it should not be treated as if it were. Oklahoma is confirmed to run its own state telemarketing statute, separate from federal TCPA, though the specific penalty structure and private-right-of-action detail for Oklahoma’s law were not independently confirmed in the research behind this guide. That gap is stated plainly rather than papered over with an invented figure: tracking every state’s telemarketing statute in full is a genuinely large undertaking, and a state-by-state legal review is the right next step before scaling a text-outreach list nationally, not a substitute this guide is trying to be.
What a Multi-State Texting List Has to Check
Segmenting a list by area code is not a reliable proxy for a number’s actual assigned state, since number portability lets a person keep an old area code after moving, which means area-code-based geo-filtering can both miss real Florida numbers and flag numbers that were never Florida-assigned. The more defensible check runs against the number’s actual current assignment, not its area code’s historical association with a state.
For an agency running outreach across multiple states, the practical takeaway is that “is this list TCPA-compliant” and “is this list also clear of every state mini-TCPA law that might apply to it” are two different questions, and the second one does not get answered by clearing the first.
Building a Standing State-Law Check Into the Outreach Process
- Confirm whether any number on an outreach list is assigned to a Florida resident or business, independent of area code, before treating federal TCPA clearance as sufficient.
- Document consent specifically for any Florida-assigned number, since the FTSA’s private right of action means an individual recipient can act without a regulator involved.
- Before scaling into a new state’s numbers at volume, check whether that state runs its own telemarketing statute, rather than assuming Florida is the only one that matters.
- Treat “we’re not based there” as irrelevant to a number-based statute like the FTSA. Location of the caller is not the trigger.
- Keep the consent record retrievable per number, not just per campaign, since a state-specific claim will ask about the specific contact, not the campaign as a whole.
Where a Documented Consent Record Does Double Duty
A consent record built to satisfy federal TCPA tends to satisfy most of what a state mini-TCPA claim asks for too, which is the practical reason to build one thorough record rather than maintaining a separate compliance posture per state. Human + AI SDRs document every SMS conversation, consent included, as a timestamped transcript on the VA Horizon Private CRM, the same record whether the number on the other end is assigned to Florida, Oklahoma, or anywhere else.
What this means for you
- Florida’s FTSA, Fla. Stat. Section 501.059, adds $500 to $1,500 per call or text on top of federal TCPA exposure, with a private right of action letting a recipient sue directly.
- The FTSA applies based on the phone number’s assignment to a Florida resident or business, not the agency’s own physical location, so having no Florida office does not exempt an agency from it.
- Oklahoma is confirmed to run its own separate telemarketing statute; the exact penalty structure was not independently confirmed here, and other states may run similar laws worth checking before scaling a list.
- Area-code-based geo-filtering is not a reliable way to identify Florida-assigned numbers, since number portability lets a person keep an old area code after moving states.
Sources
The external data in this guide draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.
- LeadCompliant, Business-to-Business Telemarketing Rules
- dnc.com, Are B2B Calls Exempt From TCPA Regulations?