AI Products
Customer-facing
Employee-facing
Who We Help
Employee-facing
Platform
Trust & Security
Copyright ©0000 Posh AI. All Rights Reserved.
Ask any ARM operator how long it takes to build a collector who is reliably good and you will hear some version of three years. Ask them why and the answer gets vague. Experience. Reps. Time on the phone.
That vagueness is worth pushing on. Three years is roughly how long it takes to accumulate enough live encounters with hard call types when live accounts are the only place those call types exist. Nothing about the number is fixed.
A new hire finishes four weeks of class. Then nesting, live, with a supervisor listening. Then they are on their own, with nobody listening unless a call gets pulled for QA. From that point forward, every hard thing they learn, they learn on a real consumer who owed real money and isn't calling back.
They might go six weeks without meeting a hostile interrupter. Two months before someone discloses a disability and exempt income. Longer before a non-consumer picks up and the FDCPA changes what they are allowed to say mid-sentence. Each of those first encounters is a live account, and each one mostly goes badly, because a first attempt at anything goes badly.
The three years is just how long it takes for those encounters to happen at random.
Every floor supervisor can name the two or three people on their team who should not be taking live accounts yet. They know it in week two of nesting.
They also have no mechanism to act on it, because the only alternative to putting that person on the phone isn't putting them on the phone, and the seats have to be filled. So the collector goes live, works accounts at a quality level everyone privately knows isn't ready, and the cost of that gets absorbed silently into the portfolio.
That's the actual problem, and it has nothing to do with hiring or motivation. There's nowhere for a collector to fail safely, so they fail on your paper.
In most contact center work, a fumbled call gets a second chance. The customer calls back. The order gets fixed.
Collections doesn't work that way. Right party contact rates on outbound attempts sit in the single digits, and consumers who reach RPC typically engage once. If the collector freezes, pushes for payment before acknowledging a hardship, or lands the mini-Miranda out of the order that client requires, the account doesn't get resolved next week instead. It goes back in the queue, then to the next agency in the chain.
So a new collector's mistakes aren't recoverable errors. They're permanently lost accounts, on paper you already paid to get placed with you.
And the people absorbing those losses mostly leave before you get anything back. At one national agency collecting for bank and card-issuer clients, roughly one in six new hires is still on the floor at twelve months. The other five were recruited, licensed, paid through class, nested and coached, and left before becoming the collector the investment was for.
"Our strongest collectors have been with us 15 to 20 years. Building that depth of skill in a new hire takes us far longer than any of us would like." President and CEO, national third-party collection agency
Replacement cost is everything you spend to put a person on the floor. Sourcing, screening, licensing, classroom weeks, nesting weeks, supervisor hours, workstation. It's on somebody's spreadsheet already. It stops the day they take live accounts.
Readiness cost is what you lose between that day and the day they are actually good. It appears nowhere. It shows up as lower liquidation on the accounts they touched, as complaints, as promises that were never going to be kept, and as disclosure misses your QA team finds weeks later on a call that already ended.
Replacement cost runs for weeks. Readiness cost runs for years. Almost every agency reports the first one.
An industry benchmark won't convince your board. Yours will. Four inputs:
Item 1 times item 2 is what most agencies already report. Item 3 is usually larger. Item 4 is the one that can cost you a portfolio.
You can attack turnover or you can attack ramp.
Turnover is a labor market problem. You can pay more, and your competitor two exits down the highway can also pay more. There's a floor on how much of it you can solve.
Ramp is an operations problem, which makes it the one you can actually move. And it moves in two directions: the collector produces sooner, and collectors who feel competent quit less, so going after ramp goes after turnover as a side effect.
What moves it is where the first hard encounter happens, not how many hours of training came before it.
A new collector should meet the interrupter who talks over every disclosure, the consumer who opens with a job loss, and the third party who picks up the phone, before they ever work a real account. Scored against your scorecard, your client's authority levels, your disclosure order. Not a generic roleplay library, which is how simulation got a bad name in this industry, and not once during onboarding week, but until they clear the bar.
Then the standard becomes something you can state: no collector takes a live account until they have demonstrated they can handle the calls that matter. Right now, almost nobody in this industry can say that sentence and mean it.
Ramp claims are not new. Guidance and simulation vendors have published them for years, and some are credible. One agency reported cutting onboarding from six to eight weeks down to four with real-time guidance. Simulation vendors report speed-to-proficiency gains north of 50%.
Read those carefully, because they measure a different thing than the three years.
Time to first productive call is a short number. It covers classroom, nesting, and the point where someone can work a straightforward account without a supervisor listening. Compressing it is genuinely valuable and the published results are real.
Time to reliably good on the hard calls is the long number. That is the collector who handles a hardship disclosure with exempt income, an interrupter, and a third-party answer, correctly, in the same eight minutes, under a client's specific disclosure order. Nothing in the first number tells you about the second.
The distinction matters more now than it used to, because automation is removing the straightforward accounts the first number is measured on. When most of what reaches a human is hard, the short ramp stops being the one that determines what you recover.
Ask any vendor quoting a ramp figure which of the two it measures, and what evidence they have for the other one.
Posh Simulator is the certification step. Collectors run the hardest call types before they take a live account, and every attempt is scored against your criteria rather than a vendor's.
The part that matters for ramp is where the scenarios come from. Simulator generates them from your scripts, your client's authority levels and your scorecard, so when a placement changes its settlement terms or its disclosure order, the drill changes with it. That's the difference between practice that stays current and a scenario library that goes stale in a quarter, which is what soured most agencies on simulation the first time around.
Simulator never speaks to a consumer. It talks to your collector, which is usually the shortest compliance conversation in this category.
It also runs on the same knowledge base as Posh Knowledge Assistant and Posh CoachQA, so what a collector rehearses, looks up mid-call, and gets scored against stay in sync. Posh is the only platform that runs all three on one knowledge base. Most agencies start with one of them.
Ramp, turnover and contact figures reflect the operating experience of a national third-party collection agency collecting for bank and card-issuer clients, shared with permission. They're illustrative rather than industry benchmarks.
See it on your own script. Send us one client script and one scenario your collectors struggle with, and we'll show you how that requirement becomes a practice drill, a source-backed live answer, and a documented QA criterion. 45 minutes, nothing to prepare beyond the script.