Debt Management
Collections performance, treatment outcomes and fair-value evidence in one place.
Collections runs on operational data that rarely reaches the board intact. Contact outcomes live in the dialler, arrangements in the servicing system, and customer outcomes nowhere in particular. We join them so treatment effectiveness and customer harm are both measurable.
The numbers that matter here
What we'd connect here
Whatever it is and however it exposes itself — API, database, nightly file, or a spreadsheet somebody maintains by hand. We only ever need read access, with personal data excluded.
What we do about it
Where it hurts
- Contact, arrangement and payment data spread across three systems
- Treatment effectiveness argued from agent anecdote
- No evidence trail for fair value or vulnerable-customer outcomes
- Cure and breakage rates recalculated by hand every month
What Acta builds
- One customer timeline across contact, arrangement, payment and outcome
- Treatment pathway performance, cure and breakage by cohort
- Vulnerability and forbearance flags carried through to reporting
- Regulatory outcome reporting with the working shown
What you get
Evidence that a treatment strategy works, and where it quietly does not.
Live in months rather than years, from £5k a month, on your own Google environment — handed over to you, or run by us.
Inside a debt management engagement
Collections runs on more operational data than almost any other function and turns almost none of it into evidence. Contact outcomes sit in the dialler, arrangements in the servicing system, payments with the provider, and complaints and vulnerability notes somewhere else again. So treatment effectiveness gets argued from agent anecdote, and cure and breakage are recalculated by hand each month from exports that never quite line up.
We join those systems into one timeline per customer — every contact, arrangement, payment and outcome in order — in your own BigQuery, and carry the vulnerability and forbearance flags through with it rather than dropping them at the reporting boundary. The pattern that usually surfaces first is a treatment pathway that looks strong on cure but quietly high on breakage a few months out, which a point-in-time cure number was never going to show. Measuring by cohort and pathway makes the difference between a strategy that works and one that only appears to.
The output is fair-value and vulnerable-customer evidence with the working shown, and treatment performance you can actually act on: which pathways to expand, which to retire, and where a cohort is being harmed rather than helped. Cost to collect, contact-to-arrangement and promise-kept rates all read from the same events, so an operational decision and its regulatory evidence are the same number rather than two reconciliations.
What this looks like in debt management.
Common questions
Can you measure whether a treatment strategy actually works?
Yes — that is usually the first thing we build. We join contact outcomes from the dialler, arrangements from the servicing system and payments into one customer timeline, then measure cure and breakage by cohort and pathway. You see which treatments work and where one quietly does not.
How do you evidence fair value and vulnerable-customer outcomes?
We carry vulnerability and forbearance flags through from the operational systems into the reporting layer, so outcome reporting shows the working rather than a headline number. Every figure has an auditable trail back to the events behind it, which is what a fair-value review needs.
Our contact, arrangement and payment data live in three systems — is that a problem?
No, that is the normal starting point. We connect each system and land its events in your own BigQuery, then join them into one timeline per customer. Nothing has to be migrated or replaced — we work in your environment and read from the systems you already run.
Which debt management systems do you connect to?
Whatever you already run — it makes no difference whether a system exposes an API, a database view, a nightly file or a spreadsheet somebody maintains by hand. In debt management that usually means: Case management platform; Creditor file exchanges over SFTP; Payment processor; Client portal; Dialler and call recording; In-house Access and SQL databases. We only ever need read access with personal data excluded, and the layer is built in your own Google environment rather than ours.
Other sectors
Bring one decision your data should be helping you make.
30 minutes, no deck. We'll tell you on the call whether we're the right partner, and exactly what we'd ship in the first 30 days.