TCPA Compliant Dialer 2026: One-to-One Consent + Vendor Comparison

What changed on January 27, 2025

The FCC's one-to-one consent rule (announced 2023, effective January 27, 2025 after court delay) re-interpreted TCPA's "prior express written consent" requirement. Under the new rule:

• Consent must be specific to each seller placing the call
• A consent form listing "us, our partners and our affiliates" no longer satisfies the rule
• Each seller must have its own documented consent — captured separately
• The consent must be logically and topically related to the interaction at the point of capture

The practical effect: lead generators, affiliate networks and any business that historically relied on aggregated consent forms had to rebuild their consent capture flows.

The rule applies to:

• Telemarketing calls to consumer cell phones
• Pre-recorded messages to consumers
• Non-emergency informational calls to cell phones using auto-dialer technology

It does NOT apply to:

• Calls placed manually (not via auto-dialer)
• Business-to-business calls
• Calls to landlines without pre-recorded messages
• Existing-customer service calls within the scope of the original relationship

The 3% abandonment cap (still in force)

Predictive dialers must not abandon more than 3% of connected calls in any given 30-day period. A call is "abandoned" when the dialer connects a consumer but no agent is available within 2 seconds.

Compliant predictive dialers enforce this by:

• Real-time abandonment-rate calculation per campaign
• Automatic switch to lower pacing when the rate approaches the threshold
• Per-campaign audit log of abandonment rate over 30-day windows
• "Safe harbor" auto-message played when no agent is available

Violations of TCPA's 3% cap carry $500-$1,500 per call statutory damages plus enhanced damages for willful violations. Class actions routinely seek $1B+ in damages.

DNC scrubbing requirements

• National Do Not Call Registry scrubbing within 31 days
• Internal DNC list maintenance and 5-year retention
• State DNC list scrubbing where state laws differ from federal
• Stop-call request honored within reasonable time (typically same day)

CCaaS vendors that ship native TCPA tooling automate all four requirements. Vendors that don't require integration with third-party TCPA tools (Gryphon, Contact Compliance Solutions, etc.).

Vendor-by-vendor TCPA tooling depth

Why Five9 has deeper TCPA tooling than the rest

Five9 was founded in 2001 as an outbound-focused contact center. Its codebase has accumulated 20+ years of outbound-specific features — predictive dialer pacing math, TCPA case-law updates, DNC scrubbing automation, consent capture flows and audit log formats that match FCC and FTC investigation requirements.

The pillar review on this site documents the outbound depth: Five9 vendor review. For a head-to-head against the other 2025 Gartner Leader most often shortlisted alongside it, see Five9 vs Talkdesk.

This doesn't make Five9 the right choice for every outbound deployment — NICE CXone and Genesys Cloud CX have closed most of the gap, and a buyer choosing on AI / omnichannel breadth may legitimately pick them. But for a TCPA-heavy outbound deployment (collections, sales, lead-gen), Five9 is the safest default.

One-to-one consent capture: implementation pattern

Whatever vendor you pick, the implementation pattern looks like:

1. Capture form lists exactly one seller name (your company), no "affiliates" / "partners" language
2. Capture timestamp, IP address, form URL, consent text version
3. Store immutably in the dialer's audit log
4. Surface at dialer time — when the agent or auto-dialer reaches a number, the system confirms valid consent exists
5. Re-consent on lapse — consent doesn't expire under federal TCPA but state laws may; conservative default is 12 months
6. Honor stop-call requests within 24 hours and propagate across all campaigns

Vendors that ship native one-to-one consent capture handle steps 3-6 automatically. Build-your-own approaches (Amazon Connect Lambda, Twilio Flex custom flow) require dev effort.

Common TCPA violations that drive class actions

1. Calling numbers ported to wireless without rescrubbing. Number portability database changes must trigger re-scrub before dialing.
2. Calling beyond consent scope. Consent for product A used to dial product B (sales practice that pre-dated one-to-one consent rule).
3. Stale internal DNC list. Stop-call request honored on Campaign 1 but not propagated to Campaign 2.
4. Pre-recorded message without explicit opt-in. Auto-dialer plays a pre-recorded prompt to a non-consenting number.
5. Abandonment rate breach hidden by per-campaign math. Aggregate rate looks fine; individual campaign hits 7%.
6. Time-of-day violations. Federal rule restricts calls to 8am-9pm local time. State rules vary.
7. Caller ID violations. Spoofed or unrecognizable caller ID; under TRACED Act, must transmit accurate caller ID.
8. Stop calling list interpretation. "Don't call me" verbally counts; "don't call me at this number" does not extend to a different number on the same account.

Procurement checklist for TCPA-heavy outbound

1. Audit log immutability. Consent records, DNC scrub history and abandonment rate history must be tamper-evident.
2. One-to-one consent UI. Vendor must show, per-call, the specific consent that authorized the dial.
3. Real-time 3% cap enforcement with auto-throttling rather than after-the-fact alerts.
4. DNC scrub automation — national + state + internal — without manual intervention.
5. Cell phone identification at dial-time so manual mode kicks in for cell phones without pre-recorded messages.
6. Time-of-day enforcement per-recipient time zone, not per-server time zone.
7. Caller ID validation — TRACED Act compliance.
8. Recording retention matching state plus FCC requirements (typically 5 years for TCPA litigation defense).

For most outbound CCaaS deployments, this checklist is fully ticked by Five9, NICE CXone, Genesys Cloud CX, Talkdesk, Vonage Contact Center, Avaya Infinity and Webex Contact Center. Build-your-own approaches on Amazon Connect or Twilio Flex are possible but expensive.

Pricing impact

TCPA tooling is bundled in the outbound license tier on most vendors. Five9 includes predictive, progressive and preview dialers across Core, Premium, Optimum and Ultimate tiers. NICE CXone bundles outbound in Studio and Personal Connection modules. Genesys ships outbound in CX 2 and CX 3 tiers.

Amazon Connect's per-minute pricing covers the underlying telephony; the TCPA tooling — consent capture flows, 3% cap logic, DNC scrubbing — is the buyer's responsibility to build via Lambda functions and integrations.

Use the TCO calculator to estimate total outbound CCaaS cost at your seat count and call volume. Filter the vendor directory by company size to see only enterprise-grade TCPA tooling.

Bottom line

The January 27, 2025 one-to-one consent rule changed the bar for outbound CCaaS in 2026. Generic consent forms no longer satisfy TCPA; per-seller capture is now required, and the vendor must surface that consent at dial time. The 3% abandonment cap remains in force. The CCaaS vendors with the deepest TCPA tooling for outbound-heavy use cases are Five9 (outbound DNA from 2001), NICE CXone, Genesys Cloud CX and Avaya Infinity. Talkdesk, Vonage Contact Center and Webex Contact Center ship adequate tooling. Amazon Connect and Twilio Flex are configurable but require build-your-own. Aircall and Dialpad are inbound/service-focused and not the right fit for TCPA-heavy outbound.

For the regulatory background on the 3% abandonment cap, outbound call center pillar and predictive dialer guide go deeper.