When They Call You: The Contacts Worth More Than Any Campaign

Collections operations are built around outbound. The dialer, the campaign design, the contact strategy, the metrics — all of it exists to manufacture a conversation with someone who hasn't sought one. Meanwhile, people call in. They've decided to engage, they've spent their own time getting through, and they've eliminated every problem the outbound machine exists to solve. And in most operations they wait in a queue behind that machine, reach whoever is free, and are told someone will call them back. The most valuable contact in the operation is handled with leftover capacity.

Why inbound is different

	Outbound attempt	Inbound contact
Cost to generate	Substantial, per our cost analysis	Zero
Right party reached?	Frequently not	By definition
Willing to engage?	Unknown	Already decided
Persuasion needed	The whole call	Little or none
Complaint risk	Real	Much lower
Typically staffed	Heavily	With whatever is left

Five rows favour inbound decisively and the sixth inverts the allocation. That inversion is the finding.

Why it happens is structural rather than foolish. Outbound is controllable and measurable — you decide how many attempts to make and you can report on them. Inbound arrives when it arrives, so it looks like a cost centre rather than a channel, and gets managed to a service level instead of to recovery.

Which is a version of the measurement problem our measurement analysis describes: the channel you control generates activity data, and the channel that generates itself doesn't get credited with what it produces.

Why they're calling

Knowing the mix matters, because the responses differ and a single queue serves none of them well.

• To pay. The highest-value and the easiest to lose — if paying requires a conversation, some of these callers will abandon.
• To arrange something, per our plan guide. High value, needs authority.
• To explain a difficulty, which per our disclosure analysis requires recognition and a defined response.
• To dispute, which per our dispute analysis triggers obligations — and must be recognized as a dispute even when phrased as a complaint.
• To restrict contact, per our restrictions guide, which takes effect immediately.
• To say it isn't them — wrong party, or identity theft.
• To complain, per our complaint analysis.
• To ask what this is, having received a letter they didn't understand.

The first two are the recovery opportunities and the rest are obligations — and several of the obligations are ones where failing to recognize the call type creates a compliance problem rather than just a poor experience.

Which argues for identifying intent early, at the menu or in the first question, and routing accordingly.

Where it goes wrong

The failures, in rough order of how much they cost:

1. Waiting. Someone calling between shifts or on a break won't hold — and per our time analysis, the callers with the least schedule control are exactly the ones a queue filters out.
2. No authority to resolve, covered below.
3. A menu designed for outbound, where "make a payment" is buried.
4. Requiring identification the caller can't provide — an account number they don't have, from a letter they've lost.
5. Reaching someone without the file, so the story has to be told again.
6. Being told to call back during hours they can't.
7. A scripted outbound approach applied to someone who already agreed — pressure on a willing caller is the fastest way to lose one.

The fourth is worth fixing immediately and rarely is. A caller who received a letter, lost it, and rang the number they remembered should be identifiable by name and address. Requiring a reference they don't have turns a willing payer away at the door.

And the seventh is a training point with real value. A collector trained on outbound reflexes will negotiate against someone who already said yes — asking for more than offered, resisting a plan the caller proposed — and convert a resolution into an argument.

Authority on the call

The single highest-return change available to most operations.

A caller who has to be called back frequently isn't reached again. They called in a window they had; the callback lands in one they don't. So an arrangement requiring approval is an arrangement that may never happen.

What front-line staff should be able to do without escalation:

• Take a payment, in any amount.
• Set up a plan within defined parameters.
• Change a due date.
• Apply a short pause where circumstances warrant.
• Record a dispute and start the process.
• Apply a contact restriction immediately.
• Record a vulnerability disclosure and act on the defined response.
• Accept an amount below target where it's within the band.

The last is where operations lose the most. Per our plan guide, a plan the person can sustain outperforms a larger one that fails — so a collector negotiating up to a figure the caller doubted has traded a working arrangement for a broken one, and per our incentive analysis the compensation plan may be why.

Define the bands, delegate within them, and monitor the outcomes rather than approving each one.

The ones who don't want to talk

A substantial share of inbound contact is an attempt to pay without a conversation.

Per our small balance analysis, self-service resolution is the lowest-cost outcome available and it's also what many people prefer — a call to a collections line is unpleasant, and someone willing to pay may not be willing to discuss it.

What needs to exist:

• A direct payment path requiring no account creation.
• Balance visibility without a call.
• Plan setup without a call — the capability that converts the most people, since arranging is exactly what people want to avoid discussing.
• An automated phone payment option, for callers who don't use a portal.
• Prominent placement in the phone menu, not buried.
• Everything available at any hour.

A menu that routes payment-intent callers to a queue is the most expensive design choice in this area — it takes the cheapest, highest-intent contact available and puts a hold time in front of it.

Being reachable

The availability question, and it's the time-poverty finding applied to an operation.

The consumers hardest to reach by day are those whose work makes daytime calls impossible. An operation available only during business hours is available mainly to people who can take personal calls at work — which excludes shift workers, hourly workers, and anyone with less schedule control.

Which produces a specific and correctable failure: the population your outbound campaigns struggle to reach is the population your inbound line is closed to. The same constraint causes both, and one of them is fixable at low cost.

What helps, in order of cost:

• Self-service at any hour — most of the benefit, least of the cost.
• Automated phone payment outside staffed hours.
• Extended staffed hours, at least some evenings.
• A callback at a time the caller chooses rather than when you're free.
• Text and email channels, which are asynchronous and remove the timing problem entirely.

The fifth deserves more weight than it gets. A person who can't call can message, and per our small balance analysis those channels cost almost nothing — so the operation that treats text as an outbound tool only has missed half its value.

Abandonment as lost recovery

The measurement change that makes the case internally.

Most operations track abandonment as a queue statistic. Reframe it: an abandoned inbound call is someone who decided to resolve a debt and couldn't get through.

How to quantify it:

1. Count abandoned inbound calls over a period.
2. Match them to accounts where the number identifies one.
3. Total the balances behind those calls.
4. Apply your inbound resolution rate — which should be far above outbound.
5. That's the recovery you dropped.

The figure is usually larger than anyone expected, because the resolution rate applied is the high one rather than the outbound one — and it converts a service-level conversation into a financial one, which is what changes staffing decisions.

What else to track:

• Inbound resolution rate against outbound, separately.
• Wait time for inbound specifically, not blended.
• Share resolved on first contact, which measures authority.
• Callbacks needed, and how many connect — the second number is the one that shows the cost.
• Self-service share of inbound intent.
• Abandonment by time of day, which shows where staffing is wrong.

Designing for inbound

1. Separate inbound from outbound in reporting entirely.
2. Prioritize inbound in routing, ahead of outbound activity.
3. Staff to inbound demand by hour, using the abandonment-by-hour data.
4. Build self-service and place it first in the menu.
5. Identify intent early and route accordingly.
6. Delegate authority within defined bands.
7. Allow identification by name and address where a reference isn't available.
8. Train inbound handling separately from outbound, since the reflexes differ.
9. Offer asynchronous channels for people who can't call.
10. Report abandonment as lost recovery.

Items four, six, and ten carry most of the value — self-service captures the people who don't want to talk, delegated authority captures the people who do, and the reporting change is what gets the first two funded.

The framing worth keeping: an inbound contact is the outcome an outbound campaign is trying to buy, arriving for free. An operation that spends heavily to manufacture conversations and lets the volunteered ones abandon has its economics exactly backwards.

Frequently asked questions

---

This guide is educational and does not constitute legal or compliance advice. Requirements governing disclosures on consumer-initiated calls, dispute handling, contact restrictions, recording and consent, and identification procedures vary by jurisdiction and by whether the collector is a first or third party. Consult qualified counsel about the requirements applicable to your operation.