Comparing TCPA Litigator Scrubbing Providers for High-Volume Calling and Texting

If you push tens of thousands of dials or texts a day, a litigator scrub stops being a checkbox and becomes part of your production stack. The questions change. It’s less “does this vendor have a litigator list?” and more “will this thing slow my dialer down, does it plug into the platform I already run, and what does it cost at my real volume?”

Here’s a comparison of the providers that offer TCPA litigator scrubbing, organized around the things that matter once volume gets high.

The short list

Six providers come up most often for high-volume calling and texting:

  • TCPALitigatorList.com: a dedicated litigator database with bulk upload and a real-time API.
  • Contact Center Compliance (DNC.com): Litigator Scrub bundled with wireless, VoIP and DNC scrubbing.
  • The Blacklist Alliance: the TCPA Litigation Firewall for inbound and outbound traffic.
  • PossibleNOW: DNCSolution, an enterprise suppression platform.
  • Gryphon: litigator screening inside a real-time call and text compliance platform.
  • Trestle: phone validation API with a litigator-risk flag.

Instead of reviewing them one at a time, it’s more useful to compare them on five operational questions.

1. Batch, real time, or both?

High-volume shops usually need both. Batch scrubs clean a campaign file before it loads. Real-time checks catch numbers that arrive mid-day, like fresh web leads or texts triggered by an app event.

TCPALitigatorList.com offers both: CSV or Excel upload with multiple phone columns, which the company says returns a clean list in seconds, plus a real-time API that checks each number before the call and blocks on a match. It also has an endpoint API for single and mass scrubbing. Contact Center Compliance, PossibleNOW and Gryphon all describe real-time checking. The Blacklist Alliance says its firewall covers inbound and outbound. Trestle offers its API and batch processing.

2. Where does it plug in?

The best scrub is the one your dialer actually calls. Contact Center Compliance publishes the longest integration list of the group, about 20, including Five9, Genesys, Salesforce, Convoso, RingCentral, Vicidial, PhoneBurner, ActiveProspect, Leadspedia and Retreaver. The Blacklist Alliance offers a LeadConduit add-on through ActiveProspect and integrations with Retreaver and LeadExec, which suits lead-buying operations. Gryphon integrates with major dialers, including a NICE CXone action. TCPALitigatorList.com and Trestle provide APIs that your team or your platform vendor wires in.

Before you shortlist anyone, check where the scrub sits in your flow. If leads move from a form to a lead distribution tool to a dialer, the check should run before the number reaches the dialer queue.

3. What’s being matched, and how fresh is it?

Coverage claims vary, and each vendor describes its own data:

  • TCPALitigatorList.com says it covers more than 600,000 names (litigators, multi-case plaintiffs, demand-letter senders, attorneys and DNC complainers), updated every weekday. Its Name Recognition Algorithm flags serial litigators by name and tracks prepaid or unregistered phones, which matters because repeat plaintiffs often change numbers.
  • Contact Center Compliance says its data is updated in real time from original court documents.
  • The Blacklist Alliance checks its own high-risk data along with your internal DNC list and the national and state registries.
  • PossibleNOW checks federal, state, internal, wireless, reassigned-number and known-litigator lists.

Don’t compare headline numbers alone. Ask each vendor how a record gets added, how often, and whether matching is by phone only or also by name.

4. What does it cost at volume?

This is where the providers differ most. TCPALitigatorList.com publishes its tiers: $199 a month for Basic (no API), API plans from $299 a month, and higher tiers up to enterprise plans at $8,999 and $12,999 a month on 12-month terms. Annual billing gets two months free. For enterprise customers, it also offers a Shared Savings Program in which scrubbing is free for 12 months and the fee is 25% of any verified reduction in annual TCPA lawsuit expense, with nothing owed if there’s no reduction.

The others don’t publish rate cards. The Blacklist Alliance and PossibleNOW say they price by contact, Gryphon by seat and volume, and Trestle per lookup. Contact Center Compliance doesn’t list pricing. Per-lookup pricing can look cheap until you multiply it by every dial attempt, so model your real daily attempts, not unique records.

5. What else comes in the same call?

At high volume, one API call that returns several answers saves both latency and engineering time. TCPALitigatorList.com includes federal and state DNC scrubbing and active/inactive phone verification. Contact Center Compliance pairs litigator data with wireless and VoIP identification. Trestle returns line type, carrier and validity. PossibleNOW folds in Reassigned Numbers Database checks, and Gryphon adds consent and calling-hours rules.

Run a one-week bake-off

The cleanest way to compare is with your own data:

  • Pull one recent campaign file and one day of real-time lead traffic.
  • Send the same file to two or three vendors. TCPALitigatorList.com offers a sample list and demo scrub. Ask the others what test options they offer.
  • Compare match counts, overlap between vendors, and how many matches each one explains with a source.
  • Time the real-time API under load from your own environment.
  • Price each one against your actual monthly attempt volume.

Keep in mind that none of these tools replaces consent records, a 31-day National DNC refresh, or opt-out handling that meets the FCC’s revised revocation rules taking effect November 25, 2026. A litigator scrub lowers the odds that a mistake reaches someone who sues. It doesn’t remove the mistake.

If you want a starting benchmark, run last week’s dial file through TCPALitigatorList.com and count the matches before you talk pricing with anyone.

This article is general information, not legal advice. Review your calling and texting program with TCPA counsel. Disclosure: this publication has a business relationship with TCPALitigatorList.com. Vendor details are drawn from each company’s public materials as of November 2026.

Nine Days of AI Calls, $1.1 Million: What This Month’s Robocall Settlements Tell Operators

Four TCPA settlements in the news over the past week share one feature: every one of them involves artificial or prerecorded voice calls. One of them, involving an AI voice vendor, covered just 900 people and still settled for $1.1 million. If your team uses voice bots, voicemail drops or automated reminders, this is the batch to study.

The AI test run that became a class action

TCPAWorld reported on November 9, 2026 that the parties in Finley v. Altrua have settled for $1.1 million. The class, as described in the post, covers people that Crown Administrators sent messages to using AiRudder on behalf of Altrua during a nine-day period. TCPAWorld describes it as a class of just 900 AI call recipients and characterizes the campaign as essentially a test run by a vendor.

Do the math: that is more than $1,200 of settlement value per class member, for a nine-day pilot. The TCPA treats artificial-voice calls the same way it treats prerecorded ones, and a short test is still a campaign in the eyes of the statute.

The prerecorded settlements

  • Connect America, up to $4 million. According to a November 3 article in the National Law Review, the class covers people who did not give ConnectAmerica.com, LLC their number but received at least one prerecorded message on a cell phone from April 1, 2021 through preliminary approval. The article puts the class at 14,534 members, payments at up to $275 each, and attorneys’ fees at up to $1.3 million.
  • Bond v. Folsom Insurance Agency, $850,000. In the Northern District of Texas (No. 3:24-cv-02551-BN), the fund covers 41,719 telephone numbers that received artificial or prerecorded voice calls and voicemails between February 29, 2020 and September 15, 2026. Preliminary approval came September 15, the claim deadline is November 16, and the final approval hearing is December 29. Estimated payments are about $125 to $200. The defendants deny wrongdoing.
  • Seals v. Concora Credit, $9.375 million. In the District of Oregon (No. 3:25-cv-00728-AN), this wrong-number settlement covers non-accountholders who received prerecorded or artificial voice calls on their cell phones between May 2, 2021 and May 31, 2026. It includes an $8.375 million cash fund and at least $1 million in compliance spending over three years. The final fairness hearing is set for November 24. Concora denies the allegations.

The operator checklist

  • Treat AI voice as prerecorded voice. If a bot speaks, you need the consent level the TCPA requires for artificial-voice calls before the first dial, including during pilots.
  • Own your vendor’s tests. Altrua’s exposure came from messages sent on its behalf. Any vendor proof of concept should go through the same consent and suppression gates as a production campaign.
  • Fix wrong numbers. Concora’s class is people who were not customers at all. Reassigned-number checks and fast handling of “wrong number” responses are the defense.
  • Voicemail drops count. The Folsom class includes voicemails. Leaving a prerecorded message is not a way around the rules.
  • Budget for compliance, not just settlements. Concora’s deal includes a $1 million compliance commitment. Spending it before a lawsuit is cheaper.

Consent is the first gate; knowing who is likely to sue is the second. TCPALitigatorList.com lets operators check dial lists against known TCPA litigators and serial plaintiffs before calls go out, so a pilot or a voicemail campaign does not land on the phone of someone who files these cases for a living.

Bottom line

The dollar amounts range from $850,000 to more than $9 million, but the theme does not change: automated voice without clean consent is still the most expensive mistake in outbound. AI makes it faster to make.

Sources

Two New TCPA Rulings Just Took Away a Pair of Plaintiff Shortcuts. Here’s What Operators Should Do With Them.

Two federal decisions issued in the last ten days won’t make headlines outside the TCPA bar, but anyone running outbound calls or texts should know them. On November 2, 2026, a judge in the Western District of Washington ruled that a consumer who opted out of a prior class settlement can keep suing on her own but cannot turn around and lead a competing class. Three days earlier, on October 30, a Central District of California judge refused to enter a default judgment over texts that offered free products, holding they were not “telephone solicitations” at all.

Neither ruling is a free pass. Both are useful signals about where courts are drawing lines, and both reward operators who keep their records and message content clean.

Case one: Brown v. Citibank

In Brown v. Citibank, N.A., No. 3:25-cv-5119-TL (W.D. Wash. Nov. 2, 2026), the plaintiff alleged she received at least 46 unsolicited prerecorded robocalls. She had opted out of an earlier class settlement, Head v. Citigroup, and then sought leave to amend her complaint to add class claims of her own.

The court said no to the class piece. According to TCPAWorld’s summary of the order, opting out preserved her right to pursue her individual claims, not to launch a competing class action. The court found the proposed class failed Rule 23’s requirements, including typicality, and denied leave to add class claims. It did allow her to amend to add individual factual allegations, so her own case continues.

Why should an operator care? Because the opt-out-then-relaunch move is one way a single settled exposure turns into two. When a company settles a class, it is buying peace for that group. A ruling that keeps opt-outs from rebuilding a parallel class makes that peace more durable.

Case two: Bravo v. Hygeia Health

In Bravo v. Hygeia Health, Inc., No. 2:26-cv-08900 (C.D. Cal. Oct. 30, 2026), the defendant never appeared, and default was entered on September 24. The plaintiff asked for $1,000 in statutory damages plus $565 in costs over texts received in April 2026 at roughly 6:54 and 6:55 a.m.

Even with no one on the other side, the judge denied the default judgment. The texts offered breast pump accessories covered by the recipient’s insurance, at no cost. The court held they were not “telephone solicitations” under Section 227(c)(5), because they did not encourage the recipient to buy anything. It relied on the Seventh Circuit’s 2025 decision in Hulce v. Zipongo Inc. and ordered the plaintiff to show cause within 14 days why the case should not be dismissed.

Courts do not rubber-stamp a TCPA claim just because the defendant failed to answer. The content of the message still decides whether the do-not-call rules even apply.

What to do on the floor this week

  • Track settlement opt-outs. If you have settled a class, keep the list of people who opted out and flag them in your CRM. They are your most likely individual plaintiffs, and they should never be dialed again without fresh consent.
  • Audit your “free” messages. Hygeia’s texts survived because nothing in them pushed a purchase. Upsells, “limited time” language or a link to a paid tier change that analysis fast. Have someone read your informational templates with a plaintiff’s eyes.
  • Don’t confuse “not a solicitation” with “no rules.” The Hygeia ruling addressed the do-not-call claim. Prerecorded and artificial-voice rules, quiet hours and state laws can still apply to non-marketing messages.
  • Respond to every complaint. Hygeia got lucky. A default is still the most expensive way to lose a case you might have won.

The common thread is screening. Many of the plaintiffs who bring these cases, including those who opt out and sue again, are repeat filers. TCPALitigatorList.com lets outbound teams check numbers against a database of known TCPA litigators and serial plaintiffs before a campaign goes out, so the riskiest contacts are suppressed up front instead of discovered in a demand letter.

Bottom line

Brown narrows a procedural shortcut and Hygeia narrows a substantive one. Neither will help an operator whose consent records are a mess. Both help an operator who can show exactly what was sent, to whom, and why.

Sources

The Best TCPA Litigator Scrub List Services: Who Can Screen Your Calls and Texts Against Known Litigators

Most TCPA lawsuits don’t come from random consumers. A large share come from a small, identifiable group of repeat plaintiffs and the attorneys who file for them. Contact Center Compliance, one of the oldest vendors in this space, says about one-third of TCPA suits come from serial plaintiffs and litigators. Whatever the exact number, the takeaway for anyone running outbound calls or texts is the same: if you can identify those numbers before you dial, you avoid a large part of your exposure.

That is what a TCPA litigator scrub does. Below is a practical look at the companies that offer it, what each one actually provides, and how to choose.

Litigator scrubbing vs. Do Not Call scrubbing

A DNC scrub checks your list against the National Do Not Call Registry, state DNC lists, and your own internal suppression list. That is legally required for telemarketing. A litigator scrub is different. It checks your numbers against a database of people who have filed TCPA lawsuits, sent demand letters, or filed repeated complaints, plus the attorneys behind them. It isn’t required by law. It’s a risk filter that removes the contacts most likely to turn a single call into a federal case.

Most serious outbound programs run both. Several of the vendors below bundle them.

Companies that screen outbound lists against TCPA litigators

1. TCPALitigatorList.com
TCPA Litigator List has been operating since 2017 and focuses on litigator suppression. The company says its database holds over 600,000 names, including individual plaintiffs, professional and multi-case litigators, demand-letter “trolls,” plaintiff attorneys, and frequent DNC complainers, and that its researchers update it every weekday. You can upload a CSV or Excel file with multiple phone columns and download a clean list, or connect through a real-time API that checks each number before the call and blocks it on a match. A Name Recognition Algorithm flags serial litigators by name, which helps catch plaintiffs who switch to new prepaid numbers. The service also scrubs against federal and state DNC lists. Pricing is published: a Basic plan at $199 a month, and API plans starting at $299 a month that scale to enterprise tiers.

2. Contact Center Compliance (DNC.com) – Litigator Scrub
DNC.com has been in call center compliance for more than 20 years. Its Litigator Scrub runs alongside its wireless, VoIP and DNC scrubs, and the company says its litigator data is updated in real time from original court documents. It offers a REST API and lists about 20 integrations, including Five9, Genesys, Salesforce, Convoso, RingCentral, Vicidial and PhoneBurner. Pricing isn’t published; you book a meeting.

3. The Blacklist Alliance – TCPA Litigation Firewall
Blacklist Alliance’s firewall scrubs against its own high-risk data plus your internal DNC list, the National DNC Registry and state registries, for both inbound and outbound campaigns. It’s widely used in lead generation, partly because it is available as a LeadConduit (ActiveProspect) add-on. Subscribers also get access to online TCPA compliance training.

4. PossibleNOW – DNCSolution
PossibleNOW is aimed at enterprises. DNCSolution checks calls in real time against federal, state, internal, wireless, reassigned-number and known-litigator lists. It’s a fit for large financial, insurance and healthcare operations that want litigator suppression as one layer of a wider consent and preference program.

5. Gryphon
Gryphon puts litigator screening inside a broader real-time compliance platform that also enforces DNC rules, consent and calling-hour restrictions at the dialer level. It’s worth a look if you want one control point across many agents and dialers, but you’re buying a platform, not just a list.

6. Trestle – Real Contact
Trestle is mainly a phone validation and data quality API: line type, carrier, whether the number is active. It also includes a litigator-risk flag. It works well as an add-on at the lead-intake stage, though it isn’t a dedicated litigator database.

How to choose

  • Coverage beyond plaintiffs. Ask whether the database includes demand-letter senders and plaintiff attorneys, not just people named in filed cases. Many TCPA claims settle before anyone files.
  • Update frequency. Serial plaintiffs register new numbers constantly. Daily or weekday updates should be the minimum.
  • Name matching. Matching by phone number alone misses a litigator’s new number. Name-based matching closes that gap.
  • Real-time vs. batch. Batch scrubs suit campaign lists. Real-time API checks suit inbound leads, dialers and SMS platforms where numbers arrive constantly.
  • Integration. Confirm the vendor connects to your dialer, CRM or texting platform before you sign.
  • Transparent pricing. Published pricing makes it easy to compare cost per scrub at your volume.

What a scrub won’t do

Removing litigators lowers your exposure. It doesn’t fix a consent problem. You still need documented prior express consent where the law requires it, a working opt-out process, and calling-hour controls. The FCC’s revised opt-out rules take effect November 25, 2026, so this is a good time to check your revocation handling too. Treat litigator scrubbing as one layer of a compliance program, not a replacement for one.

If you’re deciding where to start, run a sample of your current list through TCPALitigatorList.com and count how many known litigators and plaintiff attorneys are already on it. That number usually makes the case on its own.

This article is general information, not legal advice. Talk to TCPA counsel about your specific program. Disclosure: this publication has a business relationship with TCPALitigatorList.com. Vendor details are drawn from each company’s public materials as of November 2026.

Where Can I Buy Verified MCA Leads? A 2026 Guide for Brokers and ISOs

If you broker merchant cash advances, you already know the hard part isn’t closing a merchant who wants capital. It’s finding enough of them, with working phone numbers, before another shop gets there first. “Verified” is the word every MCA lead seller puts on its homepage. Few of them can tell you what it actually means. This guide covers where verified MCA leads come from, what verification should include, and how to buy them without paying for a list that’s already been worked to death.

Where Verified MCA Leads Actually Come From

Most MCA data you can buy falls into one of four buckets:

  • Real-time inquiry leads. A merchant fills out a funding form, and the record goes to you within minutes. These have the highest intent and the highest price, and they go stale fastest.
  • Aged leads. These are inquiries from days, weeks, or months ago, sold at a discount. They can be very profitable if the phone data has been re-validated. If it hasn’t, they’re close to worthless.
  • UCC and public-record data. Merchants who have filed UCC liens, which often means they’ve taken funding before. These are useful for renewal and stacking campaigns, but they aren’t inquiries.
  • Compiled business data. Broad lists of businesses by industry, revenue band, and time in business. Cheap and large, but low intent.

Verification matters in every bucket. It matters most in aged and compiled data, where phone and email decay is fastest.

What “Verified” Should Mean Before You Pay

Ask any MCA lead vendor to show you, not just tell you, how each record has been checked. At a minimum, a verified MCA lead should include:

Phone validation by line type. Every number should be checked as live and classified as landline, mobile, or VoIP. Disconnected numbers waste dials, and the line type changes how you can legally contact the merchant.

Email validation. Bounced emails hurt your sender reputation across your whole domain, not just one campaign. A clean file should be validated before it reaches you.

Proof of consent. For inquiry-based leads, ask for Jornaya LeadiD or TrustedForm certificates. These are independent, timestamped records of how and where the merchant submitted their information. Without them, you only have the vendor’s word.

TCPA and DNC scrubbing. Records should be scrubbed against the National Do Not Call Registry, state lists, and known TCPA litigator lists, and scrubbed often. A file scrubbed once in the spring isn’t clean in November.

Deduplication and suppression. You shouldn’t pay twice for the same merchant, and you should be able to suppress merchants you already have in your CRM.

Red Flags When Buying MCA Leads

  • No sample file. A vendor confident in its data will let you test it.
  • Prices that look too good. A record at a fraction of market price usually means it’s been sold many times, or never validated.
  • Vague answers on sourcing. If a vendor can’t say where the merchant came from, you can’t defend that contact if a complaint arrives.
  • No line-type data. Without it, you can’t separate numbers you can dial from numbers that need extra care.
  • Delivery delays. Real-time leads that arrive hours late aren’t real-time.

How to Test a New MCA Lead Source

Don’t commit your whole budget to an untested vendor. Buy a small batch, enough for a few hundred dials, and track these four numbers:

  1. Connect rate: the percentage of numbers that reach a live line.
  2. Right-party contact rate: the percentage that reach the actual business owner or decision-maker.
  3. Application rate: how many contacts submit an application or bank statements.
  4. Cost per funded deal: total spend divided by merchants who actually fund.

The last number is the only one that decides whether a source is worth keeping. A cheap file with a poor connect rate almost always costs more per funded deal than a clean file at a higher price.

Where Cashyew Fits

Cashyew.com sells verified MCA leads and aged business funding data built for brokers, ISOs, and funders. Every file is checked before you download it:

  • Jornaya and TrustedForm verification on inquiry records
  • Phone validation with landline, mobile, and VoIP classification
  • Email validation
  • TCPA scrubbing about every three days
  • Deduplication and suppression list support
  • Instant Excel or CSV download
  • 95%+ marketable records

Cashyew also offers cash-discount-processing leads for merchant services providers who want to sell more than funding.

The Bottom Line

The best place to buy verified MCA leads is a vendor that can prove its verification, record by record, and let you test before you scale. Ask for consent certificates, line-type data, and scrub dates. Then judge every source by what you pay per funded merchant, not per record.

Ready to test a cleaner file? Browse verified MCA leads at Cashyew.com and download your first list today.

Pennsylvania Just Moved Your Calling Window. Three Weeks In, Is Your Dialer Caught Up?

Pennsylvania’s rewrite of its telemarketing law has been in force since October 18, 2026, and it is the kind of change that sits quietly in a dialer config until it causes a problem. If your campaigns still treat Pennsylvania like it did in September, you are now calling outside the legal window, texting under rules that did not apply before, and possibly relying on a consent standard the state no longer accepts.

Pennsylvania’s governor signed Senate Bill 992 on July 20, 2026. The law had a 90-day compliance runway, which put the effective date at October 18. Here is what changed on the floor, based on law firm summaries of the statute.

Texts and ringless voicemail now count

The definition of a telephone solicitation now expressly covers text messages and ringless voicemail, not just live calls. If your SMS or RVM programs ran on the assumption that Pennsylvania’s telemarketing law was a voice-only problem, that assumption ended on October 18.

The calling window got shorter

The old window was 8 a.m. to 9 p.m. The new one is 9 a.m. to 7 p.m., and solicitations on Sundays are banned entirely. Holidays were already off limits. That is three hours a day cut from your schedule, plus every Sunday, for any number tied to Pennsylvania. Check your time-zone logic too: the rule follows the person you are contacting, not your call center’s location.

Robocalls need written consent

According to Kelley Drye and Mac Murray & Shuster, the law replaces the old “express request” carve-out with a prior express written consent standard that largely tracks the federal TCPA definition. Robocalls using prerecorded or artificial voice need that written consent for residential, business and wireless lines, subject to statutory exceptions. Electronic signatures count. The established-business-relationship exception survives.

The law also prohibits unfair or deceptive practices to obtain consent and bans using synthetic or computer-generated messaging to defraud, deceive or mislead. Operators running AI voice agents should have their scripts reviewed with that language in mind.

No spoofing, and the brand is on the hook

Telemarketers may not falsify their caller ID name or number. The prohibitions reach anyone who “initiates or causes to be initiated” a solicitation, which TCPAWorld reads as extending liability to the company that hired the telemarketer. If you buy outbound from a vendor, their mistakes in Pennsylvania are now more clearly yours.

Penalties remain up to $1,000 per violation, or $3,000 when the person contacted is 60 or older. The Attorney General and district attorneys can enforce. Commentators disagree on how easily consumers can sue on their own under the state’s consumer protection law, so do not plan around a quiet plaintiffs’ bar.

The state is paying attention

This is not a sleepy statute. Attorney General Dave Sunday co-led a bipartisan coalition that in July urged the FCC to toughen “Know Your Customer” obligations for voice providers, citing an estimated one billion robocalls to Pennsylvanians the year before. A state AG that engaged on carrier policy is not likely to ignore a fresh telemarketing law.

Your three-week audit

  • Pull Pennsylvania numbers into their own calling-window rule: 9 to 7, no Sundays, no holidays.
  • Apply the same window to SMS and RVM, not just voice.
  • Audit consent records for robocall and prerecorded campaigns against a written-consent standard.
  • Confirm all seven opt-out words (stop, quit, end, revoke, opt out, cancel, unsubscribe) are honored.
  • Get written assurances from vendors, since liability flows back to you.

State mini-TCPAs like Pennsylvania’s tend to draw the same repeat plaintiffs who work the federal statute. Scrubbing your lists through TCPALitigatorList.com before you dial flags known TCPA litigators so a Sunday text to the wrong person does not turn into a demand letter.

Pennsylvania just joined the growing list of states with their own calling rules. The operators who handle that best treat state rules as data in the dialer, not a memo in a shared drive.

Sources

The FCC’s New Opt-Out Rules Hit on November 25. Here’s the Operator’s Checklist.

If you run calls or texts at volume, put November 25, 2026 on the wall. That is the day the FCC’s revised TCPA consent-revocation rules take effect, the day before Thanksgiving. The rules change how “stop” works for informational messages, let callers name the channels they will accept opt-outs through, and widen an exemption banks rely on for fraud alerts. They do not loosen anything for telemarketing.

The Commission adopted the Report and Order and a Further Notice of Proposed Rulemaking on September 30, 2026. Both were published in the Federal Register on October 26, which started the clock. Comments on the new proposals are due the same day the rules take effect, November 25, and reply comments are due December 28.

Why this matters on the floor

For two years, operators have been planning around a broad “revoke all” requirement: a consumer who opts out of one kind of robocall or robotext from you would be treated as opting out of everything. That requirement kept getting delayed, most recently to January 31, 2027. The new order replaces that approach for informational traffic with a narrower, category-specific framework.

In practice, a customer who texts STOP to your payment reminders can still get fraud alerts, appointment reminders and similar informational messages from you. That is a big deal for servicing, collections and healthcare scheduling teams, who were bracing for a single opt-out to shut down every non-marketing message.

What did not change

Telemarketing is where operators should be careful not to over-read the headlines. The narrower framework does not apply to advertising or telemarketing. If someone revokes consent in response to a marketing call or text, that revocation still covers all of your future marketing robocalls and robotexts. Your sales and promotional lists should treat an opt-out as global, just as before.

The deadline to honor a revocation also stays put: a reasonable time, not more than ten business days after you receive it.

The new tool: exclusive opt-out methods

Starting November 25, a caller can designate exclusive methods for revoking consent. The order lists three:

  • An automated, interactive voice or key-press opt-out during the call.
  • A reply text using any of seven words: stop, quit, end, revoke, opt out, cancel or unsubscribe.
  • A website or phone number the caller designates for opt-outs.

The method has to be clearly and conspicuously disclosed. If you tell texters to reply STOP, you still have to honor all seven words. Callers that designate an exclusive method do not have to process revocations sent some other way. Callers that do not designate one must keep honoring any reasonable method. Counsel at CommLaw Group also caution not to switch this on before the 25th, and note that separate mandated opt-outs for certain prerecorded telemarketing calls still apply.

The operator’s checklist

  • Tag every message stream as informational or telemarketing. The rules now treat them differently, so your suppression logic must too.
  • Map opt-outs to categories for informational traffic, and keep marketing opt-outs global.
  • Decide on exclusive methods, then update scripts, IVR prompts and text templates with the disclosure language before the 25th.
  • Parse all seven keywords on every inbound text channel, not just STOP.
  • Measure time-to-suppress. Ten business days is the ceiling, and the FCC is asking whether to cut it to seven.

What’s next

The FNPRM asks whether to shorten the ten-business-day window to seven, require two-way texting so consumers can always reply, make category-specific treatment depend on also offering a one-step “revoke all” option, and clarify how affiliates and separate business divisions are treated. None of that is final, but each would land on the same systems you are touching now. Build with headroom.

Clean opt-out handling is half the battle; the other half is knowing who you are dialing. Many TCPA suits come from a small group of repeat plaintiffs who know these rules better than most compliance teams. TCPALitigatorList.com lets outbound teams screen their lists against known TCPA litigators before a campaign goes out, so a rule change does not become someone’s next demand letter.

The bottom line for operators: November 25 gives informational programs some room, keeps marketing just as strict, and rewards teams whose opt-out plumbing is already tidy.

Sources

Ask It Once, Answer It Right: An Operator’s Guide to FAQ Pages AI Engines Quote

Most FAQ pages were built for one of two reasons: to cut down on support tickets, or to win a rich result in traditional search. Neither goal produced pages that are especially good at what AI answer engines now need from them. When a buyer asks an assistant a direct question about a product, a policy or a process, the system goes looking for a passage that answers that exact question clearly and can be lifted without losing its meaning. A well-run FAQ page is one of the most natural places for that passage to live. A neglected one is a common source of stale or contradictory answers.

Start with an honest inventory

Before writing anything new, find every place your organization already answers questions in a Q&A format. The list is usually long: the main FAQ page, product-level accordions, pricing page FAQs, help articles framed as questions, old campaign pages and sales PDFs. For each one, record the URL, the owner, the last time it was reviewed, and whether the answers still match what is true today.

The output of this step is usually uncomfortable. The same question is often answered three different ways, with different numbers, different eligibility rules or different product names. AI systems that encounter those conflicts have no reliable way to know which version is current, so they may blend them or pick the wrong one. Fixing conflicts is worth more than adding new questions.

Choose questions from real demand, not brainstorming

The best FAQ questions come from places where customers have already typed or spoken them:

  • Support tickets and live chat transcripts, grouped by theme
  • Site search logs, especially searches that returned nothing useful
  • Questions sales teams hear on calls before a deal closes
  • The questions you see when you ask AI assistants about your category and your brand
  • Reviews that mention confusion about how something works

Keep the customer’s wording where you can. If people ask “Can I cancel anytime?” rather than “What is the subscription termination policy?”, the first phrasing belongs in your heading.

Write answers that survive being quoted alone

An AI engine may cite a single answer without any of the page around it. Each answer therefore needs to stand on its own. In practice that means:

  • Answer in the first sentence. Yes, no, a number, a timeframe or a clear statement, then the qualification.
  • Name the subject. Write “The Pro plan includes three user seats” rather than “It includes three seats.”
  • State conditions explicitly. If the answer varies by region, plan or product, say so in the answer rather than in a footnote.
  • Date anything that changes. Prices, deadlines, availability and policy terms should carry a visible “as of” date or a last-reviewed date.
  • Link instead of restating. If the full policy lives elsewhere, summarize briefly and link to the source of truth so you maintain the detail in one place.

Fix the format problems that hide answers

Many FAQ sections are technically present but practically invisible. Common culprits include answers that only load after a click through client-side JavaScript, questions stored as images, accordions that render empty HTML until expanded, and FAQs embedded in third-party widgets on another domain. Check the raw HTML of each priority page. If the answer text is not in the page source or the rendered DOM without interaction, assume some crawlers will miss it.

Use real heading elements for questions, keep one question per heading, and avoid stuffing several unrelated questions into a single block. Group questions under clear subheads such as Billing, Setup or Shipping so both readers and machines can tell what each section covers.

A note on FAQ markup

FAQPage structured data can help machines understand the question and answer pairs on a page, but it is not a shortcut. Search engines have narrowed where FAQ rich results appear, and markup that does not match the visible page is a liability. Only mark up questions and answers that appear on the page exactly as written, and remove markup when you remove or change the content.

Decide where each question belongs

One giant FAQ page is rarely the right answer. A better pattern is a small number of focused FAQ sections placed where the question naturally arises: billing questions on the pricing page, compatibility questions on the product page, returns questions on the policy page. A central FAQ hub can still exist, but it should link out to those canonical answers rather than duplicating them. When a single question becomes important enough, such as a frequent pre-purchase objection, give it a dedicated page with a fuller explanation.

Put FAQs on a maintenance schedule

FAQ content decays quietly. Assign every FAQ section an owner, add FAQ review to the checklist for any pricing, policy or product change, and set a recurring review date for anything time-sensitive. When an answer is no longer true, update it or remove it. Leaving outdated answers in place is how brands end up with assistants repeating policies they retired long ago.

Measure whether the answers are being used

Keep a short list of the questions your FAQ content is meant to answer and test them in the AI assistants your customers use, on a regular schedule. Note whether the answer is correct, whether your page is cited, and which other sources appear instead. Track support volume on the same themes as a second signal: if a rewritten answer is clear enough for an AI engine to quote, it is usually clear enough to prevent a ticket.

Teams that want help building this kind of question-led content program into a wider strategy can look at generative engine optimization services that cover audits, content and ongoing prompt testing.

The operator’s takeaway

FAQ pages sit exactly where customer questions and machine-readable answers meet. Inventory them, resolve conflicts, write answers that make sense out of context, make sure the text is in the page, and give someone the job of keeping it true.

Brief the Writer, Not the Algorithm: An Operator’s Template for GEO-Ready Content Briefs

Most teams that take generative engine optimization seriously eventually hit the same wall. The strategy deck is clear, the prompt set is built, the audit has found the gaps, and then a writer opens a blank document and produces a page that reads like every other page on the internet. The problem is rarely the writer. It is the brief. A traditional SEO brief tells a writer which keyword to target, how long to go, and which competitors to beat. That is not enough information to produce a page an AI answer engine will quote, summarize or recommend.

Here is an operator’s template for briefs that close that gap.

Why the old brief falls short

Answer engines do not rank a page and send a visitor. They read a set of sources, pull out passages that answer a question, and assemble a response. A page earns a place in that response when it contains clear, self-contained, verifiable statements that match what people actually ask. Keyword targets and word counts say nothing about any of that. A writer working from a keyword brief will optimize for coverage and length, and will often bury the one sentence that matters under three paragraphs of context.

A GEO-ready brief shifts the writer’s attention from “what term am I ranking for” to “what questions must this page answer, and what facts must it state so plainly that a machine can lift them without distortion.”

The template, section by section

1. The question set

Start with the real questions the page needs to answer, written in the words customers use. Pull them from your prompt-testing set, support tickets, sales call notes and on-site search. Group them into a primary question the page exists to answer and a handful of follow-ups people tend to ask next. If a question belongs on a different page, say so in the brief, so the writer does not try to answer everything in one place.

2. Current AI answers

Paste in what two or three assistants currently say when asked the primary question, along with the sources they cite where visible. Mark what is wrong, what is missing and what is outdated. It shows writers the gap they are filling instead of asking them to imagine it.

3. The answer in one or two sentences

Before any drafting, the brief owner writes the direct answer to the primary question in plain language. This becomes the opening of the page or of the relevant section. Writers can improve the wording, but they should not bury it. If the team cannot agree on a two-sentence answer, the page is not ready to be written.

4. Key facts and their source of truth

List every factual claim the page must make: names, numbers, dates, prices, eligibility rules, specifications, locations. Next to each, record where the approved version lives and who owns it. This protects against a common GEO failure, a new page contradicting an older one, and it makes future updates far easier because everyone knows where each fact came from.

5. Evidence and expertise

Note who the named author or reviewer will be and why they are qualified. List the evidence the page should reference: customer stories, original data, documentation, third-party coverage. Answer engines tend to favor material that shows its work, and a brief that names its evidence up front produces a page that does the same.

6. Structure requirements

Specify the structural elements that help extraction:

  • Descriptive subheadings phrased close to the follow-up questions
  • Short paragraphs where each one can stand on its own if quoted
  • A table when the content compares options, plans or specifications
  • Lists for steps, requirements or criteria
  • Any structured data the page should carry, and the visible content it must match

7. Boundaries

Say what the page should not do. Common entries: no claims compliance has not approved, no restating facts that live on another canonical page (link instead), no internal product names customers never see, and no overstatement. Honest pages hold up better when an assistant cross-checks them against other sources.

8. Links in and out

Name the existing pages that should link to the new one and the pages it should link to. Internal links help both people and crawlers understand where the page sits, and assigning them in the brief means they actually get added at publish time rather than forgotten.

9. Success check

Define how you will know the page worked. Usually this is a re-run of the question set a few weeks after publishing, a check that the key facts now appear correctly in AI answers, and whatever traffic or conversion signal matters to the business. Write the check into the brief so it gets scheduled rather than hoped for.

Running briefs as a system

A template only helps if it is used consistently. A few operating habits make the difference:

  • One owner per brief. Someone who can resolve disputes about facts and wording, not just a project manager.
  • Short review loops. Have subject experts review the answer and key facts sections before drafting, not the finished draft. Corrections are cheaper at that stage.
  • Keep briefs after publishing. Store them alongside the page. When a fact changes, the brief shows exactly what to update and what else depends on it.
  • Feed results back. When the success check shows a page is not being picked up, note what was different about pages that are, and adjust the template.

Where to start

If your team wants an outside view on how its briefs, content and measurement fit together, working with a partner that offers generative engine optimization services can help set the template and the review rhythm. Either way, start with the next page on your calendar. Write the question set, paste in the current AI answers, and agree on the two-sentence answer before anyone starts drafting. That one habit often does more for AI visibility than another round of technical fixes.

The Newsroom Nobody Visits Is the One AI Reads: Rebuilding Your Press Page as a Source of Record

Ask most operators when they last looked at their company newsroom and you will get a shrug. It is the page where press releases go to sit, often years deep, frequently built on an old template, sometimes half migrated to a PR distribution platform. Human visitors rarely browse it. That does not mean nobody reads it.

A newsroom contains exactly the kind of material AI systems look for when they describe a company: founding details, leadership names, product launches, acquisitions, funding, partnerships and official statements. When a generative engine answers a question about your business, those pages can become part of the evidence, including the ones that are years out of date. Treating the newsroom as a source of record, rather than an archive, is one of the more neglected jobs in generative engine optimization.

What goes wrong in a typical newsroom

The problems are predictable once you look:

  • Undated or vaguely dated releases. A release that says “today we announced” without a visible date reads as current forever.
  • Superseded facts with no signal. An old release names a CEO who left, a product that was renamed, or a headcount that has since doubled.
  • Releases trapped in PDFs or images. The text exists, but not in a form that is easy to read, quote or link.
  • Boilerplate drift. The “About the company” paragraph at the bottom of each release changes over the years, so the newsroom contradicts itself.
  • Duplicates elsewhere. The same release lives on wire services and partner sites, sometimes in slightly different versions.

None of this is unusual. But each issue gives an AI system a chance to repeat something that is no longer true.

Step 1: Inventory what you have

Export a list of every newsroom URL with its title, publication date and format. Flag anything without a visible date, anything published only as a PDF, and anything that mentions people, products, prices, locations or company size. Those are the facts most likely to be stale.

While you are at it, note where the same announcement appears off-site. You cannot control every syndicated copy, but you should know which version is canonical.

Step 2: Make every release dated and self-contained

Each release should show its publication date near the top in plain text. The opening paragraph should state the news in one or two sentences that make sense without the headline: who did what, when, and why it matters. That is good press writing anyway, and it gives an AI system a passage it can lift accurately.

Convert PDF-only releases to HTML pages. Keep the PDF as a download if your communications team wants it, but make the HTML version the primary page.

Step 3: Mark history as history

Do not delete old releases just because the facts changed. They are part of the public record, and removing them can break links from press coverage. Instead, add a short, visible note to releases whose key facts are superseded. For example: “Update: this product was renamed in 2025. See the current product page.” Link to the current source.

This keeps the archive honest. A reader, or a machine, that lands on the old page is told plainly that the information has a successor.

Step 4: Standardize the boilerplate

Write one current company description and use it on every new release, your About page and your media kit. You do not need to rewrite the boilerplate on every historic release, but the most recent ones should match. Consistency across your own pages is the cheapest form of corroboration you have.

Step 5: Build a newsroom landing page that answers basic questions

The newsroom index is often a reverse-chronological list and nothing else. Add a short fact block at the top with the details journalists and AI systems ask for most:

  • Company name and any former names
  • Founding year and headquarters
  • Current leadership with links to bio pages
  • A one-paragraph description that matches your About page
  • Media contact details and a link to brand assets

Keep this block current. It should be the first thing updated when leadership, location or naming changes.

Step 6: Add structure without overdoing it

Use clear headings, real text and consistent URLs. Article or NewsArticle markup can describe each release, including its publication and modification dates, as long as those dates match what the page shows. Do not add markup claims that are not visible on the page.

Step 7: Put the newsroom in the change process

Most stale newsroom content happens because nobody connects company changes to the press archive. Add the newsroom to the checklist for leadership changes, rebrands, product renames, office moves and acquisitions. When one of those happens, someone updates the fact block, adds supersession notes to the affected releases and checks that the boilerplate is current.

Check what the machines say

Once the cleanup is done, ask a handful of AI assistants basic questions about your company: who runs it, when it was founded, what it sells, and what it announced recently. Note which answers are wrong and which sources are cited. If an outdated release keeps surfacing, that page needs a clearer update note or a stronger link to the current information.

Operators who would rather not run this alone can bring in a specialist GEO team to audit the archive. The core idea stays simple: your newsroom is already being read. Make sure it tells the current story, and tells the old ones as history.