Recalling Accounts From an Agency: Doing It Cleanly | HL Hunt
Recalling Accounts From an Agency: Doing It Cleanly
Placing accounts with an agency is routine. Getting them back is usually undocumented until the first time it goes wrong, and it goes wrong in two distinct ways. Urgent recalls have to move in hours, because a bankruptcy or a cease contact request that waits for the nightly file has already produced calls that should not have happened. Bulk recalls generate commission disputes: on 3,000 accounts, an unspecified tail period puts about $39,648 in play, decided by one clause nobody read until afterward.
What you'll learn
Why accounts come back
Placing accounts with an agency is routine. Getting them back is not, and the recall process is usually undocumented until the first time it goes wrong.
Recalls happen for reasons that fall into two very different groups:
| Reason | Urgency | Group |
|---|---|---|
| Bankruptcy filed | Immediate, stop all activity | Must recall |
| Customer deceased | Immediate, per our deceased accounts analysis | Must recall |
| Dispute or fraud claim raised | Immediate suspension | Must recall |
| Balance found to be wrong | Immediate, per our accuracy analysis | Must recall |
| Cease contact received at origin | Immediate, per our cease contact analysis | Must recall |
| Litigation or regulatory contact | Immediate | Must recall |
| Account paid at origin | Immediate | Must recall |
| Agency underperforming | Planned | Commercial |
| Portfolio being sold or re-placed | Planned | Commercial |
| Contract ending | Planned | Commercial |
The two groups need entirely different machinery. The first seven are single-account events that must move in hours and cannot wait for a batch. The last three are bulk movements that need a schedule, a reconciliation, and a commission settlement. Operations that build only the second kind discover the gap when a bankruptcy notice arrives on a Friday.
The recall that has to work in hours
A bankruptcy filing, a cease contact request, a fraud claim, or a discovery that the balance is wrong all require collection activity to stop, and the obligation sits with the creditor regardless of who is holding the account. An agency that learns about it in the next nightly file has already made calls it should not have made. Every one of these needs a same-day channel that does not depend on the regular placement feed, and someone at the agency who can confirm receipt.
The commission question nobody settles in advance
This is where recalls generate disputes, and the arithmetic is large enough to justify getting it right in the contract.
An agency has worked an account for 40 days. It is recalled. Five days later the customer pays the creditor directly. Who earned the commission?
The standard answer is a tail period: the agency earns on payments received within some window after recall, on the basis that its work produced them. The size of the exposure:
- Portfolio recalled: 3,000 accounts at an average balance of $1,180
- Paying within a 60-day tail: 4%, or 120 accounts
- Payments received: $141,600
- Commission at stake at 28%: $39,648
What the contract needs to say is narrow and specific:
- The tail length, in days, from the recall effective date rather than from the notice date.
- Whether the tail applies to all recalls or only to commercial ones. An account recalled because the balance was wrong should not generate commission, and an account recalled for convenience arguably should.
- Which payments count: payments to the creditor, payments to the agency after recall, and payments arising from an arrangement the agency set up are three different things.
- The reporting obligation, meaning who tells whom about a payment and within what period.
- How arrangements in progress are treated, per our payment plan analysis, since a customer paying an agreed plan is the most valuable thing a recall can disrupt.
Item five is the one with a customer consequence rather than only a commercial one. A recall that silently breaks a working arrangement produces a customer who made a plan, kept it, and then received a demand from a different party. Per our customer view analysis, that is exactly the experience that ends engagement permanently.
What has to come back with the account
The account returns; the knowledge frequently does not, and rebuilding it costs more than the recall saved.
- All contact attempts and outcomes, so the next party does not repeat what failed.
- Updated contact data, per our contact analysis, which is often the most valuable thing the agency produced.
- Every promise, arrangement, and payment, including broken ones and their dates.
- Disputes raised and how they were resolved, because an unresolved dispute that disappears in a handover reappears as a complaint.
- Vulnerability and treatment flags, per our vulnerability analysis, which must not be lost in transit under any circumstances.
- Cease contact and channel restrictions, which are legal constraints rather than preferences.
- Any documentation supplied by the customer, which they will not want to supply twice.
Items five and six are the ones where a data loss becomes a compliance failure rather than an inconvenience. A customer who told the agency not to call at work, or disclosed a circumstance requiring different treatment, has told the creditor as far as they are concerned. Per our boarding analysis, a transfer that drops those flags produces conduct that would never have been approved deliberately.
Building the process
- Define two paths. An urgent single-account path measured in hours and a bulk path measured in days, with different channels and different confirmations.
- Require acknowledgement, not just transmission. Per our notice analysis, a recall notice sent is not a recall notice acted on, and the difference matters when an agency contacts a bankrupt customer the day after you sent it.
- Suspend on both systems simultaneously. An account recalled at origin and still active at the agency is the failure mode this whole process exists to prevent.
- Specify the data return format in the contract, including the fields above, and test it before you need it.
- Reconcile the return. Accounts sent, accounts returned, accounts unaccounted for. The third number should be zero and frequently is not.
- Settle commission against an agreed statement within a defined period rather than leaving it open.
- Confirm furnishing responsibility, because the party reporting the account must change when the holder does and a gap or an overlap both produce a consumer file error.
- Tell the customer. Per our compliance analysis, someone who has been dealing with one party and is now dealing with another should hear it from you rather than infer it from a different letterhead.
Item seven is the one that reaches the consumer's credit file. Two parties furnishing the same account produces a duplicate, and neither furnishing it produces a stale record that keeps reporting whatever it last said. Per our errors analysis, both are difficult for the consumer to correct and neither is visible to the operation that caused it.
Item five catches a quieter problem. Accounts that were placed, were never worked, and do not come back in the return file are still somewhere, and an account nobody is certain about is an account still capable of generating contact.
Recalls that move at the speed the reason requires
HL Hunt AI Debt Collection separates urgent single-account recalls from bulk movements, requires acknowledgement rather than transmission, suspends activity on both sides at once, carries treatment and restriction flags through every transfer, and reconciles returns account by account.
Recalling to re-place
Most bulk recalls exist to move a portfolio elsewhere, and the decision to move deserves more scrutiny than it usually gets.
- Compare like for like. Per our benchmarking analysis, an agency handed older and thinner accounts will underperform one handed fresher ones, and the comparison is about placement quality before it is about agency quality.
- Recognize what re-placement destroys. Contact data, established relationships, and arrangements in progress all reset, and per our prioritization analysis the accounts most damaged are the engaged ones that were about to pay.
- Expect a dip. A newly placed portfolio recovers slowly at first while the new agency works through contact, so a comparison made in the first sixty days will always favour the incumbent.
- Consider splitting rather than moving. Per our testing analysis, placing a randomized portion with a challenger answers the performance question without disrupting the whole book.
The fourth point is the one worth adopting as standing practice. A split placement makes agency performance measurable rather than arguable, costs nothing beyond the administration, and removes the situation where a portfolio is moved on a comparison that was never valid.
Know where every placed account is
Get started with HL Hunt AI Debt Collection for acknowledged recalls with same-day escalation paths, account-level return reconciliation that surfaces what did not come back, and furnishing ownership that transfers with the account rather than beside it.
Frequently asked questions
Bankruptcy, death, disputes or fraud claims, wrong balances, cease contact requests, litigation, and payment at origin. All need a same-day channel outside the nightly feed.
Whatever the contract specifies, which is why it must. On 3,000 accounts with a 60-day tail and 4% paying, $39,648 of commission is at stake.
Contact outcomes, updated contact data, arrangements, disputes, customer documentation, and above all vulnerability flags and contact restrictions, which are legal constraints.
Usually not on the comparison being made. Split-place a randomized portion with a challenger instead, since re-placement resets contact data and breaks arrangements in progress.
Key takeaways
- Urgent single-account recalls and bulk portfolio movements need entirely different machinery, and most operations build only the second.
- Bankruptcy, death, disputes, wrong balances, cease contact, litigation and payment at origin all need a same-day channel outside the regular feed.
- On 3,000 accounts averaging $1,180 with 4% paying in a 60-day tail, $39,648 of commission turns on one contract clause.
- Specify the tail from the recall effective date, whether it applies to all recalls, and which payments count.
- A recall that silently breaks a working arrangement produces a customer who kept a plan and then got a demand from someone else.
- Vulnerability flags and contact restrictions are legal constraints, and losing them in a transfer produces conduct nobody approved.
- Require acknowledgement rather than transmission, and suspend activity on both systems at once.
- Confirm which party furnishes after a recall, since a gap or an overlap both create a consumer file error the operation cannot see.
This guide is educational and does not constitute legal or compliance advice. All figures are stylized illustrations using assumed portfolio sizes, balances, payment rates, and commission rates, and do not describe any particular operation or agency agreement. Obligations following notice of bankruptcy, death, dispute, cease contact, or attorney representation, and requirements for furnishing accuracy during a transfer of holder, vary by jurisdiction and by product. Have agency agreements and recall procedures reviewed by qualified counsel and your compliance function.