Arizona Telemarketing Law for Insurance Agents (2026)

Yes, Arizona’s do-not-call statute applies to insurance agents, it covers text messages as well as calls since a 2023 amendment, and it offers no exemption for insurance producers the way it does for real estate licensees. A.R.S. §44-1282 bars a “seller, solicitor, or anyone acting on their behalf” from initiating an outbound telephone solicitation call or text message to any number on the National Do Not Call Registry, and the Arizona Attorney General can pursue a civil penalty of up to $1,000 per violation. That’s state law, running on top of the federal Telephone Consumer Protection Act, not instead of it, and most agencies working Arizona leads are only thinking about one of the two.

The gap is understandable. Arizona’s statute is short, mechanical, and doesn’t get the same coverage as, say, Florida’s Telephone Solicitation Act or Texas’s no-call list. But it’s enforceable, it’s specific about who’s exempt, and the 2023 amendment that added text messages to the prohibition changed what “compliant” means for any agency that texts leads, renewals, or quotes into the state. What follows is what the statute actually says, who it reaches, what a violation costs when you stack the state penalty on top of federal exposure, how to build a list that’s actually clean, and where an AI caller fits once compliance and speed stop being a tradeoff.

What Arizona’s Telephone Solicitation Statute Actually Says

Arizona regulates telemarketing through Title 44, Chapter 10 of its revised statutes, and two sections matter most for an insurance agency: §44-1271, which defines the terms the rest of the chapter uses, and §44-1282, which sets the do-not-call prohibition and its penalty.

§44-1271 defines “telephone solicitation” broadly: “any voice communication from a live operator, announcing device or otherwise” that offers merchandise for sale or rent, placed to or from a person located in Arizona. That definition doesn’t distinguish between a live agent dialing from a script, a predictive dialer, or an AI voice agent placing the call. “Merchandise” under the same section covers physical items, intangibles, real estate, securities, and services, which is broad enough to include an insurance policy, a quote, or a plan comparison. If you’re calling someone in Arizona to offer them coverage, you’re almost certainly placing a “telephone solicitation” as the statute defines it, regardless of how the call gets dialed.

§44-1282 is where the actual prohibition lives, and its current text, as amended by House Bill 2498 in 2023, is specific:

Read the exemption language carefully, because it’s the detail most agents miss. The carve-out in §44-1282(A)(1) through (3) doesn’t exempt “insurance agents” or “licensed professionals” in general. It names a specific licensing chapter: Title 32, Chapter 20, which is real estate brokers and salespersons. Arizona’s insurance producers are licensed under an entirely different part of the code, Title 20, the insurance title. There’s no equivalent paragraph in §44-1282 naming Title 20 licensees. If you’re an Arizona-licensed insurance agent calling a number on the national registry, the statute’s own exemption list simply doesn’t include you, the way it includes a real estate agent calling about a past listing agreement.

Why the Text Message Change Actually Matters

Before House Bill 2498 took effect in April 2023, §44-1282 addressed telephone solicitation calls. A text pitching a quote or a policy to a number on the registry sat in a genuine gray area under the old statutory language, even if federal law already had something to say about it. The 2023 amendment closed that gap at the state level by rewriting the prohibited conduct to explicitly include “a text message,” using the same statutory machinery, the same registry, and the same $1,000-per-violation penalty that already applied to calls.

That’s a mechanism worth understanding on its own, not just a footnote to the call rule. A2P text campaigns, drip sequences, and automated SMS follow-ups have become standard tools for insurance lead follow-up precisely because they’re fast and cheap to send at volume. The same qualities that make text effective for speed to lead make a non-compliant blast expensive to run in Arizona: every text to a registered number is now its own potential $1,000 exposure under state law, stacked on whatever the number of texts actually sent works out to.

How Arizona Stacks on Top of Federal Law

This is the piece that actually drives cost exposure, and it’s where most of the real risk hides, because Arizona’s law and federal law are answering two different questions with two different penalty schedules, and both apply to the exact same phone call.

The federal Telephone Consumer Protection Act, codified at 47 U.S.C. §227, makes it unlawful to place a call using an automatic telephone dialing system or an artificial or prerecorded voice to a cell phone without the called party’s prior express consent, with narrow exceptions for emergencies and certain debt collection calls. Enforcement runs through a private right of action: a consumer can sue for an injunction, actual monetary loss, or $500 per violation, whichever is greater, and a court can treble that figure to $1,500 per violation for a willful or knowing violation. That’s federal law, enforced by whoever received the call, independent of Arizona’s registry rule.

Arizona’s §44-1282 asks a narrower, different question: was this specific number on the National Do Not Call Registry, and did a seller or solicitor without an applicable exemption call or text it anyway? That’s a state-law violation enforced by the Arizona Attorney General, capped at $1,000 per violation under §44-1531, regardless of whether the call also happened to comply with the TCPA’s separate consent rules.

Stack the two and a single non-compliant call to a registered Arizona number, placed without consent and without an applicable exemption, can carry state exposure up to $1,000 and separate federal exposure of $500 to $1,500, from two different enforcement bodies, for the same ten seconds of dialing. That’s not a reason to panic over any one dial. It’s the reason “we’re TCPA compliant” and “we’re compliant in Arizona” are two separate sentences that both need to be true, not one sentence that implies the other.

What It Actually Costs to Get This Wrong

There’s no published figure for “average Arizona insurance agency telemarketing exposure,” and this piece won’t invent one. What’s real and sourced is the scale of the registry itself and the maintenance burden that creates for any agency calling or texting into the state.

The FTC’s Do Not Call Data Book 2025, published December 2025 with data as of September 30, 2025, states plainly that the registry has continued to grow since its 2003 launch and held roughly 259 million active registrations as of that date. The same document is explicit about the scrubbing obligation: “Telemarketers and sellers must remove numbers added to the Registry from their call lists at least every 31 days.” A purchased lead list, an aged database being reactivated, or a referral list built from past clients all need to run through that same 31-day scrub, every time, for the life of the campaign, not once at intake.

Set that against the economics of the people doing the dialing. The U.S. Bureau of Labor Statistics puts the median annual wage for insurance sales agents nationally at $62,280, or about $29.94 an hour, based on May 2025 data, with roughly 572,600 people employed in the occupation. That’s the cost of the staff time spent building, scrubbing, and re-scrubbing a compliant calling list by hand, on a 31-day cycle, on top of actually making the calls. A missed scrub cycle isn’t just a compliance question; it’s that same producer’s time being spent on cleanup instead of calls, the same tradeoff that shows up every time manual compliance work competes with manual selling work for the same hours.

Who Actually Carries the Risk: Agency, Vendor, or Both

§44-1282’s prohibition reaches a “seller, solicitor, or anyone acting on their behalf,” which is deliberately wide language. It’s not limited to whoever physically places the call. An agency that buys a list from a lead vendor, hands it to a call center, or runs it through a third-party dialer hasn’t moved the compliance obligation off its own books just because someone else is doing the dialing. “Acting on their behalf” is built to catch exactly that arrangement.

This matters most in three common insurance-agency setups:

Buying shared or aged leads from a vendor. If the vendor’s own consent documentation is thin, missing, or simply unverifiable, you’ve bought someone else’s compliance gap along with the lead. The agency calling the number carries the practical exposure, whatever the vendor’s lead-gen page claims about its own consent process.

Outsourcing follow-up to a call center or virtual assistant team. Whoever actually dials still needs a clean, re-scrubbed list and a documented lawful basis for each call. Handing a list to an outside team doesn’t create a new exemption; it just adds a layer between the agency and the dial that still needs to be accountable for the same statute.

Running a multi-producer agency where different people pull from the same database. A shared contact list that one producer scrubbed last month and another producer is now dialing from isn’t “scrubbed” in any way that protects the second producer’s calls. The 31-day clock runs against the list as it’s actually used, not against whoever happened to run the last export.

How to Build a Compliant Arizona Calling List Yourself

This part is worth doing properly even if you never touch an AI caller, because the underlying discipline is the same regardless of who’s dialing.

Step 1: Treat the National Do Not Call Registry as the floor, not the whole picture. Arizona’s §44-1282 incorporates the federal registry directly, so your scrub needs to check the actual national database, not a state-specific or locally-maintained list that might be stale or incomplete. Telemarketers access the registry through the FTC’s own telemarketing.donotcall.gov portal.

Step 2: Re-scrub on a cycle no longer than 31 days, for the life of the campaign. The FTC’s own guidance sets this as a hard maximum, not a best practice. A campaign that runs for three months needs at least three scrubs, timed to the calendar, not just one scrub at the start.

Step 3: Know exactly which exemption, if any, actually applies to your call. Don’t rely on an assumed professional-courtesy carve-out. If you’re not licensed under Title 32, Chapter 20, the real estate exemption in §44-1282(A)(1)-(3) doesn’t apply to you. The call needs a different lawful basis: the consumer’s own prior express request, an applicable federal authorization, or documented consent that satisfies the TCPA separately.

Step 4: Log consent at the point of capture, not after the fact. A lead form, a quote request, or a referral that includes a clear, timestamped consent record is the asset that lets you call or text a number even if the number happens to be on the registry, because consent is the actual legal basis the exemptions and federal law both turn on. A list without that record has no way to tell a legitimate exception from a straightforward violation after the fact.

Step 5: Apply the same discipline to text as to calls. Since the 2023 amendment, there’s no lighter-touch version of this rule for SMS. If your agency runs text-based follow-up sequences into Arizona numbers, those sequences need the identical registry scrub and consent record that an outbound calling campaign would need.

If you want to see how a consent-aware calling and texting workflow is actually built end to end, see how it works.

How TheAffordableAI Handles This

TheAffordableAI’s managed AI caller runs outbound campaigns through a fleet of warmed Twilio numbers, rotating round-robin so no single number carries disproportionate volume, and syncs every call’s tags, disposition, transcript, and recording back to HighLevel automatically, per the platform’s own how-it-works and features pages. That operational discipline, built for number health and spam avoidance, is the same infrastructure a registry scrub and consent-logging workflow needs to run on: a system that already treats call pacing, number reputation, and record-keeping as first-class problems rather than afterthoughts.

None of this replaces the registry scrub itself or the Attorney General’s enforcement authority. What it removes is the operational excuse: “we didn’t have time to re-scrub this month” stops being a believable reason once the scrubbing, pacing, and record-keeping are built into the platform doing the dialing rather than depending on someone remembering to run it manually every 31 days.

If you want to hear what this actually sounds like before you decide anything, there’s a demo call on the homepage. theaffordableai.com

What You Get

A compliant Arizona calling program isn’t more complicated than a non-compliant one, it just has an extra, recurring step: knowing that Title 20 insurance licensure doesn’t buy you the same exemption Title 32 real estate licensure does, and treating the National Do Not Call Registry scrub as a 31-day recurring obligation rather than a one-time intake task. Get that right and you can call and text an Arizona list as aggressively as the lead flow justifies, with the state-law and federal exposure both accounted for instead of assumed away.

The math changes once that discipline is built into the system placing the calls, rather than depending on a producer remembering to run a scrub on schedule. The math above uses $0.20 a minute because that’s what a Single Account costs. Run it with your own numbers. See current pricing.

Frequently Asked Questions