A configuration playbook for collections leaders and dialer admins: which dialing mode fits which list, how Reg F and TCPA constraints become actual Five9 objects, and how to take payments without widening PCI scope. US rules first, UK section at the end.
How should Five9 be configured for debt collection?
Segment first: predictive for deep early-stage lists, power or progressive for thin skip-traced files, preview or TCPA Manual Touch Mode for high-balance accounts and cell numbers without consent. Enforce Reg F seven-in-seven with attempt counters and disposition-driven cooldowns, separate promise-to-pay, dispute, cease and wrong-number dispositions, and keep card data out of recordings with DTMF suppression or pay-by-link.
One pacing profile for every portfolio is the most common configuration mistake we see on collections floors.
Collections lists are not one thing. A day-one placement file of 40,000 fresh accounts behaves nothing like a skip-traced remnant of 900 hard-won numbers, and neither behaves like the 60 high-balance accounts your best negotiators are nursing toward settlement. The setups we audit usually run all three through one predictive campaign with one pacing profile, which wastes agent hours at one end and burns rare numbers at the other.
| Segment | Sensible starting mode | Why |
|---|---|---|
| Deep, fresh placement lists | Predictive, conservative pacing | Statistical pacing needs volume to work. Fresh files produce enough live answers to feed the math, and per-account value is low enough that throughput wins. |
| Thin or skip-traced lists | Power or progressive at 1:1 | Too few records for the predictive math to settle. Every number cost money to find, so an abandoned call on a skip-traced hit is paying twice to annoy someone. |
| High-balance accounts | Preview | The agent reads the history before dialing. One good conversation is worth more than an hour of extra dials, so pace is the wrong thing to optimize. |
| Cell numbers without consent on file (US) | TCPA Manual Touch Mode | Takes automated dialing out of the picture entirely. Covered in the next section. |
Two notes on the predictive row. First, collections tolerates far less abandonment than sales, because an abandoned call to a debtor is not a missed sale, it is a harassment complaint waiting for a form. Second, measure abandon rate properly: abandoned calls divided by calls answered by a live person. Dividing by dials makes the number look several times better than it is and tells you nothing about what actual humans experienced. We cover the mechanics in our piece on abandonment rules for predictive dialing.
Five9 gives you the four standard modes (predictive, power, progressive, preview) plus the TCPA-specific manual option, and campaigns can be split so each portfolio gets its own mode, pacing and attempt rules. The configuration is not hard. Deciding to use it per segment, rather than cloning last year's campaign, is apparently the hard part.
Removing autodialer character from cell dialing when there is no consent on file.
The Telephone Consumer Protection Act is why collections floors treat cell numbers differently. Calling a cell with an automatic telephone dialing system or an artificial or prerecorded voice, without prior express consent, exposes you to statutory damages of 500 dollars per call, up to treble that for willful violations, and collections portfolios generate calls by the hundred thousand. In 2021 the Supreme Court narrowed what counts as an ATDS in Facebook v. Duguid: equipment must store or produce numbers using a random or sequential number generator. A list-based dialer arguably falls outside that definition. Arguably is doing heavy lifting in that sentence. The plaintiffs' bar has spent the years since testing every edge of it, and prerecorded-voice liability never depended on the ATDS definition at all, so most collections operators still route non-consented cells away from anything automated.
Five9's answer is TCPA Manual Touch Mode. What Five9 documents publicly: contact lists flagged for TCPA handling are placed on a separate system that lacks ATDS functionality and, in Five9's words, 'requires human intervention for each call to be placed'. The agent launches every call, nothing dials on its own, and the compliance consultancy CompliancePoint has reviewed the design. Operationally it feels like preview dialing with the automation physically absent rather than switched off. That distinction is the whole point: post-Duguid arguments turn on what the equipment has the capacity to do, and a mode toggle on an autodialer leaves that question open in a way separate infrastructure is designed to close. We are describing the design goal, not offering a legal conclusion; whether a given configuration removes autodialer character on your facts is a question for your counsel, not your CCaaS vendor.
Two adjacent obligations belong in the same design conversation. Five9 ships do-not-call list management and time-zone dialing rules alongside the mode itself; use both. And the FCC's revocation rules that took effect in April 2025 require honoring an opt-out made by any reasonable means, including a standard keyword list for texts, within ten business days. The broader revoke-all provision, which would extend one revocation to unrelated future contact, has been pushed back to January 31, 2027 while the FCC rethinks it. Build the suppression plumbing now anyway. Retrofitting it later is worse.
Our free Five9 Health Check runs 17 questions across pacing, compliance controls, list hygiene and reporting, and tells you where the gaps are before an auditor or a regulator does.
Seven calls, seven days, one debt: the counters, cooldowns and suppression rules that enforce it.
The regulation itself is short enough to configure from. Under 12 CFR 1006.14(b), a debt collector is presumed compliant if it places calls to a particular person about a particular debt no more than seven times within seven consecutive days, and does not call within seven consecutive days after having a telephone conversation with that person about that debt. The conversation date counts as day one of the cooldown. Go past either line and the presumption flips against you. It is a presumption rather than a hard cap, but treating it as anything other than a hard cap in dialer configuration is a bet we have never seen a compliance officer take.
The unit of counting is the debt, not the consumer and not the phone number. That single fact drives most of the implementation:
The exclusions matter just as much. Calls that do not connect, such as busy signals and dead numbers, do not count toward the seven. Calls made with the consumer's prior consent, given directly to the collector and used within seven days, sit outside the count too, which is what makes a promised callback lawful on day three of a cooldown. Where ring-no-answer and voicemail land involves reading the CFPB commentary; our conservative default is to count anything that reached a network endpoint, because undercounting is the expensive direction to be wrong in. Several states layer tighter frequency caps of their own on top, so counter logic needs a per-state parameter, not a constant. The full build, including the Five9 objects involved, is in our Regulation F dialing configuration guide.
In Five9 terms this means disposition-driven redial timers handling the cooldowns, campaign-level attempt caps handling the seven, and a nightly list job reconciling both against the system of record, because dialer-side counters alone drift the moment an agent places a manual call from the CRM. Frequency rules also evolve; check the current text and involve qualified counsel where the exposure warrants it, rather than treating any summary, including this one, as the spec.
Every downstream compliance process keys off whatever the agent clicks in the three seconds after wrap. That is the whole case for designing dispositions before go-live rather than letting them accrete afterwards. Four outcomes carry legal weight and get their own codes, cleanly separated:
Creates a dated payment arrangement in the system of record and schedules the follow-up. It also counts as a conversation, so the follow-up scheduler has to respect the seven-day Reg F cooldown unless the consumer gave direct consent for a specific callback.
Flags validation obligations under the FDCPA and pauses collection activity on that debt where required. The dispute queue in your system of record should populate from this disposition automatically, same day, with the call recording attached.
Hard suppression matching the scope of the request: a channel, a number, or all contact. Reg F separately requires honoring a request to stop using a specific medium, so the suppression model needs per-channel granularity, not one kill switch.
Number-level suppression plus list hygiene. The number leaves every campaign for that consumer, feeds the do-not-dial pool, and never recycles back in from skip-tracing output without human review. This is also your cheapest TCPA risk reduction.
Design rules we hold to on every build: each disposition maps to exactly one machine action, agents get no ambiguous catch-alls (a callback code that sometimes means promise and sometimes means dispute is an audit finding in waiting), and every disposition carries a flag for two-way conversation about the debt, because that flag, not the disposition name, drives the Reg F cooldown. When a regulator asks for every dispute logged in March, the answer should be a filter on one field, not two weeks of transcript review.
Reg F is blunt about the disclosures. The initial communication must state that the debt collector is attempting to collect a debt and that any information obtained will be used for that purpose; every subsequent communication must state that it is from a debt collector; and an oral initial disclosure gets repeated in the first written one. Put both variants in the scripted opening block in Five9, not in agent memory, and make the CRM tell the agent which situation they are in, because 'is this an initial communication' is not a judgment call you want made live on a headset.
On recording, the rule that surprises people is retention: if you record calls, 12 CFR 1006.100 requires keeping each recording for three years after the date of the call, alongside the general obligation to keep compliance records until three years after your last collection activity on the debt. On a 200-seat floor that is a storage line item worth pricing before, not after, you switch to recording 100 percent of calls. Recording disclosure is the other scripting note: enough US states require all-party consent that most national floors announce recording on every call rather than maintain a state matrix with failure modes. QA then samples against three things: recording disclosure present, mini-Miranda present and correct for the communication type, and no card numbers spoken aloud. Which brings us to payments.
Three ways to keep card numbers out of your recordings, compared without vendor loyalty.
A card number read aloud on a recorded line puts your recording platform, its storage and everyone with playback access inside PCI DSS scope, and collections floors record everything. The PCI Security Standards Council's guidance on protecting telephone-based payment card data describes the standard ways out, and they are worth comparing honestly rather than picking whichever one a demo showed first.
| Approach | How it works | Effect on scope | Honest trade-offs |
|---|---|---|---|
| DTMF suppression or masking | The customer keys the card number on their phone keypad mid-call; tones are suppressed or replaced so neither the agent nor the recording receives usable digits. | Strong descoping of the agent and recording environment; the payment path itself still needs securing. | The agent stays on the line, which protects fragile arrangements. Poor implementations leak partial tones (DTMF bleed), so test rather than assume. |
| Pause-resume recording | Recording stops during card capture and restarts after, either manually or automatically. | Partial. The agent still hears the number, so agent-side controls stay in scope. | PCI SSC guidance notes that neither manual nor automated pause-resume is fully accurate, so it needs routine verification. Manual pause on a busy floor fails often enough to plan for. |
| Pay-by-link or secure IVR transfer | The agent sends a payment link or warm-transfers into a secure IVR; card entry happens entirely outside the agent environment. | Strongest descoping of the floor. | Some payers drop off between promise and payment, and in collections that gap is where arrangements die. Measure completion rates before standardizing on it. |
We deliberately make no vendor recommendation here. All three patterns work when implemented properly and verified regularly, and every one of them fails quietly when nobody owns the verification. Whichever you choose, write the fallback script for the moment the technology breaks mid-payment, because agents will otherwise improvise, and improvisation is how card numbers end up in recordings.
Everything above rations your attempts. Right-party contact decides what each rationed attempt is worth. Under a seven-call weekly budget per debt, dialing a dead number five times spends most of the week's budget reaching nobody, so number quality scoring and best-time-to-call windows stop being nice-to-haves and become the economics of the portfolio. The statutory presumption window of 8 a.m. to 9 p.m. at the consumer's location sets the outer bounds under FDCPA calling rules; inside it, attempt timing is where the gains live. Caller ID reputation deserves standing attention too, because collections numbers attract spam flags faster than almost any other traffic, and a flagged number turns permitted attempts into ignored ones. Across our outbound portfolio, sustained work on number health and attempt timing sits behind a 40 percent connect rate improvement, though that figure is an aggregate across client programs, not a promise about any one floor. The full playbook is in our right-party contact guide. One caution specific to collections: local presence rotation, common in sales, reads as evasive in a debt context and sits badly with the transparency regulators on both sides of the Atlantic keep signaling. Use a small, stable, well-maintained set of numbers that answer when called back.
For consumer credit collected in the UK, the FCA's consumer credit sourcebook and Ofcom's persistent misuse policy replace the federal machinery above, and they reward different instincts. CONC 7 is the operative FCA chapter. It requires firms not to contact customers at unreasonable times, and to pay due regard to reasonable requests about when, where and how they are contacted; the FCA's own example is a customer working shift patterns. CONC 7.3 requires treating customers in arrears difficulties with forbearance and due consideration, and proportionality runs through the whole chapter. None of that reads like dialer configuration until you try to comply at scale: per-customer contact windows have to live in the dialer, channel preferences have to suppress at campaign level rather than sit as CRM notes, and vulnerability flags need to pull accounts out of automated pacing into a trained queue. A policy the dialer cannot see is a policy the floor is not following.
Ofcom's persistent misuse policy governs the mechanics themselves: silent and abandoned calls. The revised statement in force since March 2017 removed any notion of a safe abandoned call rate. The old 3 percent figure is explicitly no longer a safe harbor, and silent calls, including those produced by answering machine detection false positives, are treated as unacceptable in any volume. Abandoned calls that do occur are expected to carry a short information message identifying the caller, and outbound calls must present a callable CLI. The practical consequence on the UK floors we run: collections campaigns default to progressive or power at 1:1 with AMD off or aggressively validated, and any abandoned call is handled as an incident with a cause, not a rate to stay under. Our Ofcom dialler rules guide covers the detail. Both regimes get revised and enforcement emphasis shifts between revisions, so verify against the current CONC text and the latest Ofcom statement, and take proper advice where a configuration decision carries real exposure.
Five9 offers TCPA Manual Touch Mode. Lists flagged for TCPA handling are held on a separate system that lacks autodialer functionality, and an agent must initiate every call individually. The design goal is removing autodialer character from cell phone dialing where no prior express consent exists, and Five9 has had the design reviewed by the compliance consultancy CompliancePoint. Whether it removes TCPA exposure on your specific facts is a question for your counsel.
Regulation F (12 CFR 1006.14) presumes a debt collector complies with the ban on harassing call patterns if it calls a person about a particular debt no more than seven times in seven consecutive days, and not within seven days after a telephone conversation about that debt. Exceeding either flips the presumption toward violation. The count is per debt, across all numbers attached to it, and some calls, such as those that never connect, are excluded.
Calls that do not connect, such as busy signals or dead numbers, do not count toward the seven-call presumption. Connected calls count whether or not anyone speaks. Treatment of ring-no-answer and voicemail edge cases sits in the CFPB commentary, so many operators count conservatively and treat anything that reached a network endpoint as an attempt. A completed two-way conversation additionally triggers the seven-day cooldown before the next call about that debt.
It depends on the list, not the floor. Deep fresh placement files suit predictive dialing with conservative pacing and tight abandon control. Thin or skip-traced lists suit power or progressive at 1:1, since predictive pacing needs volume and skip-traced numbers are expensive to waste. High-balance accounts suit preview mode, where the agent reads history first. Cell numbers without prior express consent belong in TCPA Manual Touch Mode. Most floors need several campaigns running different modes at once.
After Facebook v. Duguid (2021), equipment only meets the TCPA autodialer definition if it stores or produces numbers using a random or sequential number generator, which arguably excludes list-based predictive dialers. But prerecorded-voice liability is unaffected, litigation keeps probing the boundary, and statutory damages run 500 dollars per call. Most collections operators therefore still keep non-consented cell numbers out of automated modes. Take advice from qualified counsel before relying on Duguid alone.
If a debt collector records calls, Regulation F (12 CFR 1006.100) requires retaining each recording for three years after the date of the call. The same section requires keeping records evidencing FDCPA compliance from the start of collection activity until three years after the last collection activity on the debt. Electronic storage is acceptable if records can be accurately reproduced and accessed. Budget the storage before switching to recording every call.
Three patterns dominate, all described in PCI Security Standards Council guidance on telephone-based payments. DTMF suppression or masking lets the customer key their card number while the tones are blocked from agent and recording. Pause-resume stops the recording during card capture, though the agent still hears the number. Pay-by-link or secure IVR transfer moves card entry out of the agent environment entirely. Each descopes differently and each needs routine verification that it actually works.
Two regimes apply. The FCA's CONC 7 governs conduct: no contact at unreasonable times, due regard to customer preferences about when and how they are contacted, and forbearance toward customers in financial difficulty. Ofcom's persistent misuse policy governs dialer mechanics: since March 2017 no abandoned call rate is considered safe, and silent calls, including answering machine detection false positives, are not tolerated. UK collections floors therefore usually run progressive or 1:1 power dialing with AMD off.
Under Regulation F (12 CFR 1006.18(e)), a debt collector's initial communication with a consumer must state that the collector is attempting to collect a debt and that any information obtained will be used for that purpose. If the initial communication is oral, the disclosure must be repeated in the first written one. Every later communication must state that it is from a debt collector. On a dialing floor this belongs in the scripted opening, driven by CRM state.
We configure and operate Five9 collections operations daily: dialing strategy, Reg F counters, disposition architecture and payment capture. If part of this article read like your backlog, we can take it off your hands.
Talk to us