Reaching the Customer: Contact Data, Skip Tracing, and Why Most Collections Fail Before the Message

Collections advice concentrates almost entirely on what to say — the wording, the tone, the offer, the escalation. All of it is downstream of a variable that receives almost no attention and determines everything: whether the message reaches a person at all. An operation can have perfect scripts, well-designed payment plans, and disciplined timing, and recover nothing from an account whose phone number was disconnected eight months ago. Contact rate is the binding constraint in most recovery functions, it degrades continuously without anyone noticing, and improving it frequently produces larger gains than any change to the message. This guide covers data capture, decay, skip tracing, and the compliance boundaries that make the difference between finding someone and creating liability.

Contact rate is the constraint

Work through the funnel and the arithmetic becomes obvious. Recovery requires: a valid contact point, a delivered message, a person who reads it, and a payment path they can act on. Most collections improvement effort targets the last step. The first step fails silently and eliminates everything downstream.

Why it goes unnoticed:

• Failures are invisible. A disconnected number produces no error anyone reads; an email to a dead address bounces into a log nobody checks. The account simply doesn't respond, which looks identical to a customer ignoring you.
• Effort metrics conceal it. An operation measuring accounts worked or messages sent looks productive while sending messages into the void.
• It compounds with age. Contact data degrades continuously, so the older an account gets the less reachable it becomes — which is part of why the decay curve in our collections framework falls as steeply as it does. Some of what looks like declining willingness to pay is declining ability to reach.

The practical reframe: before optimizing messages, find out what share of your outbound actually lands. If a meaningful portion of an aged portfolio is unreachable, data work has a higher return than anything you could do to the copy.

How contact data decays

Every contact point has a half-life, and they differ substantially.

Contact point	Decay driver	Durability
Mobile number	Carrier changes, non-payment disconnection, reassignment	Moderate — and the most consequential to lose
Landline	Abandonment, moves	Low and falling
Personal email	Abandonment, provider changes, deliverability filtering	Relatively high, and underused
Work email	Job change	Low for consumers, moderate for B2B
Physical address	Moves	Moderate, and traceable through forwarding data
Employer	Job change	Low, and constrained in how it may be used

Two dynamics worth naming. Decay correlates with the distress you're collecting on. A customer under financial pressure is more likely to lose a phone line, move to cheaper housing, or change jobs — which means contact data degrades fastest for exactly the accounts where you most need it. And B2B decay runs through people rather than businesses: the company persists while the accounts payable contact leaves, which is why an invoice addressed to a departed employee ages quietly. Capturing a role-based contact alongside a named one is the fix, and it costs nothing.

Capturing data that lasts

The highest-return work happens at onboarding, before there's any problem to collect on.

1. Capture multiple channels. The single phone number collected at signup is the least durable data you'll ever hold. Collect mobile, email, and — for business customers — both a named contact and an accounts payable address that survives turnover.
2. Validate at entry. Phone and email verification at the point of capture costs almost nothing and prevents the typos that render an account unreachable from day one. A meaningful share of bad contact data was never good.
3. Obtain consent properly. Consent for calls, texts, and emails should be captured explicitly at onboarding with a record of what was agreed and when, because retrofitting consent later is difficult and using channels without it creates exposure.
4. Ask for updates at natural moments — order confirmations, account changes, annual reviews. A customer updating their address for a delivery will update it for billing if asked in the same flow.
5. Keep the history. Prior numbers and addresses are the starting point for a trace later, and systems that overwrite rather than append destroy that.
6. For B2B, capture the hierarchy — the buyer, the AP contact, and someone above both. The invoice routing failure our collection letters guide identifies is frequently a contact data problem wearing a messaging costume.

The framing that gets this funded: contact data is a collections asset created by the sales and onboarding process. The teams that capture it bear none of the cost of its absence, which is why it degrades — and why making contact completeness a visible onboarding metric changes behavior.

Unreachable versus avoiding

Silence has two causes requiring opposite responses, and conflating them wastes effort in both directions.

Unreachable means the message never arrived — disconnected number, dead email, wrong address. The response is data work: refresh, trace, try an alternative channel. Escalating tone here is pointless, because nobody is reading it.

Avoiding means the message arrived and the customer chose not to respond. The response is different: change the channel, change the offer, or escalate — and the segmentation in our collections framework applies.

How to tell them apart:

• Delivery signals. Email opens, link clicks, text delivery receipts, and call dispositions all distinguish delivered from undelivered. Capturing them is the entire diagnostic.
• Channel divergence. An account where email is opening but calls fail is reachable; one where nothing lands anywhere is a data problem.
• Payment activity elsewhere. A customer still transacting with you is reachable by definition, which makes non-response a choice rather than a failure.
• Bounce and disconnect codes, which state the answer directly and are routinely discarded.

The operational point: an account should not advance through an escalation sequence on the basis of non-response until you've confirmed the messages were delivered. Sending a final demand to a dead address and then placing the account with an agency is a sequence that produces a placement with no history and no contact — the worst possible input to the process our agency guide describes.

Skip tracing: methods and limits

Skip tracing is locating a customer whose contact information has failed, and it's a legitimate, long-established practice with defined data sources.

What's typically used: credit header information, public records including property and court filings, address change and forwarding data, phone verification and carrier lookup services, and employment data where lawfully available. Providers aggregate these and return likely current contact points.

What determines whether it's worth doing:

• Balance. Tracing costs money per account, so it belongs above a threshold — the expected-value discipline in our metrics guide.
• Age. Tracing an account that's already past your recovery decay point spends money to reach someone who won't pay.
• Prior data quality. A trace starting from a full history of prior addresses and numbers succeeds far more often than one starting from a single stale field.

The limits that matter:

• Permissible purpose. Accessing credit-derived data requires a permissible purpose under credit reporting law, and collection of an existing obligation generally qualifies — but the boundaries are real and worth confirming with counsel rather than assuming.
• Finding is not confirming. A returned number is a probability, not an identification. Using it without verification is how wrong-number liability is created.
• Data quality varies enormously between providers, and a cheap trace returning stale results costs more than it saves.
• Vendor oversight applies. A trace provider is a service provider handling consumer data, with the diligence obligations our compliance guide describes.

The third-party contact rules

Contacting someone other than the customer to find them is permitted within limits that are narrow, specific, and among the most frequently litigated provisions in debt collection.

For third-party collectors, the framework generally permits contacting a third party solely to obtain location information, and requires that the collector:

• Identify themselves and state that they are confirming or correcting location information.
• Not state that the consumer owes a debt. This is the core prohibition and the most common violation.
• Not identify their employer unless expressly asked.
• Generally not contact the same third party more than once, unless requested to do so or unless the collector believes the earlier response was erroneous or incomplete and that the person now has correct information.
• Not use postcards or any language or symbol on an envelope indicating a debt collection purpose.
• Cease contact if the consumer is known to be represented by an attorney.

Two important extensions. Creditors collecting their own debts sit outside the federal third-party framework but remain subject to state law and unfair practices standards — the perimeter our first-party compliance guide maps — and disclosing a debt to a third party is a serious matter regardless of which framework applies. And workplace contact carries additional constraints, including ceasing contact at a workplace where the collector knows the employer prohibits it.

The practical posture: script third-party contact tightly, train it specifically, and record it. The margin between a permitted location inquiry and a disclosure violation is a single sentence, and it's usually crossed by someone trying to be helpful.

Wrong numbers and reassignment

Mobile numbers are reassigned regularly, which creates a specific and growing exposure: a number that was correct when captured may now belong to someone else entirely.

The risks:

• Disclosing a debt to a stranger, which is a violation and a privacy harm.
• Repeated calls to someone who has said they're not the customer, which compounds it substantially and is the pattern most likely to generate a claim.
• Consent doesn't transfer. Consent to be contacted was given by your customer, not by whoever holds the number now — which matters for the telephone contact rules and is the technical basis for a large share of litigation in this area.

The controls that prevent it:

1. Check reassignment data before dialing aged or traced numbers, using the available services designed for this.
2. Verify identity before disclosing anything. Confirm you're speaking to the right person before the conversation turns to the account.
3. Suppress immediately and permanently when someone says they're not the customer — and record it, so the number can't re-enter through a later data refresh.
4. Suppress across the whole system, not just on that account, since the same number may sit on several.
5. Log the disposition so the next person working the account knows.

Channel strategy

Given decay rates and consent requirements, the practical hierarchy for most operations:

• Email is durable, cheap, carries a payment link, produces delivery and open signals, and is forwardable — which matters enormously in B2B. It's underused relative to its performance.
• Text achieves the highest open rates and requires consent handling and opt-out processing, with the quiet-hours and frequency constraints our compliance guide covers.
• Phone resolves complexity and gets commitments, at the highest cost per contact and with the most regulation.
• Physical mail is the most durable against digital decay, provides proof of delivery, and carries weight at formal stages.
• Portal and in-product messaging has no deliverability problem at all where an ongoing relationship exists, and is the most reliable channel available to businesses that have one.

Two design principles. Multi-channel beats single-channel substantially, because decay is channel-specific — an account unreachable by phone is frequently reachable by email. And every channel should carry the payment path, since the point of reaching someone is to let them resolve it, per the structure in our collection letters guide.

What to measure

• Contact rate — the share of attempts reaching the intended person. The headline number and the one most operations don't have.
• Deliverability by channel: bounce rates, disconnect rates, text delivery failures.
• Data completeness at onboarding, by acquisition channel, which is where the problem is created.
• Unreachable share of the portfolio, by age band, which quantifies the opportunity in data work.
• Trace hit rate and cost per successful trace, by provider, since providers differ enormously.
• Recovery lift from refreshed data — the comparison that justifies the spend.
• Wrong-party contact incidents, which is a compliance metric and a leading indicator of a data quality problem.

The single most useful diagnostic if you measure nothing else: what percentage of your aged accounts have a verified working contact point? Most operations don't know, and the answer usually reframes where the recovery problem actually sits.

Frequently asked questions

---

This guide is educational and does not constitute legal advice. Third-party contact rules, permissible purpose requirements, telephone consent obligations, and state collection laws vary and are actively litigated; consult qualified counsel about your scripts and procedures.