Best Dialer for Collections 2026: FDCPA + TCPA + Reg F

The four-rule overlap

Collections dialers in 2026 operate inside a four-rule compliance perimeter:

Rule 1: FDCPA's call-cap (15 USC § 1692c)

The Fair Debt Collection Practices Act, as amended by Regulation F (CFPB rule effective November 30, 2021), caps debt collector contact attempts at 7 telephone calls per consumer per debt within a 7-day period, with a 7-day quiet window after talking to the consumer.

This is the "7/7/7 rule." Violation creates a private right of action: $1,000 statutory damages plus actual damages plus attorney's fees.

Rule 2: TCPA's one-to-one consent (effective Jan 27, 2025)

The FCC's one-to-one consent rule requires per-seller consent capture. Lead-aggregated consent no longer satisfies prior express written consent. Collections agencies dialing consumer cell phones using auto-dialers need verifiable consent per debt per consumer.

The TCPA pillar covers this in depth.

Rule 3: FCC 3% abandonment cap

Predictive dialers must hold abandonment rate at or below 3% of connected calls in any 30-day rolling window per campaign. Statutory damages $500-$1,500 per abandoned call.

Rule 4: State-by-state collections rules

States overlay collections-specific rules on top of federal:

• California Rosenthal Fair Debt Collection Practices Act — broader than FDCPA, covers first-party collections (creditors collecting their own debts)
• Massachusetts 940 CMR 7.04 — call frequency cap of 2 successful contacts per 7 days
• New York 23 NYCRR 1 — verification and recording disclosures
• Texas Finance Code Chapter 392 — collection harassment definitions
• Other states add caps, disclosures, language requirements

The CCaaS must support per-state call-cap and disclosure rules.

What a collections dialer must do natively

A collections-ready CCaaS dialer ships these capabilities natively, not through manual configuration:

1. FDCPA call-cap tracking per consumer per debt — real-time count of attempts in the rolling 7-day window
2. Reg F 7/7/7 enforcement — automatic suppression of further attempts when cap is reached
3. TCPA one-to-one consent verification — verifiable consent record per debt per consumer surfaced at dial time
4. Real-time 3% abandonment cap — auto-throttling pacing logic, per-campaign math
5. State law overlays — per-state call-cap rules layered on federal
6. Disclosure scripts — Mini-Miranda ("This is an attempt to collect a debt") and similar disclosures presented to agents
7. Quiet hours — federal 8am-9pm caller's local time + state variances
8. Cell-phone identification at dial time
9. DNC scrubbing — federal, state, internal — automated
10. Immutable audit log for CFPB/FTC investigation cooperation

A dialer that requires the buyer to build these features (Amazon Connect, Twilio Flex) is a build-your-own — not a wrong choice, but a different commitment.

Vendor matrix for collections

Why Five9 dominates the collections vertical

Five9's collections market share is driven by three structural advantages:

1. Outbound DNA from 2001. The codebase, the implementation methodology, the partner ecosystem, the support team — all built around outbound. NICE and Genesys closed most of the gap over 2018-2024 but Five9 still ships the deepest collections-specific feature set.
2. CFPB-aligned audit log. When the CFPB or FTC issues a Civil Investigative Demand, Five9's audit log structure matches what investigators ask for. Other vendors require translation work.
3. Per-state law library. Five9 ships an updated library of state collections rules; competitors require manual configuration.

This doesn't make Five9 the only choice. NICE CXone Proactive Engagement Suite and Genesys Cloud CX Outbound have closed the gap for greenfield collections deployments. Avaya has the largest legacy install base in collections from the Aura era. Salesforce shops use Vonage Contact Center or Service Cloud Voice with Reg F apps.

CFPB enforcement priorities (2024-2026)

The Consumer Financial Protection Bureau has prioritized:

• Call-cap violations under Reg F — multiple seven-figure settlements
• Verifiable consent capture under TCPA-Reg F overlap — record-keeping standards
• Mini-Miranda compliance — agent disclosure scripts must be auditable
• State-law preemption disputes — federal vs state rule conflicts

A CCaaS that can produce per-consumer, per-debt, per-attempt audit trails on demand is the minimum bar.

Build-your-own on Amazon Connect

For collections agencies with engineering resources and a desire for maximum control, Amazon Connect is a credible build-your-own platform. Required components:

• DynamoDB or RDS for consumer/debt master with attempt counters
• Lambda functions triggered on each dial to check FDCPA/Reg F caps
• Amazon Pinpoint for outbound SMS reminders (with TCPA-safe consent)
• Amazon Comprehend for call-record disclosure analysis
• CloudTrail + S3 for audit log
• Step Functions for multi-stage workflows (initial contact, validation notice, post-validation, dispute handling)

Total implementation: 6-12 months. Total cost: $0.018-0.038/min Connect + AWS services. Right answer for the largest collections agencies; wrong answer for mid-market.

State law deep-dive — California Rosenthal Act

California's Rosenthal Fair Debt Collection Practices Act is the most-extended state collections law. It covers:

• First-party creditors (not just third-party debt collectors as under federal FDCPA)
• Stricter call cap — Rosenthal Act adopts FDCPA's 7/7/7 plus additional limits
• Mandatory recording disclosure in single-party consent states
• Spanish-language requirement for borrowers who originated in Spanish
• Private right of action with attorney's fees

CCaaS deployments serving California require Rosenthal Act-compliant configuration. Five9, NICE CXone Proactive Engagement Suite and Genesys Cloud CX Outbound ship Rosenthal Act-tuned templates.

TCPA outbound to cell phones — the consent capture pattern

Most collections calls go to cell phones in 2026. The TCPA + Reg F overlap requires:

1. Per-debt consent capture at debt origination (creditor's job, but CCaaS must verify before dialing)
2. Cell phone identification at dial-time
3. Manual mode for cell phones when consent is uncertain
4. Recording of consent disclosure at call start
5. Audit trail linking each dial attempt to a specific consent record

Five9 ships this pattern natively. NICE CXone and Genesys Cloud CX with Outbound do as well. Other vendors require integration with consent-management platforms (e.g., InstantCheckmate, ContactConsent, ActiveProspect).

Pricing for collections

Collections CCaaS pricing in 2026:

• Five9 — Premium $199 / Optimum $219 / Ultimate $229 per concurrent user, 50-seat minimum
• NICE CXone with Proactive Engagement Suite — $150-260/seat/mo
• Genesys Cloud CX 2 or CX 3 — $130-180/seat/mo plus partner integration
• Avaya CC Elite (outbound) — gated pricing; collections shops typically pay $120-200/seat/mo
• Amazon Connect with build-your-own — $0.018-0.038/min plus AWS services plus 6-12 month implementation

Use the TCO calculator at your call volume to model collections-specific scenarios. Per-concurrent-user pricing (Five9) often beats per-named-user pricing for collections shops with high seat utilization.

Buyer playbook

1. Verify per-state law library. Don't accept "we can configure" — get the specific state rules the vendor ships.
2. Test CFPB audit log format. Ask vendor to produce a sample audit report for a fictitious CID.
3. Pilot on one debt portfolio (auto loan, credit card, student loan) before all-portfolio rollout.
4. Train agents on Mini-Miranda + state disclosures in scripted form within the agent desktop.
5. Build TCPA consent verification into onboarding — debt origination flow must capture verifiable per-debt consent.
6. Establish CFPB response runbook — when CID arrives, what's the 30-day response procedure?

For deeper context, see TCPA-compliant dialer, outbound call center pillar, predictive dialer guide and Five9 review.

Bottom line

For collections in 2026: Five9 is the most-deployed and the safest default for new collections CCaaS deployments. NICE CXone Proactive Engagement Suite and Genesys Cloud CX Outbound are credible alternatives. Avaya has the legacy install base. Salesforce + Vonage Contact Center fits Salesforce-anchored collections. Amazon Connect build-your-own works for the largest agencies with engineering resources. The four-rule perimeter (FDCPA call-cap, Reg F 7/7/7, TCPA one-to-one consent, FCC 3% abandonment) is non-negotiable; per-state overlays add Rosenthal Act (CA), Massachusetts 940 CMR, and similar.