CX Dialer Guidelines November 2026

Bob Barnes

Research date: 18 November 2026 · US and Canada

TLDR Suggestions:

·       Focus on/understand summary tables

·       Understand – 05 Genuinely New

·       Review – 07 Timeline - What is coming next

·       Review – 08 Practice Today

Introduction

Outbound contact centers · Dialer pacing & “hold time”

There is no “hold time between calls” rule. Here is what is actually regulated:

No jurisdiction researched sets a minimum pause, wrap-up, or rest period between one outbound call and the next for an agent. What regulators police — tightly — is the mirror image: how long a person who just answered waits in silence, how many of those waits may end in abandonment, and how soon you may try the same person again.

Bottom line for a US operator today

The 2-second connect, 3% abandonment, and 15-second / 4-ring rules are still in force — do not dial to the FCC’s proposed rollback. Layer state frequency caps and hours on top, honor revocations within 10 business days, and have systems ready for the revocation change taking effect 25 November 2026.

Key Metrics To Monitor

2 Seconds

US & Canada — from the person’s completed greeting, or play a compliant message.

3% / 5%

Abandonment caps

US ≤3% per campaign per 30 days · Canada ≤5% per calendar month · UK: no cap.

3 in 24h

Same-person retry cap

FL, OK, MD & OR (from 1 Jan 2026) — same subject, any number dialed from.

72 hrs

UK post-abandonment cooldown

No repeat call after an abandoned call unless a live agent is guaranteed.

01 · Clarifying the question

Four different things get called “hold time between calls”

Only three of them are regulated as dialing rules. The fourth — the agent’s own pause — is not.

1 · Consumer hold / dead air after answering Regulated

Time to connect a live agent, or play a compliant recorded message, after the person answers. US / Canada: 2 seconds from the completed greeting. UK: information message no more than 2 seconds after answer or speech starts.

2 · Abandoned & silent calls Regulated

Share of live answers that may be abandoned, minimum ring time before hanging up on a no-answer, and required message content. US 3% / 30 days / campaign; 15 sec or 4 rings. Canada 5% / month. UK: no safe harbour.

3 · Interval between attempts to the same person Regulated

Attempts per period, post-abandonment cooldowns, calling hours, and opt-out honoring periods. FL / OK / MD / OR: 3 in 24 hours. UK abandoned-call cooldown: 72 hours. Federal US hours 8am–9pm; many states 8am–8pm. There is no federal US per-day attempt cap.

4 · Agent pause / wrap-up / ACW / rest NOT a dialing rule

No dialing-specific regulation found anywhere researched. Governed only by general wage-and-hour / working-time law — e.g., in the US, after-call work is compensable and short breaks of ~5–20 minutes must be paid under the FLSA. Any claim of a legally mandated “wrap-up time” is best practice, contract, or workforce management — not law. See Agent-side rules.

Why answering-machine detection (AMD) is a compliance control

AMD listens before deciding human vs machine, consuming part of the 2-second window. A false positive, meaning a live person classified as a machine and hung up on — counts as an abandoned call. AMD tuning is therefore a compliance variable, not just a productivity one.

02 · Summary Table Federal Rules

Rules by jurisdiction, at a glance

Jurisdiction

Connect / message deadline

Abandonment cap & window

Min ring

Repeat / frequency

Hours

’24-’26 Change

US — FCC / TCPA

Live rep within 2 sec of completed greeting, else compliant recorded message + automated opt-out

≤3% live-answered, per campaign, 30 day

15 sec / 4 rings

No federal per-day cap; revocation honoured ≤10 business days

8am–9pm residential

Core 2003, in force. AI-voice rule 2024 in force. Revocation replacement eff. 25 Nov 2026. Deletion of 3% / 15-sec proposed Oct 2025, not adopted

US — FTC / TSR

Same 2-sec definition

≤3% safe harbor (all 4 conditions), campaign / successive 30 days

15 sec / 4 rings (safe harbour)

-

8am–9pm

Abandonment figures unchanged. 2024: B2B misrepresentation + 5-year records. Jan 2025: tech-support inbound

US states (strictest)

NY / WA: ID within 30 sec; WA: end within 10 sec on request; CA: live-voice preamble before ADAD message

State law incorporates federal abandonment via mini-TCPAs in some states

-

FL / OK / MD / OR: 3 in 24h, same subject / person

FL / OK / MD / OR / WA 8am–8pm; TX 9–9 (noon Sun)

MD 2024, CA / NY / TX 2025, OR / VA 2026 — in force

Canada — CRTC

Live telemarketer within 2 sec

≤5% per calendar month; monthly records 3 years

No rule found

Internal DNC: add in 14 days, keep 3 yrs + 14 days

Weekday 9am–9:30pm, weekend 10am–6pm

2007/08 rules in force; enforced Dec 2025 ($15,000 notice incl. 5% breach)

*DNC scrubbing cycles for reference: US National DNC ≤31 days · UK TPS / CTPS ≤28 days · Canada DNCL ≤31 days.

03 · United States — Federal

The 2003 core still governs. Everything around it moved.

Two federal regimes run in parallel — the FCC under the TCPA and the FTC under the Telemarketing Sales Rule. Operators must satisfy both: the FCC’s 3% is a direct cap; the FTC’s 3% is a safe-harbor condition.

FCC / TCPA baseline — 47 CFR §64.1200(a)(6)–(7), adopted 2003 In force

  • A telemarketing call is abandoned if not connected to a live sales representative within 2 seconds of the called person’s completed greeting.

  • A caller may not abandon more than 3% of telemarketing calls answered live by a person, measured over a 30-day period for a single calling campaign.

  • A caller may not disconnect an unanswered call before at least 15 seconds or 4 rings.

  • When no representative is available within 2 seconds, a recorded message must state the call was for telemarketing purposes, name the business, give a number for do-not-call requests, and offer an automated interactive (voice / key-press) opt-out that adds the number to the seller’s DNC list and ends the call.

  • Solicitations to residential subscribers: only 8am–9pm local time at the called party’s location, §64.1200(c)(1).

  • Penalties: TCPA private statutory damages $500 per violation, trebled to $1,500 if willful / knowing (47 USC §227(b)(3)), plus FCC forfeiture and state AG enforcement.

AI voices are “artificial” In force

Declaratory Ruling FCC 24-17, released 8 Feb 2024, effective immediately: calls made with AI-generated voices are “artificial” under the TCPA, so the consent, identification, and opt-out regime for artificial / prerecorded voice calls applies to voice-cloning and generative AI calls.

Federal AI-call disclosure Proposed only

NPRM FCC 24-84, adopted 7 Aug 2024 would define “AI-generated call,” require disclosure when consent is obtained, and require callers to disclose at the start of each AI call that AI is being used. Comments closed Oct 2024. No final rule had been adopted as of Oct / Nov 2026; trackers list it as a long-term action, next action undetermined.

Advisor warning: many vendor blogs state a federal “say it’s AI” duty as if in force. Federally it is proposed only. Binding duties today come from state law (California).

Consent revocation — the change landing 25 November 2026 Imminent

·        Core in force 11 Apr 2025 (FCC 24-24, §64.1200(a)(10)–(12)): a consumer may revoke consent by any reasonable method; callers may not designate an exclusive method; revocation must be honored within a reasonable time, not to exceed 10 business days; the words stop, quit, end, revoke, opt out, cancel, unsubscribe are per-se reasonable for texts; one confirmation message is allowed.

·        The “revoke-all” element (one revocation covering all robocalls / robotexts from that caller) never took effect on schedule — waived to 11 Apr 2026, then by DA 26-12 (6 Jan 2026) to 31 Jan 2027.

·        FCC 26-67 — adopted 30 Sep 2026, published 91 FR 67214 on 26 Oct 2026, effective 25 Nov 2026 (imminent, not yet in force on the research date): supersedes revoke-all. Callers may designate one or more of exactly three methods as the exclusive revocation method — (i) automated interactive voice / key-press opt-out on the call, (ii) reply text with one of the seven standard words, (iii) a designated website or telephone number — if clearly and conspicuously disclosed. A caller that does not designate keeps the any-reasonable-method default. An opt-out from a telemarketing call / text still revokes all telemarketing from that caller; an opt-out from an informational category may be treated as category-specific. The 10-business-day ceiling stays.

·        Its companion FNPRM seeks comment on shortening the honouring deadline (possibly to 7 business days), two-way texting, and a revoke-all option — comments / replies reported as due 25 Nov / 28 Dec 2026.

Do not rely on pre-2026 guides describing “no exclusive method, ever” or “revoke-all from Apr 2025 / 2026” without the 26-67 replacement.

Proposed rollback of the abandonment rules Proposal — not law

FCC 25-76 (“Call Branding,” adopted 28 Oct 2025), paras 97–98, seeks comment on whether to eliminate the 15-second / 4-ring rule and the 3% abandonment rule, reasoning they were adopted in 2003 for that era’s predictive dialers. Comments were due 5 Jan 2026, replies 3 Feb 2026. No order deleting (a)(6) / (7) was found; the eCFR still contained them in late Oct / Nov 2026. The same item proposes verified caller-name / Rich Call Data transmission and foreign-origin marking, and drew consumer-group opposition — the rollback is contested, not a foregone conclusion.

Two court / consent developments

One-to-one consent — vacated, never took effect. The Dec 2023 order (FCC 23-107) would have limited prior express written consent to one seller at a time for lead generation. The Eleventh Circuit vacated it in Insurance Marketing Coalition v. FCC, 24 Jan 2025, days before its start; the FCC restored the prior text effective 29 Aug 2025.

McLaughlin Chiropractic v. McKesson (US Supreme Court, 20 June 2025): district courts are not bound by FCC interpretations of the TCPA under the Hobbs Act — increasing court-by-court variance risk.

FTC Telemarketing Sales Rule — safe harbor & the 2024 amendments

Abandoned-call prohibition + safe harbour (long-standing). §310.4(b)(1)(iv): abandoning an outbound call is an abusive practice; a call is abandoned if a person answers and the telemarketer does not connect it to a sales representative within 2 seconds of the person’s completed greeting. The §310.4(b)(4) safe harbour requires all four together: (1) technology ensures abandonment of ≤3% of all calls answered by a person, measured over the campaign if <30 days, or separately over each successive 30-day period; (2) each call rings at least 15 seconds or 4 rings before an unanswered call is disconnected; (3) when no representative is available within 2 seconds, a recorded message is promptly played stating the seller’s name and telephone number (no sales pitch; number must allow a DNC request); (4) records establishing compliance are retained. TSR calling hours (§310.4(c)) mirror the FCC 8am–9pm window.

New — 2024 amendments (final rule 89 FR 26760, published 16 Apr 2024). Effective 16 May 2024: prohibition on material misrepresentations in business-to-business telemarketing (do not conflate this with the separate B2B exemption for the abandoned-call analysis in §310.6(b)(7)). Record-keeping expanded and retention raised from 2 years to 5 years under §310.5, including, from 15 Oct 2024, a record of each telemarketing call and copies of prerecorded messages. A second amendment (89 FR 99069, effective 9 Jan 2025) extends the TSR to inbound calls offering technical support services.

Penalties — verify before quoting: TSR civil penalties were cited at up to $51,744 per violation in 2024–2025 law-firm sources; the amount is inflation-adjusted annually under 16 CFR §1.98 (a 2026 secondary source cites $53,088). Caution: the FTC’s own business guide still said “two years” in its record-keeping section in late-2026 secondary reporting — the rule text (5 years) controls, not the guide.

No new TSR abandonment threshold was adopted in 2024–2026. If the FCC deletes its parallel rules, the FTC safe harbour would remain unless the FTC separately acts — a key reason not to treat an FCC deletion as deregulating abandonment altogether.

Also to watch: FCC foreign call-center proposal (FCC 26-16)

FCC 26-16 (adopted 26 Mar 2026) is an NPRM on foreign customer-service / call-center operations — onshoring incentives, standards for remaining foreign operations, possible extension to texts / email / chat. It is a customer-service proposal, not a hold-time rule, but outbound operators with offshore floors should track it.

04 · Summary Table  — By States Rules

State “mini-TCPAs”: where the litigation risk now sits

Federal law is a floor. These states add shorter hours, per-day frequency caps, text coverage, disclosure timing, or AI disclosure — and most carry a private right of action. This is a notable-states survey, not a 50-state survey.

State

Law / status

Hours

Frequency / interval

Other pacing-relevant duties

Penalties (as sourced)

Florida

Telephone Solicitation Act, §501.616(6) (2021, in force); FTSA §501.059 consent (narrowed by HB 761, 2023)

8am–8pm

Max 3 solicitation calls in 24h to a person, same subject, regardless of number used

Prior express written consent for sales calls using automated selection and dialing or prerecorded messages under §501.059

$500 / violation, trebled if willful (secondary sources)

Oklahoma

Telephone Solicitation Act 2022, 15 OS §775C.4, eff. 1 Nov 2022

8am–8pm

Max 3 in 24h, same subject, any number

Registration with AG ($250 / $100 renewal, $10,000 bond in secondary sources); “selection or dialing” — wider autodialer trigger than FL

$500 or actual damages, up to 3× if willful / knowing

Maryland

Stop the Spam Calls Act, §§14-4501–4503, eff. 1 Jan 2024; private action added Apr 2024

8am–8pm

Max 3 in 24h to same called party, same subject, regardless of numbers used (§14-4502(c)(2))

PEWC for automated selection / dialing or recorded message; B2B-type exemptions excuse only the consent rule, not hours / frequency

Up to $500 or actual damages, up to 3× if willful / knowing

Oregon

HB 3865 (2025), eff. 1 Jan 2026 — NEW

8am–8pm (moved from 9–9)

Max 3 solicitations in 24h, calls + texts combined, unless established business relationship (transaction in prior 18 months)

“Telephone solicitation” now expressly includes text messages; autodialer prompt-disconnection and opt-out duties

Unlawful trade practice under OR UTPA; private action + DOJ enforcement

California

AB 2905, eff. 1 Jan 2025 — NEW, amending Pub. Util. Code §2874

ADAD calls: no calls 9pm–9am (§2872, per secondary summary)

No per-day cap found

Before an ADAD plays a prerecorded message, a natural (live, unrecorded) voice must state the nature of the call, business name / address / phone, ask consent to hear the message, and disclose if the message uses an artificial voice (“artificial voice” = generated / significantly altered using AI). Scope limit: prerecorded robocalls via an ADAD, not a live conversational AI agent — do not overstate it as “all AI calls”

DTPA exposure incl. possible trebling + fees; AG penalties reported up to $5,000 / violation

New York

“Seinfeld Law”, eff. 1 Jan 2025 — NEW, GBL §399-z; registration §399-pp

8am–9pm

No per-day cap found

Within the first 30 seconds: telemarketer name, seller represented, purpose, whether the call is being recorded, and offer to be added to the seller’s internal DNC list. Registration: $500 fee, $25,000 bond, 2-year term (with exemptions)

Up to $20,000 per violation under §399-z (secondary source); §399-p ADAD claims $50, up to $1,000 if willful

Washington

RCW 19.158.110; RCW 80.36.390; RCW 80.36.400 (ADAD ban as amended 2023)

8am–8pm

No per-day cap found; DNC request honoured at least 1 year

Identify solicitor / company / purpose within 30 seconds; end the call within 10 seconds when asked; no person may use an automatic dialing and announcing device for commercial solicitation — no consent exception written into §80.36.400(2) in secondary readings (treat AI / prerecorded commercial solicitation into WA as high-risk and take advice)

$1,000 per robocall violation (actual damages if greater); CPA liability

Virginia

SB 1339, eff. 1 Jan 2026 — NEW, Va. Code §59.1-514

8am–9pm

No per-day cap found

A text recipient may opt out by replying STOP or UNSUBSCRIBE; solicitor must honour it for at least 10 years

$500 first, $1,000 second, $5,000 subsequent (secondary sources)

Correction to common vendor tables — Florida

Several dialer blogs attribute Florida’s 3-in-24h cap to §501.059 (the FTSA). Statute-based sources attribute the hours + frequency rule to §501.616(6) and the consent / autodialer rule to §501.059. At least one 2026 blog claims Florida has no cap after reading only §501.059 — that reading misses §501.616. Cite both sections and check exemptions. Law-firm outlook (Apr 2026): more states are expected to introduce / pass TCPA-style laws in 2026, with state enforcement and private suits rising.

05 Genuinely new

  • AI-generated voice = “artificial voice” under TCPA (FCC 24-17, Feb 2024, immediate)

  • Revocation: any reasonable method + 10 business days (Apr 2025); exclusive-method + category-specific replacement (adopted Sep 2026, eff. 25 Nov 2026)

  • TSR: B2B misrepresentation coverage + 5-year records incl. per-call records (2024); tech-support inbound coverage (Jan 2025)

  • CA AI-voice preamble disclosure (2025); NY 30-second disclosures incl. recording (2025); TX texts as solicitation + DTPA (2025); OR texts + 3 / 24h (2026); VA text STOP honoured 10 years (2026); MD mini-TCPA in force (2024)

  • UK PECR fines £500k → £17.5m / 4% (DUAA, in force Feb 2026); Ofcom CLI blocking guidance (Jan 2025)

  • EU AI Act Art. 50 AI-interaction disclosure in application (Aug 2026)

  • FCC proposals to delete the 3% + 15-sec rules (Oct 2025) and for AI-call disclosure (Aug 2024) — neither is law

06 Long-standing, now re-enforced / re-litigated

  • 2-second connect rule (US 2003; Canada 2007/08)

  • 3% abandonment cap (US, 2003) / FTC safe harbour incl. 15 sec / 4 rings

  • Canada 5% per month + 3-year monthly records

  • Calling hours: federal US 8–9, stricter states 8–8

  • DNC scrubbing cycles: US ≤31 days; UK ≤28 days; Canada ≤31 days

07 · Timeline - What is coming next

All Adopted & dated Proposals only watch list:

·       FCC 26-67 revocation amendments take effect Adopted

Exclusive opt-out methods; category-specific informational opt-outs; marketing revoke-all retained. Highest confidence — prepare scripts, disclosures, and suppression logic now.

25 Nov / 28 Dec 2026

·       Comments / replies on the 26-67 FNPRM Proposal

Shortening the 10-day honoring window (possibly to 7 days), two-way texting, revoke-all option.

2 Dec 2026

·       Former “revoke-all” date — superseded Do not plan to this

Superseded by FCC 26-67. Do not plan to this date as a standalone duty.

2026–2027 · no date

·       FCC decision on deleting the 3% + 15-sec rules (FCC 25-76) Proposal

Comments closed Feb 2026; outcome and timing unknown. Even if the FCC deletes its rules, the FTC TSR safe harbour and state laws remain unless separately changed. The same proceeding covers caller-name / Rich Call Data transmission, foreign-origin marking, and DNC clean-up.

Undetermined

·       FCC AI-generated call disclosure final rule (FCC 24-84) Proposal

No final rule as of Nov 2026 (“long-term” action). State / EU disclosure duties are filling the gap.

2026–2027

·       More state mini-TCPAs; possible UK CLI extension Directional

More US state mini-TCPAs / text expansions expected (law-firm outlook); possible UK extension of CLI blocking to spoofed UK mobile numbers. Directional, not dated law.

Potentially Apr 1, 2027

08 · Practice today

How businesses are currently managing compliance

Practices below are industry practice / vendor capability descriptions, not law. Vendor figures are labelled.

Dialer mode is the primary control

Operators match mode to risk: preview (agent sees the record, initiates the call — no over-dial, safest), progressive (1 call per available agent — near-zero abandonment), power (fixed ratio >1:1), predictive (algorithm over-dials on predicted answer rate and availability — highest talk time, structural abandonment, needs a large agent pool). Leading vendors treat predictive pacing, campaign rules, callable-time sets, DNC checks, and maximum-attempt settings as one configured system, and notes AMD can be disabled for compliance reasons so agents handle every connected call. Parallel dialing is subject to the same 2-sec / 3% analysis for dropped simultaneous answers.

Pacing with an internal buffer — never to 3.0%

Mature floors set an internal ceiling well below the cap (commonly cited operating targets 1–2%; vendor case studies claims routinely below 1% Vendor claim) because the US measurement is per campaign over a rolling 30 days — a bad hour early in the window cannot be averaged away by blending campaigns. Pacing inputs: live answer rate, average handle time including ACW, shrinkage, AMD false-positive rate, and list quality.

AMD tuning: too aggressive → live humans dropped = abandoned calls; too loose → agents burned on machines. UK-facing practice is to randomly sample paced calls to estimate the AMD false-positive rate, feed it into the abandonment calculation and pacing algorithm, calculate the rate over a fixed 24-hour period for Ofcom purposes, and use “assured / guaranteed connection” dialing for repeat calls.

Messaging, attempt controls & scrubbing

  • Abandoned-call messaging: pre-recorded, non-sales messages meeting FCC content (purpose, business name, DNC number, automated opt-out) / FTC content (seller name + number) / Ofcom content (identity + opt-out route), triggered within the 2-second window, with the event logged. A message does not erase the abandonment from the US 3% count (except the narrow consented prerecorded-campaign exception in §64.1200(a)(7)(ii)).

  • Attempt controls: campaign-level maximum attempts, retry intervals, and state caps (3 / 24h in FL / OK / MD / OR) enforced in the dialer, not in agent behaviour; time-zone callable sets applying the strictest window (often 8am–8pm) per record.

  • Scrubbing: National DNC (US version ≤31 days; Canada ≤31 days), internal DNC, TPS / CTPS in the UK (≤28 days), plus litigator / known-complainant lists in US practice; consent records retained to the new 5-year TSR standard.

Forecasting, compliance dialers, QA & callbacks

  • WFM: Erlang-style forecasting treating ACW, coaching, breaks, and adherence as unavailable time; blended floors throttle predictive pacing in real time to protect inbound levels; supervisors monitor live abandonment rate, AMD rate, occupancy, and dead-air reports with automatic cutback — abandonment is usually a staffing-forecast failure before it is a dialer failure.

  • Compliance / human-initiated modes: Five9 markets Manual Touch Mode and, via Acqueon, a Compliance Rules Builder (DNC, state timings, mode / channel rules, consent, TCPA / mini-TCPA / Ofcom rule sets) Vendor documentation. NiCE markets Personal Connection “no-pause” predictive and SmartReach / Human Call Initiator — a case study claims ~80% of predictive productivity with abandonment below 1% Vendor claim.

  • Recording / QA: full recording with retention aligned to record rules (US TSR 5 years; Canada 3 years; UK ≥6 months), speech analytics for disclosure / opt-out failures, and per-campaign reporting in the regulator’s own window (30 days US, calendar month Canada, 24 hours UK practice).

  • Callbacks & omnichannel: scheduled callbacks instead of repeated predictive attempts, voicemail drop where lawful, shifting follow-up to consented SMS / email — now itself regulated (TX / OR / VA text rules), so “move it to text” is no longer a compliance shortcut.

09 · Planning ahead

How businesses are planning to manage in future

This section is vendor marketing and industry direction, clearly separated from law. None of these announcements changes a legal threshold.

AI voice agents as the “no-hold” answer — with a consent trade

An AI agent speaks immediately on answer, so there is no 2-second wait for a human — but the call becomes an artificial-voice call (US: prior express written consent + revocation regime; CA: preamble disclosure for ADAD prerecorded messages). The planning assumption in current vendor content: disclose AI in the opening line everywhere, even where (US federal) it is still only proposed. Leading vendors launched a new Voice AI Agents release in Q2/Q3 2026.

Compliance as a separate orchestration layer

The clearest 2026 product signal: Partner provided solutions layered on top of CX solutions deliver integrated outbound compliance solution for Customers — a compliance / orchestration layer on top of core CX platforms, with “built-in safeguards including time-of-day restrictions, frequency controls, and audit-ready records” and orchestration for “human-first or agentic-first” campaigns Vendor announcement.

Real-time, availability-aware pacing

Roadmaps across market leading vendors emphasize pacing that ingests real-time agent / AI availability, predicted ACW, and campaign abandonment burn-down and auto-throttles before a cap is breached, plus “compliance abandon rate” as a first-class campaign setting

Safer modes + human-in-the-loop + caller identity

  • Shift to preview / progressive / human-initiated for regulated and high-value work, reserving predictive for large, consented, low-risk pools. Human-in-the-loop AI (AI handles opening, qualification, voicemail, and after-call summarisation; a human takes the live conversation) is the dominant stated design in 2026 vendor material from Dialpad, RingCentral RingCX, and NiCE.

  • “Compliance by default” claims — test them. NiCE markets platform-level enforcement of “consent, dialing rules, branded caller ID, and auditability” and controls that “automatically update as regulations change” Vendor claim — no platform can transfer the seller’s legal liability; Genesys’ own material states the customer owns compliance. Test any “TCPA compliant dialer” claim against: measurement-window configuration, AMD false-positive handling, state-cap enforcement, revocation-method handling after 25 Nov 2026, and record export for the 5-year TSR / 3-year CRTC regimes.

  • Caller identity as infrastructure: STIR / SHAKEN attestation, branded calling / Rich Call Data (the subject of FCC 25-76’s main proposals), and number-reputation management are being bought as answer-rate and trust controls.

10 – Leader checklist — what to do before 25 Nov ‘26

1) Confirm dialers still pace to the in-force 2-sec / 3% / 15-sec rules, with an internal buffer (1–2%).  

2) Decide whether to designate an exclusive revocation method under FCC 26-67 — and if so, script the clear-and-conspicuous disclosure.  

3) Verify state caps (3 / 24h) and hours are enforced in the dialer per record, including texts in OR / TX / VA.  

4) Confirm records retention meets the 5-year TSR standard.  

5) If AI voices are in use or planned, map consent + opening-line disclosure by jurisdiction (CA / EU duties are binding; the federal duty is still proposed).

Sources

US federal — primary / official

  • FCC 25-76, Call Branding FNPRM / NPRM (28 Oct 2025), paras 97–98 — docs.fcc.gov — VL

  • FCC, “FCC Makes AI-Generated Voices in Robocalls Illegal,” FCC 24-17 (8 Feb 2024) — fcc.gov — VL

  • FTC, Telemarketing Sales Rule final rule page (Apr 2024 amendments) — ftc.gov — IX

  • FTC tech-support TSR amendment, 89 FR 99069 (eff. 9 Jan 2025) — federalregister.gov — IX

  • FCC 26-16, foreign call-center NPRM (Mar 2026) — docs.fcc.gov — IX

US federal — law-firm / specialist summaries & rule text

  • Keller Heckman via Legal500, FCC Oct 2025 Call Branding NPRM — legal500.com — IX

  • Legal500, FCC Aug 2024 AI calls NPRM (FCC 24-84) — legal500.com — IX

  • JD Supra, FCC 26-67 exclusive opt-out rule (eff. 25 Nov 2026) — jdsupra.com — IX

  • Herzog, FCC Amends TCPA Consent Revocation Rules — herzoglaw.co.il — IX

  • Goodwin via JD Supra, TCPA and Mini-TCPAs, Looking Ahead to 2026 — jdsupra.com — IX

  • NCLC, Nine New or Revised FTC Rules Released in 2024 — library.nclc.org — IX

  • K&L Gates via Legal500, Texas SB 140 one year on — legal500.com — IX

·        Sources: FCC 25-76 para 97 summarizing (a)(6),(7) — docs.fcc.gov (verified live) · rule summaries — imisofts.com, imisofts.com · penalties — leadcompliant.com (index)

·        Sources: FCC 25-76 text — docs.fcc.gov (verified live) · legal500.com · opposition — nasuca.org (index)

·        Source: FCC news release — fcc.gov (verified live)

·        Sources (index): legal500.com · nextlevel.ai

·        Sources (index): jdsupra.com · herzoglaw.co.il · history — jeffapierson.com

·        Sources (index): visionxlab.com · jdsupra.com

·        Sources (index): ftc.gov · library.nclc.org · federalregister.gov · imisofts.com · impactdialing.com

·        Source (index): docs.fcc.gov

·        Sources (index): privacylawnetwork.com · mgaleg.maryland.gov · Oregon — start.telgrow.cc, jdsupra.com · Texas — legal500.com · California — imisofts.com, botnotice.app · New York — apps.cio.ny.gov, imisofts.com · Washington — imisofts.com · Virginia — dls.virginia.gov

Canada · Agent-side · Practice

Vendor Sources:

·       Sources (index): nice.com · dialpad.com · smartcustomerservice.com

·       Source (index): qvccs.com

·       Source (index): smartcustomerservice.com

·       Source (index): smartcustomerservice.com

·       Source (index): enu.docs.genesys.com (Ofcom)

·       Sources (index): documentation-be.five9.com · nice.com · nice.com (case study)

·       Sources (index): enu.docs.genesys.com · getvoip.com

 

© 2026 Sherman Advisors – Technology Consulting

© 2026 Sherman Advisors · Technology operations, unified.

Technology consulting for complex organizations