Who this is for
This playbook is for early-stage and mid-stage collection agencies, debt buyers, and BNPL recovery teams that have already proven a recovery model in-house and now need to scale dialing capacity without doubling their compliance footprint. If you have at least one licensed collector on staff, recordings on every call, and a documented FDCPA training program, this is the operational layer you can offload to a nearshore vendor.
It is not for buyers shopping for "the cheapest dialer in the Caribbean." If your operating premise is that you can lower cost by lowering compliance, this is not the playbook · and we are not the vendor.
A note on what we do
CFG agents are nearshore fronters and dialers, not licensed debt collectors in any US state or jurisdiction. We support FDCPA-aligned operations · scripts, recording, dispositioning, RPC capture · under your licensed agency's name and oversight. Licensed collection activity (payment negotiation in regulated states, validation responses, legal escalation) stays with your licensed staff.
Why the cost equation has shifted
Three things have moved in the last 18 months that change the buy-versus-outsource math for collections:
AI dialers raised the floor
Predictive and AI-augmented dialers have collapsed the gap between a mediocre dialing operation and a strong one. Drop rates, abandonment, and pacing are largely solved problems if you pay for a major dialer platform. The differentiator is no longer dialing technology · it is agent quality on the contact and disposition discipline after.
FDCPA enforcement is denser
State AG actions, CFPB consent orders, and private FDCPA suits have made the cost of a noncompliant call higher than the marginal revenue from one more contact. The economic logic now favors fewer, cleaner contacts over high-volume, low-quality dialing.
Consumer recording-disclosure expectations
Two-party-consent state expansion and the post-Reg F environment mean recordings, disclosures, and audit trails are no longer a nice-to-have. They are the audit defense. A vendor that cannot produce a clean recording within hours of a complaint is a liability, not a cost-saving.
Nearshore vs. far-offshore · the compliance footprint difference
"Offshore" is not a single thing. The operational and compliance differences between nearshore (Caribbean and Latin America) and far-offshore (South Asia, Southeast Asia, Eastern Europe) matter for collections specifically:
| Dimension | Nearshore (Caribbean/LatAm) | Far-offshore |
|---|---|---|
| Time-zone overlap with US business hours | Full overlap (EST to PST) | Inverted or partial |
| Agent native English | Common (Jamaica, Trinidad, Bahamas) | Variable, often accented |
| Right-party-contact (RPC) consumer experience | Indistinguishable from US-based agent on most calls | Often flagged by consumer as offshore |
| US dialer integration and IP whitelist hygiene | Routine | Routine but more network hops |
| Recording chain-of-custody to US S3 | Same-region transit | Trans-oceanic, more failure modes |
| Live escalation to US-based supervisor | Real-time, same shift | Off-hours handoff |
| Hourly cost band (2026) | Mid-tier offshore | Lowest-tier offshore |
If your collection book is heavy on consumer accounts where complaint risk is real, the nearshore premium over far-offshore typically pays for itself in fewer escalations and faster RPC resolution. If you are dialing strictly commercial accounts where the contact is a CFO at a known business, the calculus shifts.
Recording retention + audit trail expectations
Every collection call your vendor makes should produce an artifact you can retrieve, replay, and hand to a state AG or your client within hours. The minimum bar:
- Retention period. Industry standard is 7 years minimum for collection call recordings. Some clients require longer based on the underlying contract or state law. Confirm in writing before launch.
- Dual-channel recording. Agent and consumer audio on separate channels so QA, transcription, and dispute review can isolate who said what. Single-channel recordings are a debt-buyer red flag.
- Chain of custody from agent desktop to S3. The recording leaves the agent's softphone, transits the dialer, and lands in your S3 (or vendor S3 with your access). Document each hop. If the vendor cannot draw the diagram, they do not have a chain of custody.
- Tamper-evident storage. Recordings should be write-once and hash-verified. If a recording can be edited or replaced, it is not evidence.
- Retrieval SLA. 4 hours is aggressive but defensible. 24 hours is the upper end of acceptable. Anything longer means audit response is broken.
- Searchable metadata. Every recording must be retrievable by account number, phone dialed, agent ID, disposition, and date. If retrieval requires "email me the date and we will look," you cannot defend a complaint.
The 6 vendor red flags
Use these as disqualifiers during evaluation. Each one is a sign the vendor is selling cost without compliance.
Red flag 1 · Cannot share a recording sample
Every legitimate collection BPO has redacted sample recordings ready to share. If they need a week to find one, they either do not record or do not retain. Walk.
Red flag 2 · Cannot share their script
The script is the compliance artifact. If the vendor will not show you the actual scripts their agents use, you cannot brief your compliance officer · and you certainly cannot defend the calls in an audit.
Red flag 3 · No documented FDCPA training proof
Ask for the training curriculum, attestation records, and renewal cadence. "We train our agents on FDCPA" is not training. A documented program with named trainers, content, and per-agent attestation is.
Red flag 4 · Payment instructions to a non-licensed entity
If a vendor proposes that consumer payments route through their entity rather than your licensed agency, that is licensed collection activity. They are either licensed (verify in every state of operation) or they are exposing you to a per-violation FDCPA suit.
Red flag 5 · No escalation matrix
What happens when a consumer asserts a dispute, asks for cease-and-desist, claims attorney representation, or threatens suit? The vendor should have a documented escalation tree with US-based response within minutes, not a vague "we will let you know."
Red flag 6 · Vague SLAs
SLAs that read "industry standard" or "best effort" are not SLAs. The next section walks through what real collection SLAs look like.
Sample SLAs to ask for
These are the contract-level metrics that separate a managed collections operation from a body shop. Ask for committed numbers, monthly reporting, and remediation triggers when missed.
Right-Party Contact (RPC) rate
Of contacts where a person answers, what percent are confirmed right-party-contact (the actual debtor)? Industry averages vary widely by portfolio age, debt type, and skip-trace data quality. Pin a baseline in the first 30 days, then commit to a minimum from month 2 forward. RPC below baseline two months running should trigger a vendor performance review.
Abandonment rate (ABR)
The percent of dialed contacts where the consumer connects but no agent is available. FCC and FDCPA-conscious operations typically operate well below 3 percent. Above 3 percent puts you at TCPA risk on predictive dialing patterns. Ask the vendor to commit to a hard ceiling.
Compliance Recording Capture (CRC) rate
The percent of calls fully recorded with searchable metadata. The only acceptable answer is 100 percent (with documented exception handling for system failures). Anything less is an audit gap.
Dispute response time
When a consumer asserts a dispute on a call, how fast does the vendor route it to your licensed staff for validation response? Inside a single business day is the standard. Inside 4 hours is best-in-class. The vendor should track and report this monthly.
Recording retrieval SLA
Time from your audit request to the recording landing in your inbox or audit portal. 4 hours is aggressive, 24 hours is the upper end of acceptable. Tie this to the contract with a remediation clause if missed twice in a quarter.
Agent attendance and adherence
Often overlooked in collections SLAs. Adherence below 90 percent quietly destroys dialer pacing and pushes ABR up. Ask for monthly per-agent and per-team adherence reporting, not aggregate.
A practical SLA template
Most healthy vendor contracts include: RPC floor, ABR ceiling, CRC at 100%, Dispute response under 24 hours, Recording retrieval under 24 hours, and Adherence above 90%. Each should have a measurement methodology, monthly reporting cadence, and a documented remediation step when missed two months running.
The bottom line
Outsourcing collections dialing is a real cost-reduction lever · the labor cost differential between nearshore and US-based dialers typically runs 40 to 60 percent. But the savings only stick if the compliance footprint stays clean. The vendors that destroy program economics are the ones that look cheap on the rate card and expensive in the consent decree.
The buyers who get this right do three things: they vet vendors on recording posture and FDCPA training before they vet on price, they keep payment-handling and licensed activity in-house, and they treat SLAs as live operational instruments instead of contract decoration.