What is a right party contact rate?
A right party contact (RPC) is a live conversation with the person who owes the account, as opposed to a voicemail, a no-answer, a relative, or a stranger who now has the number. RPC rate is the share of your attempts that end in one. It is the closest thing collections operations have to a single health metric, because nothing downstream (a promise to pay, a payment plan, a dispute resolved) happens without it. The usual reaction to a falling rate is to dial more. That is the wrong lever, and under Regulation F it has a hard ceiling.
Key takeaways
- Pick one denominator for RPC rate (attempts, connects, or accounts) and never mix them in one report.
- Unanswered calls that connect count toward Regulation F's 7-in-7 call frequency presumption, so dials on bad numbers spend a limited budget.
- Stale phones and addresses cause most wrong-number conversations. Fix the data before tuning the dialer.
- Accept strong matches automatically, review weak ones, and record which evidence supported each number.
How to calculate right party contact rate
The formula is simple, but teams quietly disagree on the denominator, which makes benchmarks between shops close to meaningless. Choose one and label it.
| Version | Formula | What it tells you |
|---|---|---|
| Per attempt | RPCs ÷ dial attempts | Overall efficiency, including bad numbers and no-answers |
| Per connect | RPCs ÷ calls answered by a human | How often the person who picks up is the right one: a direct read on number accuracy |
| Per account | Accounts with 1+ RPC ÷ accounts worked | Coverage: how much of the portfolio you actually reached |
A hypothetical worked example: a team places 10,000 attempts in a week. 1,500 are answered by a person, and 600 of those are the right party. Per-attempt RPC rate is 6%. Per-connect rate is 40%, which means 900 conversations, 60% of all connects, were with someone else. That 60% is the number to attack. It is made of relatives, roommates, and strangers on reassigned numbers, and every one of those conversations carries disclosure risk.
Why more dials will not fix it
Regulation F presumes a debt collector complies with the harassment rule if it places no more than 7 calls to a person about a particular debt within 7 consecutive days, and does not call within 7 days after a phone conversation about that debt. Going over either line is presumed a violation.
The detail that matters for RPC: an unanswered call that connects to the dialed number counts toward the 7. Only calls that never connect, such as a number that is not in service, are excluded. So seven rings on a number that now belongs to someone else, or that your debtor no longer answers, can use a full week's budget for that debt and produce zero RPCs. More dials on stale data mostly buy you exposure.
Wrong party conversations carry their own rule. When a collector talks to a third party to find the consumer, Regulation F limits what it can say (it cannot state that the consumer owes a debt) and generally allows that contact only once. A team that keeps reaching the same aunt on the same old number is running into that limit, whatever the dialer report calls it. General information, not legal advice; confirm the rules that apply to your shop with counsel.
The data problems behind wrong party contacts
Most lost RPCs trace back to four contact data quality problems:
- Phone aging. Numbers get disconnected and reassigned to new subscribers. A number last confirmed 18 months ago is a guess. The post on checking whether a phone number was reassigned covers the FCC database step.
- Address drift. People move, and a stale address sends letters and field visits to the wrong door. See how to check if an address is current for the signals that help, such as a property sale since the address was last seen.
- Weak matches. A record that matched on a common name plus a state is not the same evidence as one that matched on name plus date of birth. Treating them alike pushes wrong numbers into the dial queue.
- No source dates. A phone with no last-seen date cannot be aged, so it never leaves the rotation.
Locating people and refreshing their contact details is the core of skip tracing; the skip tracing guide covers the wider workflow.
A data-first playbook for a higher RPC rate
Run this before you touch pacing or calling hours:
- Rank numbers by evidence, not position. Put the most recently seen number with the strongest match first. Drop numbers with no date to the bottom.
- Auto-accept strong matches, review weak ones. Set a confidence threshold. Above it, the number goes to the queue; below it, a person looks before anyone dials. CoverFi returns a 0-100 match-confidence score and labels which match tier produced each result (exact, nickname, former name, relaxed date of birth), so a reviewer can see why a number was suggested.
- Retire numbers that keep failing. After a set number of connected-but-wrong outcomes, mark the number wrong for that consumer and stop dialing it, rather than letting it burn the weekly 7.
- Check reassignment before campaigns. Query the Reassigned Numbers Database with your consent or last-contact date, and suppress numbers that come back "yes".
- Track RPC per connect by data source. If one source's numbers convert at half the rate of another's, that is a data decision, not a dialer one.
Use contact data only to reach the right person. It is not an input to decisions about credit, employment, insurance, or housing.
Frequently asked questions
What is the difference between a right party contact and a wrong party contact?
A right party contact is a conversation with the person responsible for the account. A wrong party contact is a conversation with anyone else who answers, such as a family member or the new holder of a reassigned number.
Do voicemails count as right party contacts?
No. A voicemail is not a conversation with the account holder. Under Regulation F, an unanswered call that connects still counts toward the 7-in-7 call frequency, even when it ends in a voicemail.
What is a good right party contact rate?
It depends on your denominator, portfolio age, and debt type, so compare against your own history instead of outside benchmarks. Track it per connect and per data source to see where the losses come from.