TL;DR

  • Pennsylvania’s Act 47 of 2026 amended its Telemarketer Registration Act. Approved July 20 with a 90-day effective-date provision, it took effect October 18, 2026. This is enacted law, not a pending federal proposal.
  • The amended definition of telephone solicitation expressly includes texts, voicemail, and ringless voicemail. It also contains exclusions, including communications responding to qualifying prior express written consent.
  • The law defines that written consent around an agreement between the called party and the seller. A generic “consented” field does not show whether that definition is satisfied.
  • Covered telephone solicitations face a 9 a.m.–7 p.m. window and restrictions on Sundays and legal holidays. Apply the definition and exclusions before deciding how a restriction affects a campaign.
  • Evidence capture, suppression, scheduling, and registration review are separate controls. A consent record does not replace the others.

Overview

A lead can arrive with a reassuring label and still leave the buyer unable to answer the important questions: Which seller did the consumer authorize? What did the form say? Was the planned contact a text, a live call, or an automated voice message? Did the consumer later ask that seller to stop?

Pennsylvania’s updated telemarketing statute makes those distinctions especially relevant this week. Act 47 of 2026 changes definitions, consent language, contact restrictions, and other provisions in an existing state framework. Its effective-date clause is in section 5; the substantive amendments appear in sections 1–4.

For lead buyers and publishers, the useful response is not another universal compliance badge. It is a review of the evidence and decisions connecting a source interaction to an actual outreach attempt.

This guide separates the statutory changes from recommended operating practices. It is an operational overview, not a determination that a particular campaign qualifies for an exemption.

Start with the definition, not the headline

Act 47 replaces the older “telephone solicitation call” definition with “telephone solicitation.” The amended definition reaches calls, voicemail, ringless voicemail, and text messages used to solicit consumer goods or services, or obtain information that may be used for direct solicitation. That second purpose matters when an interaction is described as lead qualification rather than a sale.

But the definition also excludes specified communications. These include responses to prior express written consent, certain existing debt or contract communications, qualifying established business relationships within the preceding 12 months, and specified nonprofit or political communications. These are not interchangeable categories.

The practical implication is that “Pennsylvania lead” should trigger a classification decision, not one unqualified rule. Document the planned communication, the applicable facts, and any exclusion being relied on. A business relationship asserted by one participant in a lead chain should not simply be assumed to belong to every downstream buyer.

Likewise, do not treat the phrase “business number” as a universal escape hatch. The amended definitions and provisions expressly refer to business as well as residential and wireless subscribers. Have the relevant scope and exceptions evaluated for the actual campaign.

Source: Act 47, section 1, amended definitions.

The new prior-express-written-consent definition describes a written agreement between the called party and a seller authorizing that seller to initiate, or cause to be initiated, a solicitation, including robocalls or texts. It specifies the authorized telephone number, a clear and conspicuous disclosure, a statement that consent is not a purchase condition, and the called party’s signature. Electronic or digital signatures can qualify consistently with the referenced federal electronic-signature requirements.

For an acquisition team, the important question is whether the delivered record supports those elements. A database value saying consent=true is a conclusion. It does not identify the agreement or show how the consumer executed it.

Recommended acceptance evidence includes:

  • The seller identity presented during the consumer interaction.
  • The telephone number associated with that interaction.
  • The disclosure as displayed at that time, including purchase-condition language.
  • The consumer action used to execute the agreement.
  • A timestamp and source reference connecting those items to the delivered lead.
  • A retrievable copy of the relevant evidence, rather than a link that may later disappear.

That list is an evidence-design recommendation, not a claim that the statute mandates a particular recording product or file format. Nor does a recording automatically establish that the disclosure was adequate or the signature legally effective. The record makes review possible; it does not predetermine the answer.

For background on that distinction, see lead consent documentation.

Do not turn the calling window into a misleading absolute

The amended unlawful-acts section prohibits initiating or causing a telephone solicitation on Sunday, before 9 a.m., or after 7 p.m. It also prohibits telephone solicitations on legal holidays.

Those are significant operating constraints, but the defined term matters. It would be misleading to reduce the statute to “every marketing contact is forbidden after 7 p.m.” without considering the exclusions in the definition of telephone solicitation. It would be equally risky to conclude that a consent flag makes all timing controls unnecessary.

A practical implementation separates two decisions:

  1. Classification: Is the planned communication a covered telephone solicitation, or is a supported exclusion applicable?
  2. Execution: Which scheduling policy follows from that decision, and which other requirements still apply?

Use an explicit, reviewed policy for ambiguous records. Do not let an absent field silently become permission to send. Keep the facts supporting an exclusion with the decision so the team can explain why a message was released.

For scheduling operations, a conservative recipient-local-time policy can be useful, especially when location is uncertain. That is a recommended control, not an assertion that an area code conclusively establishes a person’s current location or that the statute supplies your software’s timezone algorithm.

Source: Act 47, section 3, amending section 5(a)(1) and (10).

Treat opt-outs as events that must reach the sending system

Act 47 expressly names several replies consumers can use to stop telephone-solicitation texts: stop, quit, end, revoke, opt out, cancel, and unsubscribe. It also addresses prior requests not to receive solicitations made by or on behalf of a seller or telemarketer.

The operational risk is often a handoff failure. A text platform receives a reply, but the CRM retains an active campaign status. A call center records an objection, but another sending system continues its queue. A publisher supplies an older consent record, and the buyer treats it as more current than a later suppression event.

Recommended controls should make those conflicts visible:

  • Record the incoming request, its time, and the receiving channel.
  • Route the event to the systems responsible for future contact.
  • Define which seller and campaign records must be updated.
  • Check suppression again when releasing queued messages or calls.
  • Retain enough history to show what the systems knew when they acted.

These are implementation recommendations, not a complete statement of every applicable revocation rule or deadline. The amended act also contains specific opt-out mechanics for robocalls, including an interactive mechanism and voicemail callback requirements. A text-only implementation does not address those voice requirements.

Source: Act 47, amendments to sections 5(a)(2) and 5.2(l).

Keep registration and campaign conduct in the review

Act 47 also revises registration provisions and reorganizes registration exemptions. A team should not assume that consent evidence alone resolves whether a seller, telemarketer, or service provider must register. Conversely, registration is not evidence that a consumer authorized a particular contact.

The amended act separately addresses robocalls without qualifying written consent, subject to stated exceptions; deceptive practices used to obtain consent; and technology or synthetic messaging used to defraud, deceive, or mislead. These provisions are another reason to review the source experience, not just the downstream export.

For example, a consent record may faithfully preserve an interaction with a misleading page. Preservation would help show what happened, but it would not make the underlying practice acceptable. A buyer needs both inspectable records and a source-review process capable of rejecting a problematic experience.

Keep registration status, exemption analysis, creative review, and source approval as distinct review items with named owners. Avoid a single “compliant” toggle that hides which checks were completed and which were never performed.

Source: Act 47, sections 2–3.

A practical lead-buyer acceptance test

Consider a hypothetical homeowner lead delivered Monday morning. The publisher says the person requested a quote. The buyer plans to send a text and schedule an automated voice follow-up.

Before contact, the buyer should be able to connect the delivered number to the source interaction and identify what the consumer authorized. The team should then classify each planned communication, evaluate the applicable state requirements, and check current suppression information. Text and voice flows should not inherit the same result merely because they use the same lead identifier.

If the seller identity or disclosure is missing, route the lead to review rather than inventing the absent evidence. If the original agreement is available but an opt-out arrived later, preserve both events and apply the current contact policy. If an exclusion is relied on, document the basis instead of substituting the publisher’s marketing label.

This example is a suggested operating pattern. Whether a particular agreement or communication satisfies the law depends on its facts and the applicable legal analysis.

Implementation checklist

  • Inventory campaigns that contact Pennsylvania subscribers or otherwise fall within the act’s scope.
  • Review voice, text, voicemail, and ringless-voicemail flows separately.
  • Map the statutory definitions and exclusions to documented campaign decisions.
  • Inspect a sample of seller-specific agreements and the underlying source interactions.
  • Verify that delivered telephone numbers and evidence references match.
  • Review scheduling, Sunday, and holiday controls for covered solicitations.
  • Test opt-out propagation across the CRM, messaging provider, and call platform.
  • Review registration obligations and any exemption relied on.
  • Check that source pages and synthetic-message content are not misleading.
  • Assign an owner to unresolved records before permitting outreach.

Treat this as a workflow review, not an invitation to rewrite every disclosure from a blog post. Have counsel approve the relevant interpretations and language, then make those decisions executable and auditable.

Key Takeaways

Pennsylvania’s Act 47 is a current state-law development, not a reason to wait for a future FCC rule. Its definitions, exclusions, written-consent elements, and contact restrictions need to be read together.

For lead buyers, the central lesson is practical: preserve the evidence, record the decision, and control the contact. Those are related tasks, but none substitutes for the others. A well-preserved consent interaction cannot by itself establish registration status, maintain suppression lists, or decide whether a particular communication is lawful.

Start with a small sample of recently purchased leads. Trace each one from the consumer-facing disclosure through delivery and the next planned contact. Every missing link is a concrete improvement to make before the next campaign runs.

For a broader evidence-review framework, read the guide to proof of consent.