Skip to main content
Final Expense Marketing

TCPA consent language for final expense landing pages: what the form must say and whom it must name

What the consent clause on an agent-run final expense landing page must say, whom it must name, and what six states add, with an annotated example and a pre-launch checklist.

General information, not legal advice. This guide summarizes the rules in the sources listed at the end, as read on . Rules change, and they differ by state and by business, so check with a lawyer licensed where you call before relying on it.

On this page
  1. What must TCPA consent language on a final expense form say, clause by clause?
  2. Which rule text governs the form today, with the one-to-one rule vacated?
  3. How should the clause be worded so it also works as Do Not Call Registry permission?
  4. Who is ‘the seller’ when an agency or IMO builds or buys forms for downline agents?
  5. Which contact methods must the clause name: live calls, autodialed calls, prerecorded or AI voices, and texts?
  6. What has to be captured with the clause so the consent can be proved later?
  7. Which states add their own written-consent rules: Florida, Oklahoma, Maryland, Pennsylvania, Connecticut and Maine?
  8. An annotated clause-by-clause example and a pre-launch checklist
  9. Questions
  10. Sources

TCPA consent language on final expense forms must, under FCC rules for autodialed, prerecorded or AI-voice sales calls and texts, authorize your agency at the entered number, say agreeing is not a condition of purchase, and carry the consumer’s signature. Worded as an agreement to be contacted by your agency, it can double as Do Not Call Registry permission.

Every rule below was checked against its source on October 22, 2026: the eCFR, the U.S. Code, the Eleventh and Fifth Circuits’ opinions, FCC orders, the Federal Register, FTC staff guidance and six states’ statutes (four read from dated archive copies of the official pages, Oklahoma’s as enacted in 2022). This is not legal advice. Have counsel review your clause before launch and after any wording change.

The consent clause is the consent text beside the submit button plus the checkbox and button the consumer uses to accept it. When your agency calls for its own book, the seller is your agency (other cases are below), so the clause exists to authorize it. Whose words go in the clause depends on whose page it is: on a landing page your agency owns, the consent language can name your agency, and the agency in the consent text and the agency on the phone can be one business. When a vendor or a firm running final expense advertising for you builds the page, read its consent text against the elements below before launch.

For autodialed and prerecorded telemarketing calls, the FCC’s TCPA consent requirements sit in one definition, 47 CFR 64.1200(f)(9), which can be read as six elements:

  1. A written agreement. The definition starts with “an agreement, in writing”; on a landing page, the consent text is the writing.
  2. The consumer’s signature. It must bear “the signature of the person called”. An electronic or digital signature counts where federal law or state contract law recognizes it ((f)(9)(ii)).
  3. The seller. It “clearly authorizes the seller”, defined as “the person or entity on whose behalf a telephone call or message is initiated” to encourage a purchase ((f)(10)).
  4. The methods. It covers calls “using an automatic telephone dialing system or an artificial or prerecorded voice”.
  5. The number. It includes “the telephone number to which the signatory authorizes” those calls.
  6. A clear and conspicuous disclosure. The TCPA disclosure must state two things: the agreement authorizes those calls, and the consumer “is not required to sign the agreement” as “a condition of purchasing any property, goods, or services.”

The definition asks for no opt-out line and no message-rates notice, two lines some templates add. The rule requires this consent before a telemarketing call placed by autodialer, or with an artificial or prerecorded voice, goes to a cell phone (64.1200(a)(2)), and before an artificial or prerecorded telemarketing message goes to a home line ((a)(3)). A live call dialed by hand meets different rules, covered below.

Lead forms that open inside Meta’s ads, not on your page, add Meta’s own rules: see how Meta’s Instant Form disclaimers differ from landing-page consent.

Which rule text governs the form today, with the one-to-one rule vacated?

The FCC’s written-consent rule quoted above is still the rule on the books. Its TCPA one-to-one consent version never took effect, and a 2026 appeals ruling reads the statute as asking for less:

DateEventSource
December 13 and 18, 2023The FCC adopts, then releases, consent limited to “no more than one identified seller”, for calls “logically and topically associated with the interaction that prompted the consent”FCC 23-107
January 26, 2024Federal Register publication sets the (f)(9) change for January 27, 202589 FR 5098
January 24, 2025The FCC postpones the change; the prior requirements “will meanwhile remain in effect”DA 25-90
January 24, 2025The Eleventh Circuit rules to vacate Part III.D of the 2023 orderInsurance Marketing Coalition v. FCC, No. 24-10277
April 30, 2025The court’s mandate issues; the vacatur takes effectDA 25-621
July 14, 2025An FCC order restores the prior (f)(9) textDA 25-621
August 29, 2025The restored text takes effect90 FR 42137
February 25, 2026The Fifth Circuit holds that the statute permits written or oral consent for autodialed or prerecorded calls, “Contra 47 C.F.R. § 64.1200(a)(2)”Bradford v. Sovereign Pest Control of TX, No. 24-20379
October 19, 2026The eCFR, current to that date, shows the restored definition (§64.1200 unchanged since March 25, 2026)eCFR

The Eleventh Circuit addressed only the 2023 rule: “The 2012 Order is not at issue in this case.” That order is the source of the words “clearly authorizes the seller”. The court also noted: “As the FCC itself admits, consumers no doubt can give ‘prior express consent’ under the TCPA to receive robocalls from multiple parties without consenting to each caller separately” (Insurance Marketing Coalition v. FCC). Each seller must still be clearly authorized under (f)(9), so naming one seller per form remains a buyer-protection practice, not a federal rule.

The Fifth Circuit, which covers Louisiana, Mississippi and Texas, went further in a private suit over prerecorded calls: “the statute does not require prior express written consent” (Bradford v. Sovereign Pest Control of TX). The opinion does not address state statutes or registry permission, which still ask for written consent or a signed writing, so a signed clause remains the record to build.

FCC 26-67, adopted September 30 and released October 1, 2026, changes how consent is revoked and leaves the written-consent definition alone. It takes effect 30 days after Federal Register publication, which had not happened as of October 22, 2026; search federalregister.gov for “FCC 26-67” to check its status and effective date.

How should the clause be worded so it also works as Do Not Call Registry permission?

The clause should use the verb from the National Do Not Call Registry rule: the consumer agrees to be contacted by your agency, at the number entered. Registered numbers may still be called with the subscriber’s “prior express invitation or permission”, and “Such permission must be evidenced by a signed, written agreement between the consumer and seller which states that the consumer agrees to be contacted by this seller and includes the telephone number to which the calls may be placed” (64.1200(c)(2)(ii)). Registry permission answers a different trigger from written consent:

  • Written consent turns on how you dial: by autodialer, or with an artificial or prerecorded voice.
  • Registry permission turns on the number. The registry bar covers every telephone solicitation to a registered residential number, so it reaches calls you dial by hand. A call made with the person’s “prior express invitation or permission” is not a telephone solicitation ((f)(15)(i)).
  • Another route, an established business relationship ((f)(15)(ii)), has its own time limits and does not depend on the consent text: see which registered numbers you may call on a business relationship.

Where the FTC’s Telemarketing Sales Rule (TSR) applies to your calls, its version wants a writing showing “that calls made by or on behalf of a specific party may be placed to that person”, with the number and signature (16 CFR 310.4(b)(1)(iii)(B)(1)). FTC staff add, in their guide to complying with the Telemarketing Sales Rule, that the request “must be clear and conspicuous, and the consumer’s assent must be affirmative”; a pre-checked “Please call me” button does not count.

One signed clause can do both jobs: the autodialer and prerecorded-voice authorization, plus a line such as “I agree to be contacted by [Agency legal name] at the number I entered”.

Who is ‘the seller’ when an agency or IMO builds or buys forms for downline agents?

The seller is the business each call is made for, whoever dials it ((f)(10)); the telemarketer is “the person or entity that initiates” the call ((f)(12)). When the FCC adopted written consent in 2012, it said the consumer must receive “clear and conspicuous disclosure” that future calls delivering prerecorded messages will come “by or on behalf of a specific seller” (FCC 12-21, paragraph 33).

An agency whose own agents call

Calls your licensed agents place in the agency’s name are made on its behalf, so name the agency by its legal name and any trade name your agents use on the phone.

An IMO or agency that hands leads to downline agents

A downline agent who sells for their own book calls on their own behalf too, so a clause that names only the IMO (independent marketing organization) or the upline agency may not clearly authorize that agent. Two drafting routes keep the named seller and the caller the same:

  1. Route before the consumer signs. Assign the lead by state or ZIP code while the form is open, and show the receiving agency’s name in the consent text.
  2. List each agency by name in the consent text.

Wording such as “licensed agents in our network” names a category, not a seller: in our reading, no consumer could tell from it who will call. For prerecorded messages on calls the TSR covers, FTC staff go further: the seller “cannot rely on third-parties to obtain permission.”

Forms that serve several buyers

One form can carry consent for several companies, as the Eleventh Circuit’s note on the FCC’s concession shows, but each must still be clearly authorized. For prerecorded calls the TSR covers, FTC staff say the authorization “does not extend to other sellers, such as affiliates, marketing partners, or others.” On shared leads, where one record goes to several buyers, each buyer needs its own clear authorization, so read the consent text before the first dial.

When a setter desk or call center dials for you

The federal definition authorizes the seller to deliver “or cause to be delivered” the calls, so it is written around the business the calls are for. Florida, Oklahoma and Maryland word it as “the person making or allowing the placement” of the call, a phrase that can cover both the desk that dials and the agency that allows it. Connecticut authorizes “the telemarketer”, which it defines to include “any person, or any affiliate or subsidiary of any person” that makes or causes the call. If callers you hire to follow up the leads you already have, or a call center, will dial, decide with counsel whether the clause should name them too.

Which contact methods must the clause name: live calls, autodialed calls, prerecorded or AI voices, and texts?

The federal disclosure is written as “an automatic telephone dialing system or an artificial or prerecorded voice” ((f)(9)(i)(A)): name each method you will use, and ask counsel before dropping either federal term. Whether your dialer counts as an autodialer under federal and state definitions is its own question. Only Connecticut requires written consent for live calls. Cells quote each law; Maine has no consent definition, so its column quotes its consent rule:

MethodFederal (f)(9)FloridaOklahomaMarylandPennsylvaniaConnecticutMaine
Live call dialed by handNot namedNot namedNot namedNot named“A telephone call”, within “telephone solicitation” (consent is required only for robocalls)“a telephone system” (consent definition); “a live voice” (sales-call definition)Not named
Autodialer“automatic telephone dialing system”“automated system for the selection and dialing of telephone numbers”“automated system for the selection or dialing of telephone numbers”Same as Oklahoma“automated dialing system”, in its robocall definition“an automated dialing system”“automated telephone calling device”
Artificial or prerecorded voice“artificial or prerecorded voice”“the playing of a recorded message”“the playing of a recorded message”“recorded or artificial voice message”“prerecorded or artificial voice calls or messages”“a recorded message device”“an artificial or prerecorded voice”
Prerecorded voicemailNot named“prerecorded voicemail”“prerecorded voicemail”“prerecorded voicemail”“voicemail, ringless voicemail”, as telephone solicitationsNot namedNot named
SoundboardNot namedNot namedNot namedNot namedNot named“soundboard technology”Not named
Text messageNot named; the FCC reads “call” to include texts“text message”“text message”“text message”“text message”“text or media messaging”Not named

Live calls dialed by hand

A live call dialed by hand uses neither method the federal definition names, so the federal written-consent rule does not reach it; registry permission still does for registered numbers. Connecticut is the exception: it requires written consent for every telephonic sales call, live voice included (§42-288a(l)), and the agreement must disclose “the means by which the telemarketer will call or contact the consumer” (§42-284(14)).

Artificial, prerecorded and AI voices

The FCC has confirmed that the TCPA’s restrictions on an artificial or prerecorded voice “encompass current AI technologies that generate human voices” (FCC 24-17). If an AI voice agent or a recorded message may reach the consumer, the clause should say so.

Texts

The FCC reads “call” to include text messages, as the Eleventh Circuit noted, and every state in the table except Maine names texts, so a clause that covers texts should say “text messages”.

The consent record has to show what the consumer saw and did, because proving consent falls on you. In its 2012 order the FCC wrote: “should any question about the consent arise, the seller will bear the burden of demonstrating that a clear and conspicuous disclosure was provided and that unambiguous consent was obtained” (FCC 12-21, paragraph 33).

The signature step

The signature is an act, so build one that cannot happen by accident. On a TCPA consent form the signature is usually electronic, and the E-SIGN Act defines an electronic signature as an electronic “sound, symbol, or process, attached to or logically associated with” a record and “executed or adopted by a person with the intent to sign the record.” The FCC accepts E-SIGN consent “including permission obtained via an email, website form, text message, telephone keypress, or voice recording” (paragraph 34). Florida counts “checking a box indicating consent” as a signature, and for calls the TSR covers, FTC staff reject a pre-checked button. Build it as an unchecked box the consumer ticks, plus a button whose label matches the consent text.

The text, its version and the number

For each submission, keep:

  • the consent text exactly as displayed, with its version date;
  • the seller name the page showed;
  • the phone number the consumer entered;
  • the timestamp and the page URL;
  • the signature act: the box ticked and the button pressed.

Never edit live consent text in place: publish a new dated version and keep the old one, because each consumer agreed only to the words shown that day. The list is practice, not rule text: it is the record that meets the seller’s burden above.

What a certificate adds

A consent certificate is evidence of a web session, not a legal verdict. ActiveProspect says TrustedForm certificates “provide the landing page URL, timestamp, and a replay of the consent event”, but the consent text still has to carry the elements above; see what a consent certificate records, and what it cannot show.

Florida, Oklahoma, Maryland, Pennsylvania, Connecticut and Maine write their own written-consent rules into statute; these are the six our state-by-state read of telemarketing statutes found on October 14, 2026. Connecticut’s reaches live calls too, and only Oklahoma exempts licensed insurance agents from its consent rule:

State and lawWhom the consent authorizesCalls it reachesSignatureInsurance-agent carve-outStatus
Florida, Fla. Stat. §501.059(1)(g), (8)(a)“the person making or allowing the placement” of the callUnsolicited sales calls by automated system “for the selection and dialing” of numbers, or with a recorded messageElectronic, or an act such as “checking a box indicating consent”None in §501.059Last amended in 2023
Oklahoma, HB 3168 (2022), §775C.2(3), §775C.3(A)Same as FloridaSales calls by automated system “for the selection or dialing” of numbers, or with a recorded messageElectronic, if valid under federal or state lawLicensed agents soliciting within their license are exempt from the whole act (§775C.5(8))Effective November 1, 2022, as enacted
Maryland, Com. Law §14-4501(d), §14-4502(a)(3)Same as FloridaSame as OklahomaElectronic, if valid under federal or state lawNone in the exemption listIn effect since January 1, 2024
Pennsylvania, Telemarketer Registration Act as amended by Act 47 of 2026The seller, in an agreement “executed between a called party and a seller”Robocalls (§5(a)(11))Electronic, “consistent with” E-SIGNLicensees are exempt from registration onlyApproved July 20, 2026; took effect in October 2026, 90 days after approval
Connecticut, Conn. Gen. Stat. §42-284(14), §42-288a(l)“the telemarketer”, affiliates and subsidiaries includedEvery telephonic sales call, live voice includedThe agreement “bears the signature of the consumer”None in chapter 743mSince October 1, 2023 (Public Act 23-98)
Maine, 10 M.R.S. §1498(2), (6)(E)Not stated: consent “of the recipient of the call”Solicitation calls to cell and home numbers by “automated telephone calling device” or “an artificial or prerecorded voice”Not defined; the text says “prior, written, express consent”None in §1498Last amended in 2019

Where the consumer’s own request changes the answer

These laws carve out some calls that follow the consumer’s own request, consent or relationship:

  • Florida does not treat as unsolicited a call made “In response to an express request of the person called” (§501.059(1)(k)).
  • Maryland exempts from its consent rule a single solicitation made “in response to an inquiry or request from the customer or client” (§14-4502(a)(1)(v)).
  • Connecticut excludes from a telephonic sales call one made “in response to a request or inquiry made by a resident consumer” (§42-284(18)(B)(i)).
  • Pennsylvania excludes from a telephone solicitation a call made “In response to the prior express written consent of the subscriber”, or to a subscriber with whom the seller or telemarketer has “an established business relationship within the past 12 months preceding the call” (§2). An inquiry can start that relationship, but continuing it “beyond the initial inquiry” needs the subscriber’s consent.
  • Maine does not bar automated or prerecorded calls that “Respond to a telephone inquiry initiated by the person” called (§1498(6)(B)).

None of these changes the federal written-consent rule; whether your callbacks fit them is a question in check 10 below.

Pennsylvania’s amended act also bars “any unfair or deceptive act or practice in an effort to obtain” a subscriber’s consent (§5(a)(12)). Florida’s agent exemption (§501.604(8), in part IV of chapter 501) does not reach §§501.608 and 501.616(6)–(7), so the hours and call cap in §501.616(6) still bind licensed agents; §501.059, in part I, has no insurance exemption. For those hours and caps, see Florida’s and Pennsylvania’s calling hours and other limits.

An annotated clause-by-clause example and a pre-launch checklist

Example wording written for this guide, not a template. The rows are not assembled into one clause, because the right words depend on who dials, which methods you use and where you call. Have counsel review your clause.

The annotated example

ClauseExample wordingRule it answersFailure it preventsState notes
1. Signature step“By checking this box and selecting Get my quote, I sign this agreement.”(f)(9), (f)(9)(ii); E-SIGN §7006(5); FCC 12-21 ¶34An unsigned or pre-checked consentFlorida counts “checking a box indicating consent”; whether the form submits with the box empty is for counsel (row 7)
2. Named seller“I agree that [Agency legal name], doing business as [trade name],”(f)(9) “clearly authorizes the seller”; (f)(10); FCC 12-21 ¶33A clause naming only a vendor, an IMO or “partners”Each state words this differently; see the state table
3. Callers, if a setter desk or call center dials“and [Call center legal name], which calls on its behalf,”State consent definitionsConsent that covers the agency but not the desk that dialsFlorida, Oklahoma, Maryland, Connecticut
4. Contact methods“may call and text me, including with autodialed calls and calls using an artificial or prerecorded voice, which may be AI-generated,”(f)(9)(i)(A); FCC 24-17; state definitionsA method in use that the clause never namedConnecticut: disclose “the means”
5. Number“at the phone number I entered above.”(f)(9); (c)(2)(ii)Consent tied to no numberThe five state definitions require it; Maine has none
6. Registry permission“I agree to be contacted by [Agency legal name] at that number.”(c)(2)(ii) “agrees to be contacted by this seller”; 16 CFR 310.4(b)(1)(iii)(B)(1)Robocall consent that leaves hand-dialed calls to registered numbers uncoveredState do-not-call lists are a separate check
7. Not a condition“Agreeing is not a condition of buying any policy, product or service.”(f)(9)(i)(B)A clause that reads as required to buy a policyFlorida, Oklahoma, Maryland and Pennsylvania require it; Connecticut’s definition does not
8. PlacementNo wording: directly above the button, in body-size type, outside the terms, not behind a link(f)(9)(i) “clear and conspicuous”; FTC staff, for calls the TSR covers: not “buried in unrelated information”Consent text found to be hiddenConnecticut describes an “advance, clear, conspicuous and detailed written disclosure” of a consent’s scope (§42-284(9))

Ten checks before the form goes live

  1. Write the seller’s legal and trade names exactly as your callers will say them.
  2. Decide who dials: your licensed agents, a setter desk or a call center.
  3. Name each method your dialer, scripts and CRM will use, and keep both federal method terms unless counsel agrees to drop one.
  4. Show the entered phone number beside the consent text.
  5. Place the consent text directly above the button, with an unchecked box, outside the terms.
  6. Version-date the consent text and archive every version with the dates it ran.
  7. Store the per-submission record above, with the certificate script loading before submit.
  8. Check the state rows above and the calling-hours guide for every state you call, and read the statute of any state the table leaves out.
  9. When FCC 26-67 is published, decide how stop requests will be taken.
  10. Have counsel review the clause before launch and after every wording change, and ask: is a carrier also a seller on your calls; does a linked or long list of names clearly authorize each business; may the form submit with the box empty; do your callbacks fit a state’s request carve-out; and does Oklahoma’s exemption reach unlicensed staff?

Questions agents ask

  1. Can a pre-checked box count as consent?

    Not under FTC staff guidance for calls the Telemarketing Sales Rule covers: a consumer “would not be deemed to have provided such permission if the ‘Please call me’ button was pre-checked as a default.” E-SIGN asks for “the intent to sign the record”, and Florida’s box-tick signature is the consumer’s own act of “checking a box indicating consent”. Leave the box empty and let the consumer tick it.

  2. Which calls need prior express consent but not written consent?

    Under the FCC’s rules, an autodialed or prerecorded call to a cell phone needs “the prior express consent of the called party”, and written consent only when it “includes or introduces an advertisement or constitutes telemarketing” (64.1200(a)(1)–(2)). The Fifth Circuit held in 2026 that the statute’s prior express consent “encompasses both oral and written consent for both telemarketing and informational calls”; the FCC’s rule and the state statutes in this guide still ask for writing.

  3. Can one consent cover calls from more than one agency?

    It can in principle. The Eleventh Circuit wrote: “As the FCC itself admits, consumers no doubt can give ‘prior express consent’ under the TCPA to receive robocalls from multiple parties without consenting to each caller separately.” Each agency still has to be clearly authorized under the written-consent rule, and for prerecorded calls the Telemarketing Sales Rule covers, FTC staff say the authorization “does not extend to other sellers, such as affiliates, marketing partners, or others.”

  4. If I change the consent wording, do earlier sign-ups need to agree again?

    Each consumer agreed to the text on the page when they signed, and the seller carries the burden of proving the disclosure and the consent. Keep every version with its dates. A contact method added later was never in the older text, so ask counsel before using it on earlier sign-ups.

  5. Should the consent text tell leads how to stop calls and texts?

    Only as notice. Until FCC 26-67 takes effect, a consumer may revoke consent by “any reasonable method”, so a stop line cannot narrow how they revoke. Once it does, a caller that designates an exclusive revocation method must disclose it “on the call or in the text”, so a line in the consent text alone would not meet that rule.

  6. Is consent taken by phone keypress or recorded voice valid, or only on a web form?

    In 2012 the FCC said consent obtained in compliance with the E-SIGN Act satisfies its written-consent rule, “including permission obtained via an email, website form, text message, telephone keypress, or voice recording.” The rest of the definition still applies: the named seller, the methods, the number and the not-a-condition disclosure. Separately, the Fifth Circuit has held that the statute itself accepts oral consent; the FCC’s rule and the state statutes still ask for writing.

Sources

  1. 47 CFR 64.1200, Delivery restrictions (eCFR versioner, point in time 2026-10-19)Accessed October 22, 2026
  2. eCFR versioner API: Title 47 currency (up to date as of 2026-10-19; latest issue 2026-10-19)Accessed October 22, 2026
  3. eCFR versioner API: 47 CFR 64.1200 version history (latest amendment 2026-03-25)Accessed October 22, 2026
  4. Insurance Marketing Coalition Ltd. v. FCC, No. 24-10277 (11th Cir. January 24, 2025)Accessed October 22, 2026
  5. Bradford v. Sovereign Pest Control of TX, Inc., No. 24-20379 (5th Cir. February 25, 2026)Accessed October 22, 2026
  6. 28 U.S.C. 41, Number and composition of circuits (uscode.house.gov)Accessed October 22, 2026
  7. FCC DA 25-90, Order postponing the revised 47 CFR 64.1200(f)(9) (January 24, 2025)Accessed October 22, 2026
  8. FCC DA 25-621, Order reinstating the prior 47 CFR 64.1200(f)(9) (July 14, 2025)Accessed October 22, 2026
  9. Federal Register, 90 FR 42137, FR Doc. 2025-16641 (effective August 29, 2025)Accessed October 22, 2026
  10. FCC 23-107, Second Report and Order (adopted December 13, 2023; released December 18, 2023)Accessed October 22, 2026
  11. Federal Register, 89 FR 5098, FR Doc. 2023-28832 (published January 26, 2024): document recordAccessed October 22, 2026
  12. FCC 26-67, Report and Order and FNPRM (adopted September 30, 2026; released October 1, 2026)Accessed October 22, 2026
  13. Federal Register API: full-text search for "FCC 26-67" (no results on October 22, 2026)Accessed October 22, 2026
  14. FCC 12-21, Report and Order on prior express written consent (February 15, 2012)Accessed October 22, 2026
  15. E-SIGN Act, 15 U.S.C. 7001, general rule of validity (uscode.house.gov)Accessed October 22, 2026
  16. E-SIGN Act, 15 U.S.C. 7006, definitions (uscode.house.gov)Accessed October 22, 2026
  17. 16 CFR 310.4, Abusive telemarketing acts or practices (eCFR versioner, point in time 2026-10-19)Accessed October 22, 2026
  18. FTC, Complying with the Telemarketing Sales Rule (written permission to call; prerecorded-message agreements; the business of insurance)Accessed October 22, 2026
  19. Fla. Stat. §501.059, Telephone solicitation (2026 Florida Statutes; Internet Archive capture of October 2, 2026)Accessed October 22, 2026
  20. Fla. Stat. chapter 501, including part IV, the Florida Telemarketing Act (Internet Archive capture of September 25, 2026)Accessed October 22, 2026
  21. Oklahoma HB 3168 (2022), Telephone Solicitation Act of 2022, enrolled (Internet Archive capture of the official PDF, December 11, 2025)Accessed October 22, 2026
  22. Md. Code, Commercial Law §14-4501, definitionsAccessed October 22, 2026
  23. Md. Code, Commercial Law §14-4502Accessed October 22, 2026
  24. Maryland Laws of 2023, Chapter 413 (SB 90), Stop the Spam Calls ActAccessed October 22, 2026
  25. Pennsylvania Telemarketer Registration Act, as amended by Act 47 of 2026 (Internet Archive capture of September 1, 2026)Accessed October 22, 2026
  26. Pennsylvania SB 992 (2025–26 session), bill page showing Act 47 of 2026 (Internet Archive capture of September 4, 2026)Accessed October 22, 2026
  27. Pennsylvania SB 992, Printer’s No. 1649, final text (Internet Archive capture of September 4, 2026)Accessed October 22, 2026
  28. Conn. Gen. Stat. chapter 743m, Telemarketing (Internet Archive capture of September 30, 2026)Accessed October 22, 2026
  29. Connecticut Public Act 23-98 (SB 1058), approved June 26, 2023 (Internet Archive capture)Accessed October 22, 2026
  30. 10 M.R.S. §1498, Automated telephone solicitation prohibited; exceptions; penalties (Maine Legislature)Accessed October 22, 2026
  31. FCC 24-17, Declaratory Ruling on AI-generated voices (adopted February 2, 2024; released February 8, 2024)Accessed October 22, 2026
  32. ActiveProspect, Trust & Transparency (TrustedForm certificate contents)Accessed October 22, 2026
Get a quote