Oklahoma Telemarketing Law for Insurance Agents (2026)

If you sell insurance in Oklahoma, the state’s own TCPA-like telemarketing law almost certainly does not apply to you. Section 775C.5 of the Telephone Solicitation Act of 2022 lists 26 categories of callers exempt from its consent requirement, its 8 a.m. to 8 p.m. calling window, and its three-call-per-day cap, and the eighth one on that list is “any licensed insurance broker, agent, customer representative, or solicitor when soliciting within the scope of his or her license.” That’s not a loophole someone found. It’s written directly into the statute the Legislature passed in 2022.

That single fact changes almost nothing about what you actually need to do, and it’s worth being honest about why up front: Oklahoma is one state out of fifty, the federal Telephone Consumer Protection Act sits on top of every state’s law regardless of what that state exempts, and Oklahoma itself runs a second telemarketing statute, its own do-not-call registry, that does not carve out insurance at all. An agent who reads “exempt” and stops there is building a compliance program on a headline instead of a statute.

What Oklahoma actually has on the books, and there are three separate laws

Most of the coverage of state telemarketing law treats “Oklahoma’s telemarketing law” as one thing. It isn’t. Title 15, Chapter 20 of the Oklahoma Statutes contains three distinct acts, passed in three different years, each with its own scope and its own exemptions, and an insurance agent’s obligations are different under each one.

The Commercial Telephone Solicitation Act, the oldest of the three, requires a “commercial telephone seller” to register with the Attorney General at least ten days before conducting business in the state, post a $10,000 bond, and pay a filing fee, per Section 775A.3. It bans specific deceptive practices, misrepresenting a prize, faking a “free” offer, blocking caller ID, and ties any violation to the Oklahoma Consumer Protection Act. Section 775A.2(1)(g) exempts “a person or an affiliate of a person who is regulated by the Insurance Commission pursuant to Title 36 of the Oklahoma Statutes” from the entire act, which means a licensed insurance business doesn’t register, doesn’t bond, and doesn’t file with the Attorney General under this statute at all.

The Telephone Solicitation Act of 2022, created by House Bill 3168 and effective November 1, 2022, is the TCPA-shaped one, and it’s the statute most agents mean when they ask about “Oklahoma’s telemarketing law.” It requires prior express written consent before a commercial telephonic sales call uses an automated system to select or dial a number, or plays a recorded message on connection, per Section 775C.3(A). It bans calls outside 8 a.m. to 8 p.m. local time and caps solicitation calls at three per 24-hour period on the same subject matter, regardless of which number placed the call, per Section 775C.4. And per Section 775C.5, it exempts 26 categories of callers from all of it, including, at paragraph 8, “any licensed insurance broker, agent, customer representative, or solicitor when soliciting within the scope of his or her license.”

The Telemarketer Restriction Act, in force since the Attorney General built the registry by January 1, 2003 under Section 775B.3, is Oklahoma’s own state-level do-not-call list, separate from the FTC’s national one. A telemarketer cannot call a number more than 30 days after it first appears on the registry, per Section 775B.6, unless the caller and consumer have an established business relationship formed within the preceding 24 months, per Section 775B.2(3). This act’s definition of “telemarketer” is broad: any person who, for commercial purposes, initiates a telemarketing sales call to an Oklahoma consumer. Nothing in Sections 775B.1 through 775B.7, as published by the Attorney General’s office, lists an exemption for licensed insurance producers the way the other two acts do.

Why Oklahoma wrote the exemption in the first place

Look down the full list of Section 775C.5’s 26 exemptions and a pattern shows up fast: banks, credit unions, and securities brokers are on it too, alongside insurance producers, real estate licensees, and funeral service providers. None of that is random. Every one of those categories is already licensed and supervised by a separate state or federal regulator before a telemarketing statute ever enters the picture. A securities broker answers to the SEC and FINRA. A real estate agent answers to the Oklahoma Real Estate Commission. An insurance producer answers to the state’s own insurance regulator, which already sets licensing standards, conduct rules, and discipline procedures specific to selling insurance by phone.

The Legislature’s choice, in other words, wasn’t “insurance calls are less risky than other sales calls.” It was “this industry already has a regulator watching how it solicits, so a second, generic telemarketing statute on top of that regulator’s own rules would duplicate oversight that already exists.” That’s the same logic McCarran-Ferguson applies at the federal level for the business of insurance generally: when a state actively regulates an activity as insurance business, federal rules built for the broader marketplace step back rather than stack on top. Oklahoma’s Legislature made the same call for its own state telemarketing statute, just by naming insurance producers directly in the exemption list instead of leaving it to a McCarran-Ferguson analysis every time.

That rationale explains why the carve-out exists, and it also explains its limits. The exemption tracks the license, not the caller’s intent or the caller’s platform. A licensed producer soliciting insurance is inside the regulatory system the Legislature was deferring to. The same producer’s AI calling vendor, considered on its own, isn’t a licensed insurance entity and doesn’t inherit the exemption independently; it inherits it only through the licensed producer or agency actually placing the call under that license. That’s a distinction worth having in writing if you outsource any part of your dialing to a third party, so it’s clear whose license the exemption is actually running through.

What “soliciting within the scope of your license” actually means

The exemption’s own text does the scoping for you, and it’s narrower than “I have a license” might suggest. Oklahoma insurance licenses are issued by line of authority: life, accident and health, property, casualty, and so on. A producer licensed for life and health who calls an Oklahoma lead about a Medicare Supplement or a final expense policy is squarely within scope. The same producer calling that same lead to pitch a homeowners policy they aren’t licensed to sell isn’t soliciting “within the scope of his or her license” for that call, whatever the exemption says about insurance producers generally.

This matters most for agencies running multiple lines through one calling operation. If your agency licenses some producers for life and health and others for property and casualty, and your dialer routes leads by list rather than by the calling producer’s actual line of authority, you can end up with calls that are exempt on one line and not exempt on another, from the same campaign, on the same day. The fix isn’t complicated: tag each list by the line of authority it requires, and make sure whichever license, human or the AI platform’s disclosed principal, is placing the call actually covers that line. It’s a data-hygiene problem before it’s a compliance problem, and it’s the kind of thing worth auditing once rather than assuming is already correct.

A solicitor role adds one more wrinkle. Section 775C.5(8) extends the exemption to a “customer representative, or solicitor,” not just a broker or agent, which covers more of a typical call center’s staff than the narrower reading some agencies assume. But “licensed by an official or agency of this state or of any state” still requires an actual license behind that role. An unlicensed setter or a script-reading dialer operator without any producer license doesn’t inherit the exemption just by working for a licensed agency; Oklahoma’s statute exempts the license, not the employer.

The “automated system” problem, and why it matters more for an AI caller

Even for a caller this exemption doesn’t cover, Section 775C.3 has its own ambiguity that industry counsel flagged when House Bill 3168 was moving through the Legislature: the act prohibits an automated system “for the selection or dialing of telephone numbers” without defining what qualifies as automated selection. A traditional predictive dialer randomly or sequentially generating numbers is the obvious case the TCPA’s own federal definition was built around. Whether a system that automatically selects the next number from an indexed, previously compiled customer or lead list, the way most CRM-driven dialers and AI calling platforms actually work, counts as the same kind of “automated system” is a question the statute’s text doesn’t resolve on its own.

For a licensed insurance producer, this ambiguity doesn’t matter much; Section 775C.5(8) exempts you from the whole section regardless of how “automated system” gets interpreted. It matters more for anyone in an Oklahoma calling operation who isn’t covered by that exemption, an unlicensed setter, a lead-gen vendor calling ahead of the licensed producer, or a shared call center working multiple clients’ lists. If any part of your Oklahoma operation includes calling that isn’t happening under a licensed producer’s own scope, don’t assume the statute’s silence on “automated system” works in your favor. Build toward the stricter reading, prior express written consent before automated selection or dialing of any kind, rather than betting a court reads the ambiguity narrowly.

The exemption, in the statute’s own words

Here is Section 775C.5(8) of the Telephone Solicitation Act of 2022, exactly as the Oklahoma Legislature enrolled it in House Bill 3168:

Two things about that wording matter for how you actually use it. First, the license doesn’t have to be Oklahoma’s own; a producer licensed by any state’s insurance regulator qualifies, which matters if you’re calling Oklahoma numbers from an agency licensed elsewhere. Second, the exemption is scoped to soliciting “within the scope of” that license. A licensed life and health producer calling about a life or health product is squarely inside the exemption. The same person cold-calling about an unrelated product line they aren’t licensed to sell is a harder argument, and it’s not one this article can settle for you; that’s a scope question for your own counsel if your book of business crosses lines you’re not licensed for.

For comparison, here’s what the older Commercial Telephone Solicitation Act says at Section 775A.2(1)(g), which is a narrower carve-out covering only that act’s registration and bonding requirement, not consent or calling hours: “a person or an affiliate of a person who is regulated by the Insurance Commission pursuant to Title 36 of the Oklahoma Statutes.”

What still applies, no matter what Oklahoma’s own statute says

This is the part that gets skipped when a state exemption makes the news. Oklahoma’s exemption changes what an Oklahoma court can hear under an Oklahoma statute. It has no power over federal law, and it has no power over the one Oklahoma statute that didn’t exempt you in the first place.

The federal TCPA still requires consent. Under 47 U.S.C. Section 227(b)(1)(A), an autodialed or artificial-voice call to a wireless number needs prior express consent, and a marketing call needs that consent in writing, according to Cornell Law School’s Legal Information Institute. The FCC enforces this independent of any state’s own telemarketing statute, and the exemption you just read doesn’t reach it. A licensed producer calling an Oklahoma cell number with an AI voice and no consent on file is exempt from Section 775C.4’s calling-hours rule and still exposed under Section 227.

The FCC already ruled that an AI voice counts. On February 8, 2024, the FCC adopted a Declaratory Ruling holding that a call placed with an AI-generated voice is an “artificial” voice for TCPA purposes, the same category that’s covered a prerecorded message for decades. An AI calling platform doesn’t get a separate, lighter rulebook because the voice on the call is synthetic rather than a human read from a script.

Oklahoma’s own do-not-call registry doesn’t carve you out. The Telemarketer Restriction Act’s exemptions, as published by the Attorney General, don’t include the insurance-producer language that shows up in the other two acts. If an Oklahoma consumer’s number has been on that registry for more than 30 days and you don’t have an established business relationship with them formed in the preceding 24 months, Section 775B.6 treats the call as an unlawful telemarketing practice regardless of your license.

Whether the federal Do Not Call Registry and the Telemarketing Sales Rule apply to a given insurance call is its own question, not a blanket yes or no. The FTC’s own Advisory Opinion 03-1, issued August 19, 2003, lays out a McCarran-Ferguson test: the Telemarketing Sales Rule doesn’t reach an activity that qualifies as “the business of insurance” under a state’s own regulatory scheme, but that’s an activity-by-activity determination, not an industry-wide exemption, and it doesn’t extend to a third-party telemarketer just because the entity that hired them is otherwise exempt. Don’t assume this settles the question for your specific setup; it’s exactly the kind of scope call worth running past counsel who’s looked at how you actually place the call.

CMS layers its own rules on top for Medicare business. None of Oklahoma’s three statutes, or the federal TCPA, touches CMS’s separate Medicare marketing framework, which carries its own TPMO disclaimer, recording-retention, and unsolicited-contact rules for Medicare Advantage and Part D business. If part of your book is Medicare, the exemption discussed in this article changes nothing about that layer.

What one wrong assumption actually costs

The realistic failure mode here isn’t an agency deliberately ignoring the law. It’s an agency that reads “Oklahoma exempts insurance agents” somewhere, correctly, and stops reading. They assume that sentence covers the do-not-call registry too, because it sounds like the same subject. It doesn’t. They assume it covers a text campaign the same way it covers a call, when the exemption’s own scope language, “within the scope of his or her license,” never got checked against what’s actually being sold on that particular campaign. Or they assume a state exemption from a state statute also covers the federal TCPA, because nobody separated the two rulebooks out loud.

None of those assumptions are unreasonable to make once. They’re expensive to make in production, at volume, across a list of a few thousand numbers, because a private right of action under either 775C.6 or 47 U.S.C. Section 227(b)(3) runs per call or per text, not per campaign. A single Oklahoma consumer who was on the state do-not-call registry for 45 days, in a subject area you’d never established a relationship with, and who received an autodialed follow-up call without TCPA-compliant consent on file, is a fact pattern that could support claims under two different statutes at once, and the insurance exemption in Section 775C.5 answers for exactly none of it.

Run the arithmetic and the asymmetry is stark. A three-minute follow-up call at TheAffordableAI’s published Single Account rate of $0.20 a minute costs 60 cents to place. One federal TCPA violation on that same call, if it turns out consent wasn’t actually on file, carries a statutory floor of $500, and up to $1,500 if a court calls it willful, per 47 U.S.C. Section 227(b)(3). That’s not a rounding error against the cost of the call; it’s roughly 800 to 2,500 times the cost of the call itself, for the exact same three minutes, and it has nothing to do with whether Oklahoma’s own Section 775C.5 exemption applied to the state-law side of that same call.

How to build the calling cadence, step by step, without buying anything yet

None of this requires new software to get right. Every step below runs on a spreadsheet, a CRM export, and a decision you make once and document.

1. Confirm the license actually covers what you’re calling about. Section 775C.5(8)‘s exemption is scoped to soliciting “within the scope of” the license. Pull your own producer license and match it against the product line in the campaign before you assume the exemption applies to that specific list.
2. Screen every Oklahoma number against the state do-not-call registry separately from the national one. They’re different lists, run by different agencies, and only one of Oklahoma’s three statutes is the one without a producer exemption. Treat the 775B registry as fully binding.
3. Keep prior express written consent on file anyway, even though 775C doesn’t require it from you. The federal TCPA does, for any autodialed or artificial-voice call to a wireless number, and Oklahoma’s state exemption never touches that requirement. Building one consent record instead of two rulebooks in your head is simpler and it’s the one that actually protects you.
4. Document the established-business-relationship basis for any repeat contact, if you’re relying on it. Under Section 775B.2(3), that’s a relationship formed by voluntary two-way communication in the preceding 24 months. Keep the date and the nature of that first contact on the lead record, not just a checkbox.
5. Separate your Medicare business from everything else, in your CRM tags, not just in your head. CMS’s rules apply on top of all three Oklahoma statutes and the federal TCPA, and none of the exemptions discussed here reach Medicare marketing requirements.
6. If you’re licensed outside Oklahoma and calling Oklahoma numbers, confirm your out-of-state license still qualifies. Section 775C.5(8)‘s definition covers a producer “licensed by an official or agency of this state or of any state of the United States,” which is broader than most agents assume, but it’s worth confirming against your actual license type before you rely on it at volume.

You can run all six steps with tools you already have, and plenty of agencies do exactly that instead of changing anything about how they dial.

The CMS layer sits on top, separately

If any part of your Oklahoma book touches Medicare Advantage or Part D, nothing in this article substitutes for CMS’s own Medicare marketing rules, which carry their own TPMO disclaimer language, call-recording retention period, and restrictions on unsolicited contact, independent of everything covered above. The CMS 2027 Medicare marketing rules guide on this site walks through that layer specifically, and the GoHighLevel workflow guide covers building a trigger-to-warm-transfer flow that logs consent and disposition automatically, whichever of Oklahoma’s statutes ends up governing a given campaign.

Where TheAffordableAI fits

Deciding which of Oklahoma’s three statutes governs a given call, and whether a given campaign sits within your license’s scope, is a legal and licensing judgment, and no vendor, including us, makes that call for you. Where a managed AI caller helps is in what happens once you’ve made that decision: every call TheAffordableAI places gets logged against the lead’s record automatically, including disposition, consent status, and any opt-out language spoken on the call, and that log syncs natively with HighLevel instead of sitting in a dialer’s local history that nobody exports. You can configure calling windows and frequency caps as system rules once, based on whichever rulebook you’ve decided actually applies to a given list, rather than trusting each dial to happen inside the right hours by memory. The full list of what’s included on every plan is on the features page.

Where a rule change doesn’t help, and where you still need a lawyer

It would be dishonest to sell this as a technology problem, because most of it isn’t one. The genuinely hard part of Oklahoma’s exemption is a scope question: does a specific campaign fall “within the scope of” a specific producer’s license, and does a specific call fit the McCarran-Ferguson “business of insurance” test the FTC’s own advisory opinion lays out for the separate question of federal Do Not Call and Telemarketing Sales Rule coverage. No AI caller and no CRM feature answers either question. Those are license-scope and regulatory-classification calls that belong to someone who has actually looked at your book of business and your calling method, ideally counsel who’s read Sections 775A, 775B, and 775C themselves rather than a summary of them, including this one.

If your agency already runs a tight, documented consent process because you sell into other states without Oklahoma’s exemption, you likely don’t need to change much for Oklahoma specifically beyond confirming the state do-not-call registry screening is separate from the national one. Spending money on new tooling to solve a compliance gap you don’t actually have isn’t a good trade, and it’s worth ruling that out before assuming a bigger system is the answer.

Oklahoma really did write an insurance exemption into its 2022 telemarketing law, and if you’re a licensed producer soliciting within your own scope, Section 775C.5(8) means that statute’s consent rule, its calling-hours window, and its three-call cap don’t reach you the way they reach an unlicensed telemarketer. What Oklahoma didn’t do is exempt you from the federal TCPA, from its own separate do-not-call registry, or from the judgment call about whether a specific campaign actually sits inside your license’s scope. Read the exemption for what it says, not for what a headline about it implies, and the rest of your calling program looks the same as it would in a state that never wrote the carve-out at all.