Solutions / ARCs
Acquired books, worked systematically from day one
An acquired portfolio arrives as files of unknown quality, and value decays while it is being understood. attpro's upload pipeline maps, validates and enrolls a book in days, then works every account on a strategy instead of a triage spreadsheet.
Where attpro fits
Built for how arcs actually work
Three things a head of resolution needs that a generic dialler does not give them.
Fast onboarding of messy books
Column mapping, preflight validation and staged commits handle files that were never meant to be exported.
Alternate MetaData in the flow
Unreachable accounts route automatically to trace, and re-enter contact flows when new coordinates land.
Settlement machinery
Offer ladders, approval chains and documented settlements - the ARC workflow, not a retrofit.
The first ninety days
What changes, and when
A pilot is one cohort, one flow and one number to beat. This is the shape it takes on a real book.
- 01
Weeks 1 to 3: a portfolio, mapped
Acquired books arrive in the seller's format. Saved mappings, preflight validation and cross-loan grouping turn them into one clean master with a customer view.
- 02
Weeks 4 to 8: trace, contact, offer
Alternate MetaData on stale contacts, outreach across channels, and settlement offers with an approver and a validity window, all recorded on the account.
- 03
Weeks 9 to 13: recovery by vintage
Resolution and collections by acquisition tranche, with the evidence a trustee or an investor asks for.
Reporting and integration
The numbers a head of resolution reports
Each one is a dashboard view, not an export project, and the data gets in without a core-system change.
On the dashboard
- Recovery against acquisition value
- Traceable-contact rate
- Settlement conversion
- Cost per resolved account
Getting connected
File-based onboarding first; APIs when the servicer relationship matures.
What carries the load
Three capabilities do most of the work for arcs
The whole platform is included. These are the parts this segment leans on first.
Flow builder
Draw the strategy once. The engine runs it a lakh times.
A recovery strategy is a graph: contact, wait for what happens, branch on the outcome, escalate. attpro's flow builder makes the graph visible, validates it...
Open flow builderPayments
The shortest path from promise to money in the account
Payment links, UPI and NACH, promises tracked to the day, and a self-service portal where a borrower can settle at midnight without speaking to anyone.
Open paymentsCompliance
Compliance as physics, not policy
Quiet hours, consent, contact caps and evidence are enforced by the engine itself. A call that would breach the rules is not flagged afterwards - it is...
Open complianceQuestions
What arcs ask first
Straight answers to the questions that come before a pilot. The rest, an engineer takes on the demo call.
Can it handle books from many sellers?
Yes. Each upload keeps its saved mapping, and accounts from different sellers for the same customer are grouped so one conversation covers all of them.
Is Alternate MetaData built in?
An Alternate MetaData node calls the provider on your credentials, and the flow branches on results found, none found or failed. Results land on the account with their source.
How are settlements governed?
Offers carry an approver, a floor, a validity and a schedule; acceptance and payment are recorded against the offer. Full restructure workflows are on the roadmap.
Bring one delinquent cohort. We will run it.
A demo here is not a slideshow. Pick a segment of your book, watch a flow built for it, and hear an agent call a test number in your language.