AI-powered skip tracing now delivers 3-5x higher right-party contact rates than manual lookups. The industry-standard right-party contact rate sits around 25% — top performers using multi-source skip tracing hit 76%. But every one of those contacts must comply with Regulation F's 7-in-7 call cap, the FDCPA's time-of-day restrictions, the TCPA's consent revocation rules (full enforcement April 2026), and a patchwork of state collection laws that change faster than most compliance departments can track. Here's the 2026 VICIdial configuration for collections agencies that want high contact rates without high risk.
Collections is the most heavily regulated outbound calling vertical in the United States. The FDCPA has been on the books since 1977, but Regulation F — which codified specific, measurable rules for call frequency, electronic communication, and disclosure requirements — changed the compliance landscape permanently when it took effect in November 2021. Four years later, the enforcement environment continues to tighten.
This post is the 2026 update to our debt collection compliance guide, focused specifically on third-party collections agencies, skip tracing integration, and the regulatory changes that hit in 2025-2026. If you're a first-party collector (collecting your own debts), some of the FDCPA rules don't apply to you — but most of this configuration still applies because TCPA, state laws, and the CFPB's enforcement posture apply to everyone.
What Changed in 2025-2026
TCPA Consent Revocation — Full Enforcement April 2026
The FCC's consent revocation rule takes effect April 11, 2026. Under this rule:
- A consumer can revoke consent to receive automated calls/texts by "any reasonable means" — including saying "stop calling me" during a call
- Revocation must be processed within a "reasonable time" — interpreted as 24-48 hours
- The "revocation-all" component (where revoking one type of automated contact blocks all automated contact) has been delayed until January 31, 2027
For collections agencies, this is a significant operational challenge. A debtor who says "stop calling me" during a collection call triggers a consent revocation that must be processed system-wide within 48 hours. If you have multiple phone numbers for that debtor across multiple accounts, ALL automated dialing to ALL numbers must stop.
VICIdial implementation:
Custom Fields:
CONSENT_REVOKED: ENUM (NO, YES)
REVOCATION_DATE: DATETIME
REVOCATION_METHOD: VARCHAR (verbal, text, email, mail)
REVOCATION_AGENT: VARCHAR (agent who received revocation)
CEASE_DESIST: ENUM (NO, VERBAL, WRITTEN)
CD_DATE: DATETIME
Campaign Filter:
Exclude all records where CONSENT_REVOKED = YES OR CEASE_DESIST != NO
Filter updates: Every hour (not just daily — 48-hour processing window)
State Collection Law Updates
Several states enacted or updated collection-specific regulations in 2025-2026:
| State | Change | Impact |
|---|---|---|
| New York | Updated frequency caps | Stricter than Reg F in some circumstances |
| California | CCPA/CPRA data handling | Debt info may be "personal information" under CCPA |
| Massachusetts | Updated collection call restrictions | Narrower calling windows |
| Illinois | Biometric data in skip tracing | BIPA applies to voice recordings |
| Colorado | State-level frequency caps | More restrictive than federal |
Build state-level campaign filters in VICIdial to handle these variations.
CFPB Enforcement Posture
The CFPB's enforcement of Regulation F has produced several consent orders against collection agencies for:
- Exceeding the 7-in-7 call frequency cap
- Failing to properly identify the caller and the debt
- Third-party disclosure (revealing the debt to someone other than the debtor)
- Failing to send required validation notices within 5 days of initial contact
These aren't theoretical risks — they're active enforcement patterns.
Regulation F Compliance in VICIdial
The 7-in-7 Call Frequency Cap
Regulation F creates a presumption of FDCPA harassment if a collector:
- Makes more than 7 telephone calls within 7 consecutive days regarding a particular debt
- Makes a call within 7 days after a telephone conversation with the consumer about the debt
Critical distinctions:
- The cap is per debt, not per consumer. If a debtor has 3 debts with your agency, you can make 7 calls per week on EACH debt (21 total). But this is the legal maximum — not a recommended practice.
- The 7-day window is rolling, not calendar-week based.
- The cap counts call attempts, not connections. Unanswered calls count.
- The conversation lockout is 7 days from the last conversation, not the last attempt.
VICIdial Configuration for 7-in-7 Tracking
VICIdial doesn't have built-in per-debt frequency capping, so you need to build it with custom fields and external logic:
Custom Fields (per lead record):
DEBT_ID: VARCHAR (unique identifier for the specific debt)
ATTEMPTS_7DAY: INT (rolling count of call attempts in last 7 days)
LAST_CONVERSATION: DATETIME (timestamp of last live conversation)
NEXT_ELIGIBLE_DATE: DATE (earliest date the next call can be made)
External Logic (cron job running every hour):
1. Count call attempts per DEBT_ID in the vicidial_log table
for the last 7 days
2. If count >= 7, update NEXT_ELIGIBLE_DATE to [today + days remaining]
3. If LAST_CONVERSATION is within 7 days, update NEXT_ELIGIBLE_DATE
4. Campaign hopper filter: exclude leads where NEXT_ELIGIBLE_DATE > today
Implementation script (pseudo-logic):
# Run every hour via cron
# For each active debt in the campaign:
# Count calls in last 7 days from vicidial_log
# If count >= 7: set lead status to FREQ_HOLD
# If last conversation < 7 days ago: set lead status to CONV_HOLD
# If neither: set lead status back to active
Call Time Restrictions
The FDCPA prohibits collection calls before 8:00 AM and after 9:00 PM in the debtor's local time. This matches the TSR, but for collections there's no flexibility.
Campaign Settings:
Local Call Time: 8am-9pm
Timezone Method: POSTAL (use debtor's address for timezone)
Fallback Timezone: PHONE (area code — if no address data)
Convenience exception: A collector can call outside 8-9 hours if the consumer has specifically consented to being contacted at that time. Track this with a custom field:
CONVENIENCE_TIME: VARCHAR (e.g., "weekdays 7am OK" or "Saturdays 10am-2pm")
Skip Tracing Integration
Why Skip Tracing Matters for Collections
The industry-standard right-party contact (RPC) rate for collections is approximately 25%. That means 75% of your call attempts never reach the person who owes the debt. Skip tracing — the process of finding current contact information for consumers — directly attacks this problem.
Modern skip tracing vendors report RPC rate improvements of 35% or higher when agencies use multi-source skip tracing. Some platforms, like BatchSkipTracing, report 76% RPC rates — nearly 3x the industry standard.
Skip Tracing Vendors and Integration
| Vendor | Strength | Integration | Cost Model |
|---|---|---|---|
| TLOxp (TransUnion) | Full consumer data coverage | Batch API | Per-lookup |
| LexisNexis Accurint | Deep public records | API + batch | Per-lookup |
| Tracers | Cost-effective, API-first | REST API | Per-lookup |
| IDI (Idicore) | Real-time data refresh | API | Per-lookup + subscription |
| Experian Skip Tracing | Credit data linkage | Batch | Per-lookup |
| BatchSkipTracing | High RPC rate, bulk processing | API | Per-batch |
VICIdial Skip Trace Workflow
Step 1: New account loaded into VICIdial
→ Initial phone number from creditor file
Step 2: First pass dialing (creditor-provided number)
→ If RPC: proceed with collection
→ If wrong number / disconnected / no answer after 3 attempts:
flag for skip trace
Step 3: Skip trace batch
→ Send flagged records to skip trace vendor via API
→ Receive appended phone numbers, addresses, email
→ Load new phone numbers as alternate contacts in VICIdial
Step 4: Second pass dialing (skip-traced numbers)
→ Dial new numbers with fresh attempt count
→ Higher RPC rate expected on skip-traced numbers
Step 5: Ongoing skip trace refresh
→ Re-skip accounts every 30-60 days if still unresolved
→ Consumer data changes frequently — refreshing improves RPC over time
Loading Skip Trace Results into VICIdial
When skip trace results return multiple phone numbers per debtor:
API Call: /vicidial/non_agent_api.php
Function: update_lead
Parameters:
lead_id: [existing lead]
phone_number: [best phone from skip trace]
alt_phone: [second phone]
address3: [third phone] (VICIdial workaround for additional phones)
custom_7: SKIP_TRACE_DATE = [today]
custom_8: SKIP_TRACE_SOURCE = [vendor name]
custom_9: SKIP_TRACE_CONFIDENCE = [confidence score]
FDCPA compliance for skip-traced numbers:
When calling a skip-traced number, the agent must first verify they're speaking with the correct person BEFORE disclosing the debt:
"Hello, may I speak with [debtor_first_name] [debtor_last_name]?"
IF CORRECT PERSON:
→ Proceed with Mini-Miranda and collection conversation
IF NOT CORRECT PERSON:
→ "I apologize, I may have the wrong number. Thank you."
→ Disposition as WRONG_NUMBER
→ DO NOT mention the debt, the agency, or any account details
This is critical — disclosing the existence of a debt to a third party is an FDCPA violation. On a skip-traced number where you're not certain who will answer, identity verification comes FIRST.
Right-Party Contact and Mini-Miranda
Mini-Miranda Delivery
The FDCPA requires that in the initial communication with the consumer, and in all subsequent communications, the collector must disclose:
- That the communication is from a debt collector
- That the purpose is to collect a debt
- That any information obtained will be used for that purpose
Agent script with Mini-Miranda:
IDENTITY VERIFICATION:
"Hello, may I speak with [debtor_name]?"
IF CONFIRMED:
"[debtor_name], this is [agent_name] with [Agency Name]. I'm calling
regarding an account with [Creditor Name]. This is an attempt to
collect a debt, and any information obtained will be used for that
purpose. This call may be recorded."
"The balance on this account is [amount]. Are you in a position to
resolve this today?"
VICIdial Script Enforcement
Script: COLLECTION_CALL
Required Checkboxes (must be checked before any disposition):
[ ] Verified identity of debtor before disclosing any information
[ ] Delivered Mini-Miranda disclosure
[ ] Stated recording notification (if applicable)
[ ] Did NOT disclose debt to any third party
Script blocks disposition until all checkboxes are checked.
Third-Party Disclosure Prevention
Build safeguards into the VICIdial workflow:
- Voicemail messages: Never leave a voicemail that mentions the debt, the creditor, or that the call is from a debt collector. Compliant VM:
"This is [agent_name] with [Agency Name] calling for [debtor_name].
Please call us back at [number] regarding an important business matter."
Answering machine detection: When AMD detects a machine, the voicemail drop must be compliant. Review your voicemail audio file carefully — it must not contain debt-related language.
-
Third-party contacts: If someone other than the debtor answers (roommate, spouse, child), the agent can ONLY:
- Ask to speak with the debtor
- Leave a message asking the debtor to call back
- NOT reveal the debt, the creditor, or the purpose of the call
Multi-Client Portfolio Management
Client Isolation for Collection Agencies
Most third-party collection agencies handle accounts from multiple creditor clients. Each client's accounts must be isolated:
Campaign Architecture:
Campaign: CLIENT_BANK_A
List IDs: 300001-300999
DNC List: BANK_A_DNC
Caller ID: [Bank A's preferred caller ID or agency generic]
Script: BANK_A_COLLECTION
Custom Dispositions: [Bank A's required disposition set]
Campaign: CLIENT_BANK_B
List IDs: 400001-400999
DNC List: BANK_B_DNC
Caller ID: [Bank B's preferred caller ID]
Script: BANK_B_COLLECTION
Custom Dispositions: [Bank B's required disposition set]
Campaign: CLIENT_MEDICAL
List IDs: 500001-500999
DNC List: MEDICAL_DNC
Caller ID: [Agency caller ID — not medical provider]
Script: MEDICAL_COLLECTION (HIPAA-aware)
Additional Compliance: HIPAA Business Associate Agreement
Creditor-Specific Requirements
Each creditor may have requirements beyond FDCPA/Reg F:
| Requirement | Bank A | Bank B | Medical |
|---|---|---|---|
| Max call attempts/day | 3 | 2 | 1 |
| Max call attempts/week | 7 (Reg F) | 5 (stricter) | 3 (stricter) |
| Calling hours | 8-9 consumer | 9-8 (stricter) | 9-7 (stricter) |
| Settlement authority | Up to 60% | Up to 50% | Up to 40% |
| Payment plan minimum | $50/month | $25/month | $25/month |
| Recording disclosure | Required in all states | Two-party states only | Required in all states |
| Reporting frequency | Weekly | Daily | Weekly |
Build each creditor's specific requirements into their campaign configuration.
Collection Workflow in VICIdial
Disposition Codes for Collections
RPC — Right-party contact (spoke with debtor)
PTP — Promise to pay (amount and date recorded)
PTPFULL — Promise to pay in full
PTPPART — Promise to pay partial / payment plan
PAID — Payment received during call
SETTLED — Settlement agreed upon
DISPUTE — Debtor disputes the debt (trigger validation notice)
CEASE — Cease and desist requested (add to DNC immediately)
HARDSHIP — Financial hardship (reduced payment plan)
SKIP — Number is wrong / debtor not at this number
DISC — Number disconnected
EMPLOYER — Called debtor's workplace (document carefully)
REF — Refused to discuss
ATTY — Debtor represented by attorney (cease contact, contact attorney only)
BKRPT — Debtor filed bankruptcy (cease all collection activity)
DECEASED — Debtor is deceased (handle per state probate rules)
NA — No Answer
AM — Answering Machine (compliant VM left)
BZ — Busy
Payment Processing
When a debtor agrees to pay during the call:
Payment Workflow:
1. Agent confirms amount and payment method
2. Agent presses hotkey to pause recording (PCI compliance)
3. Agent enters payment in separate secure payment portal
4. Payment portal returns confirmation number
5. Agent resumes recording
6. Agent reads confirmation number and payment summary
7. Agent dispositions as PAID or PTP with payment date
Promise-to-Pay Follow-Up
Campaign: PTP_FOLLOWUP
Dial Method: RATIO at 1.0
Trigger: Day before promised payment date
Local Call Time: 9am-7pm
Agent Script: PTP_REMINDER
Max Attempts: 2
Script:
"Hi [debtor_name], this is [agent] from [Agency Name] regarding your
account with [Creditor]. I'm calling as a courtesy reminder about
your payment arrangement of [amount] due [date]. Will you be able
to make that payment as discussed?"
IF YES: "Thank you. We'll confirm receipt once it's processed."
IF NO: "I understand. Can we discuss a modified arrangement?"
Performance Metrics for Collections
Key Metrics
| Metric | Industry Average | Top Performer | Notes |
|---|---|---|---|
| Right-Party Contact Rate | 25% | 50-76% | Skip tracing quality is the primary driver |
| Promise-to-Pay Rate | 15-20% of RPC | 25-35% of RPC | Agent skill and scripting matter |
| PTP Kept Rate | 60-70% | 75-85% | Follow-up campaign improves this |
| Dollars Collected/Agent Hour | $50-$150 | $200-$400 | Varies by portfolio type and balance size |
| Cost Per Dollar Collected | $0.08-$0.15 | $0.05-$0.08 | Technology + agent efficiency |
| Compliance Violations | Industry problem | Zero target | One violation can cost millions |
VICIdial Reports for Collections
1. Right-Party Contact Rate by List/Portfolio
Track RPC rate segmented by creditor client, list age, and skip trace status. Identify which portfolios need skip trace refreshes.
2. Promise-to-Pay and Fulfillment Report
Track PTP volume, PTP amounts, and fulfillment rates by agent and portfolio. Agents with high PTP but low fulfillment rates may be making unrealistic arrangements.
3. Frequency Cap Compliance Report
Daily report showing any accounts approaching the 7-in-7 limit. Flag accounts at 5 or 6 attempts for supervisor review before the 7th call.
4. Cease-and-Desist / Revocation Report
Track all consent revocations and cease-and-desist requests. Verify they were processed within 48 hours. This is your audit trail for TCPA compliance.
5. Dollars Collected Dashboard
Real-time and daily tracking of collections by agent, team, campaign, and creditor client. This is the metric that drives agency profitability.
Call Recording and Retention
Recording Requirements
Collections calls must be recorded for compliance documentation:
Campaign Settings:
Campaign Recording: ALLFORCE
Recording Format: WAV (highest quality for regulatory review)
Recording Storage: /encrypted/recordings/collections/[client]/
Encryption: AES-256 at rest
Retention: Minimum 3 years from last collection activity per account
(per Reg F record retention requirements)
Backup: Offsite backup with same retention and encryption
State Recording Consent
Remember that recording consent requirements vary by state. In two-party consent states, the agent must disclose recording at the beginning of every call:
Recording Disclosure (played automatically or read by agent):
"This call may be monitored or recorded for quality assurance
and compliance purposes."
Two-Party Consent States (2026):
CA, CT, DE, FL, IL, MD, MA, MI, MT, NH, NV, PA, WA
(verify current list — some states have updated requirements)
Infrastructure for Collections Agencies
Server Sizing
Collections operations have unique infrastructure patterns:
- High call volume per agent (aggressive recycling)
- Large recording storage (all calls recorded, 3+ year retention)
- Complex reporting queries (per-debt frequency tracking)
Recommended architecture for 50-100 seat collections agency:
Server 1: VICIdial Web + Admin
Server 2: Asterisk Telephony (handles 200+ concurrent channels)
Server 3: MySQL Database (SSD storage for fast frequency queries)
Server 4: Recording Storage (NAS with 10+ TB for 3-year retention)
Optional: Read replica for reporting queries (prevents report load
from affecting production dialing)
Trunk Configuration
Collections agencies should use SIP trunks with:
- STIR/SHAKEN attestation (Level A)
- CNAM registration with agency name or neutral business name
- Multiple DID pools (rotate to prevent flagging)
- At least 2 SIP providers (redundancy for production operations)
If you're running a collections agency on VICIdial and need help with Regulation F compliance, skip tracing integration, frequency cap tracking, or multi-client architecture — ViciStack builds and manages production VICIdial deployments for ARM operations. We'll increase your right-party contact rate and dollars collected per agent hour within two weeks. $5,000 flat — $1,000 down, $4,000 on results.
Top comments (0)