Inside a modern debt collection platform: how prediction, routing and compliance actually work


AI-powered debt collection platform" has become the most overused phrase in Indian lending technology, which makes it hard to know what any given vendor's system actually does once the demo ends. This article opens the box. It walks through the four working layers of a modern platform - prediction, routing, engagement and compliance - with enough detail that a collections head or CTO can tell substance from label.

We'll use FrenzoFinserv's architecture as the reference, since it's the one we can describe honestly from the inside, but the layer structure applies to the category.

Layer one: prediction

Everything downstream depends on knowing, per account, the probability of the next EMI being missed. The scoring model consumes several signal families. Repayment behaviour is the strongest: on-time rate, partial payment patterns, bounce history, and the trajectory of all three. Bureau signals add external context - CIBIL score movement, fresh credit enquiries, utilisation trends - because a borrower quietly maxing out three other lines is a stress signal your own ledger can't see. Account characteristics (product type, ticket size, vintage, remaining tenure) set the base rates, and where account aggregator data is available, salary credit patterns sharpen the picture further.

The output is a live probability score per account, refreshed as new data lands. Two things distinguish a working prediction layer from a decorative one. First, it scores current accounts, not just overdue ones - the entire economic case rests on catching stress in the pre-due and SMA-0 window, where recovery probability still sits above 80%. Second, it's trained on Indian lending data. Repayment behaviour around salary cycles, festival seasons and cash-heavy segments doesn't transfer from a model built on US credit card data.

Prediction is also where the compounding happens. Every cycle's outcomes - who paid after which intervention, who rolled anyway - feed back into training. A platform that has run on your portfolio for a year is measurably more accurate than it was at month one, which is a property no static rules engine or human triage process can replicate.

Layer two: routing

A score is only useful if it changes what happens next. The routing engine takes each account's risk score and decides its treatment: which channel, what intensity, what timing, and what escalation path if the first attempt fails.

The decision weighs more than risk. Channel response history matters - a borrower who has paid twice from WhatsApp links should get a WhatsApp link, not a ₹600 field visit. Ticket size sets the economics of how much human attention an account can justify. Timing models learn when each borrower actually engages, because a perfectly worded message sent at the wrong hour is noise.

The output looks like this in practice: a low-risk X-bucket account gets an automated payment reminder sequence; a mid-risk account with declining bureau signals gets queued to a senior agent with full context on screen; a high-ticket account showing strategic-default patterns escalates on a compressed timeline. What disappears is the morning ritual of a collections manager allocating accounts from an Excel export - along with its inconsistency, its bottleneck, and its inability to run at 2 lakh accounts.

Layer three: engagement

The engagement layer executes across SMS, WhatsApp, IVR, email, in-app, agent calling and field visits, and its job is coherence. Each borrower gets one orchestrated sequence rather than uncoordinated pings from disconnected tools. Content is personalised to the account - amount, due date, a working payment link, restructuring options where policy allows - and the sequencing follows the escalation ladder configured from the lender's own collections policy.

A borrower-facing surface belongs in this layer too. FrenzoFinserv ships APRUVIT, a self-service app where borrowers can pay, request EMI restructuring or communicate without an agent in the loop. A meaningful share of early-bucket accounts resolve this way, which is the cheapest possible resolution and, frankly, the one most borrowers who simply forgot prefer.

Layer four: compliance

In India, this layer determines whether the other three are usable at all. The RBI's fair practice requirements, the August 2022 recovery agent circular and the February 2026 draft directions all converge on the same expectations: contact within permitted hours, no harassment or intimidation, controlled data sharing with agents, and complete records of every interaction.

A platform enforces these mechanically rather than aspirationally. Outreach outside permitted windows is blocked at the infrastructure level - not flagged, blocked. Escalation sequences follow regulatory order because the workflow engine won't skip steps. Pattern detection flags communication behaviour that looks like harassment before it becomes a complaint. And every touch - channel, timestamp, content, outcome - lands in an audit trail that can be produced for a supervisory review the same day it's requested. For a lender, this converts compliance from a training-and-hoping problem into a property of the system.

What the four layers add up to

Measured on live portfolios, FrenzoFinserv's stack produces around 35% higher recovery rates on average, roughly 25% faster resolution and about 30% lower collections cost, with the largest bucket-level gains at the two ends of the lifecycle: +38% in pre-due buckets, where prediction opens an intervention window that didn't exist before, and +41% in NPA buckets, where routing concentrates effort on the accounts that can still be saved.

None of it requires replacing your core systems. The platform sits alongside the LMS and LOS, connected over REST APIs in a bi-directional flow - account and DPD data in, outcomes and payment events back - with integration typically done in 2–4 weeks and full go-live in 4–6.

If you want to see the layers running on real data rather than in prose, book a demo. Bring your ugliest DPD report; that's the one the platform is for.

Comments

Popular posts from this blog

Debt Collection Platforms Are Not a Soft Upgrade They’re a Strategic Rewrite

How Debt Recovery Agencies in Mumbai Are Redefining Financial Trust

The Hidden Playbook of Debt Collection: How Agencies in Delhi Recover Money Smartly