Pennsylvania’s Telemarketing Law Just Woke Up.
Pennsylvania's telemarketing law hadn't moved since 1996. On October 18, 2026, it moves. And it brings texts, ringless voicemail, and AI voice with it.
That's the whole story in two sentences. The Pennsylvania Telemarketer Registration Act sat virtually untouched for thirty years while the way businesses actually reach consumers changed completely. The 2026 amendments (SB 992) drag it into the present and line it up much closer to the federal Telephone Consumer Protection Act.
If you call or text consumers in the Commonwealth, the landscape you memorized is gone (and yes, October 18 lands right in the teeth of Q4 outreach season). But, there's one thing you need to understand before you touch a single line of your outreach playbook: prior express written consent is the switch that turns most of these new obligations off.
Get the switch right and a lot of this stops being your problem. Get it wrong and you're honoring calling-hour restrictions, robocall rules, and registration questions you thought didn't apply to you.
Let's walk through what actually changed, who it hits, and what to do about it before the 18th.
What the old law did (and didn't) cover
The Act requires telemarketers to register with the Pennsylvania Office of the Attorney General. "Telemarketing" was defined narrowly: a plan, program, or campaign to induce the purchase of goods or services that involves more than one telephone call.
Read that again. More than one telephone call. Under the old statute, only voice calls counted. Text messages weren't covered. Ringless voicemail wasn't covered. A prerecorded message delivered any way other than a live-dialed call lived in a gray zone.
That's the world a lot of marketing teams built for. It's the world that ends on October 18.
What changes on October 18, 2026
The amendments rewrite the definitions to match how outreach actually works in 2026. Three changes carry almost all the weight.
Texts and ringless voicemail are now solicitations
"Telephone solicitation" is redefined to include "a telephone call, voicemail, ringless voicemail or text message made to a residential, business, or wireless telephone subscriber for the purpose of soliciting the sale of consumer goods or services."
Translated for 2026: the channel doesn't matter anymore. Voice, SMS, ringless drop — if it's selling something, it's a solicitation. The single-channel loophole is closed.
The consent standard is now "prior express written consent"
The redefined solicitation rules carve out any call or message made with the consumer's prior express written consent. And Pennsylvania's definition tracks the federal one at 47 C.F.R. § 64.1200(f) — the same "clear and conspicuous" written agreement, tied to a specific number, with the consumer's signature (ink or electronic), and no requirement that they consent as a condition of buying anything.
This is the switch. A contact backed by prior express written consent falls outside the solicitation rules. A contact without it is a solicitation, full stop, and every restriction below attaches to it.
The robocall definition now captures AI voice
The old "robocall" definition assumed a computerized autodialer delivering a prerecorded message. The amended definition reads: "a telephone solicitation that uses an automated dialing system to deliver prerecorded or artificial voice calls or messages."
Artificial voice. That's AI voice, named in the statute in everything but marketing copy. More on what that means in a minute — because it runs on the same switch as everything else.
The registration carveout helps. Just not as much as you'd hope.
Here's the part most licensed operators will misread. The amendments add a new exemption from the registration requirement for "a person or business engaged in a business or occupation licensed, certificated by or registered with a Federal or Commonwealth agency while acting within the scope of the business for which licensure, certification, or registration is required."
So a licensed business — a real estate brokerage, an insurance agency, a mortgage shop — gets meaningful room to run. When licensed personnel (not unlicensed team members) make the calls or texts, and the contact is within the scope of the licensed activity, ordinary outreach carries no registration burden. Good news, and real.
But, the carveout covers registration only.
Does clearing the registration exemption also clear you of the calling-hour rules and the consent rules? No.
The license gets you out of the registration line. It does not get you out of the solicitation rules. Different door entirely. A licensed agent texting a consumer who never gave prior express written consent is making a telephone solicitation, and every timing and consent restriction applies to that text exactly as it would to an unlicensed telemarketer's.
That distinction (registration relief versus solicitation relief) is where the compliant operators separate from the relieved ones.
The solicitation rules that attach without consent
For any contact that is a solicitation, meaning no prior express written consent on file, then the Do Not Call provisions of amended Act tightens the timing screws.
No solicitations on a Sunday. None before 9 a.m. or after 7 p.m. None on a legal holiday. These windows are measured against the consumer's local time, and they're stricter than the federal 8 a.m.–9 p.m. band most teams calibrate to. If your dialer or your SMS platform is set to federal hours, it's now out of compliance in Pennsylvania on Sundays, holidays, and the evening shoulder every single day.
Then there's the price of getting it wrong. Pennsylvania's civil penalties run up to $1,000 per call, and up to $3,000 per call where the person on the other end is 60 or older. Per number. Do the math on a list of any size, then remember the plaintiffs' bar reads these statutes for a living.
AI voice runs on the exact same switch
The expanded robocall definition captures AI voice. But, only for telephone solicitations.
That's the whole ballgame for anyone deploying conversational AI or artificial-voice outreach into Pennsylvania. Run it against consumers who gave prior express written consent, and the robocall requirements don't trigger — the contact isn't a solicitation. Run it against consumers who didn't, and you've triggered the full robocall regime: the opt-out procedure, the interactive opt-out mechanism, the toll-free callback in any voicemail the system leaves.
Same technology. Same script. The consent status of the number you're dialing is the only thing that decides which set of rules you live under. AI voice doesn't get a special lane in Pennsylvania. It gets the consumer's consent status, same as every other channel. This makes the audit trail for your AI voice even more important.
What to do before October 18
This is a consent problem wearing a registration costume. Four moves, this week:
Pull your consent records and sort by state. For every Pennsylvania number, ask one question: can you produce prior express written consent that meets the federal § 64.1200(f) standard? If you can't, treat every contact to that number as a solicitation and route it accordingly.
Reset your calling windows for Pennsylvania. No Sundays, no legal holidays, 9 a.m. to 7 p.m. in the consumer's local time. Set the guardrail at the platform level, not in a training deck nobody reads.
Stop assuming your license is a shield. If you're a licensed brokerage or agency leaning on the registration carveout, map which of your contacts actually ride on consent versus which are cold solicitations. The carveout may cover your registration; it does not cover the cold ones.
Audit your AI voice deployments against consent status, not against the tech. If artificial-voice outreach touches non-consented Pennsylvania numbers, the robocall requirements may apply to you the day the amendments take effect. Build the opt-out plumbing now, not after the first demand letter.
The throughline never changes: consent is the switch. Everything downstream of it (hours, channels, robocall duties, the registration question itself) gets easier or harder depending on whether you can prove it.
Get the consent architecture right, once
The discrete answer here is simple: prior express written consent turns most of Pennsylvania's new obligations off. The harder problem is proving you have it, at scale, across every number and every channel, in a form that holds up when someone comes looking.
That's a system, not a checkbox.
Building consent flows that meet the § 64.1200(f) standard and generate the records you'd want to hand a regulator is exactly the kind of work a Consent Architecture engagement is built for. If you're calling or texting into Pennsylvania and you're not certain your consent would survive a challenge, that's a conversation worth having before October 18 — not after a plaintiff's lawyer has it for you.
