Product 01 — Recovery platform

Know who paid
before the agent knocks.

Most collections software fails on one detail: the field team works off yesterday's data. An agent visits a customer who paid that morning, trust drops, and the receipt they do collect takes four days to reconcile. This platform runs on live balances and captures everything at the doorstep — with or without a network connection.

Risk-based allocation Offline field app Geo-tagged receipts Same-day reconciliation
Request a demo See the modules
What is inside

Six modules, one live balance.

Every module reads the same account state, so the tele agent, the field agent and the legal team never work from different numbers.

C/01

Allocation engine

Assigns accounts by DPD bucket, ticket size, geography, past behaviour and agent capacity. Rules are configurable by your recovery head — no developer needed to change how a bucket routes when the strategy shifts mid-quarter.

DPD bucketsCapacity aware
C/02

Field agent app

Day plan with an optimised route, customer history, live balance, receipt capture, photo proof and GPS stamp. Works fully offline and syncs when signal returns — nothing is lost to a dead zone mid-visit.

Offline-firstRoute planning
C/03

Receipting & cash

Bluetooth thermal printing at the doorstep, so the customer holds a receipt before the agent leaves. Cash-in-hand tracked per agent, deposit slips matched against bank credits automatically, and shortfalls flagged the same day.

Thermal printDeposit matching
C/04

Tele-calling & digital

Dialler integration with call disposition, promise-to-pay tracking and automatic follow-up scheduling. Payment links over SMS and WhatsApp, so a soft bucket customer settles without anyone visiting at all.

PTP trackingPayment links
C/05

Legal & settlement

Notice generation, SARFAESI and cheque-bounce case tracking, hearing calendars and advocate assignment. Settlement offers routed through approval limits by role, with waivers posting back to the ledger as proper entries.

Case trackingApproval limits
C/06

Analytics & supervision

Recovery by bucket, agent and branch, roll-forward and roll-back rates, and a live map of where the field team actually is. Supervisors see productivity without asking, and dormant agents surface before payroll does.

Roll ratesLive map
Why rollouts fail

Four reasons agents go back to paper.

When a client tells us the last collections app was abandoned, the cause is almost always on this list. None of them are about features.

One lost entry to a dropped connection and the agent never opens the app again.

It assumed a connection

Tier-3 towns, basements, lift lobbies. The visit, receipt, photo and GPS fix are written locally and queued, with conflict rules agreed with your recovery head before we build them. Nothing depends on signal at the moment of capture.

Nothing lost offline

It flattened the phone by 2pm

Continuous GPS polling kills a battery before the shift ends, and an agent with a dead phone stops using the app permanently. Location is batched, sync backs off intelligently, and draw is measured across a simulated eight-hour day before release.

Tested over a full shift

Balances were a day old

Nightly extracts mean agents chase customers who have already paid. That single experience destroys credibility with both the customer and the agent. We read live from your core system, so what the app shows is what the ledger says.

Live, not overnight

It needed training nobody got

Four hundred field staff will not read a manual. Screens are built around one task, with large touch targets for use while standing and the common path completed in as few taps as possible. We observe real agents attempting it before launch, not after.

Observed with real users
Proof

Two failed rollouts, then one that stuck.

NBFC · 400-person field force 🇮🇳 India · 7 months · Under NDA

Cash reconciliation from four days to one

The problem

Two previous apps had been rolled out and abandoned inside a fortnight. Agents lost connectivity mid-visit, entries vanished, and everyone reverted to paper receipts. Head office reconciled cash deposits against handwritten books four days later, and shortfalls were untraceable by then.

What we did

Rebuilt offline-first with conflict rules agreed with the recovery head, Bluetooth thermal receipts at the doorstep, and allocation moved to a risk-and-geography engine that plans each agent's day. Battery draw was measured on the exact handset model the agents carry.

94%
Daily active agents
4d → 1d
Cash reconciliation lag
+18%
Visits per agent per day
Before you call

Common questions.

Ask something else

Yes, that is the normal case. We integrate with your core for balances, receipts and payment posting. If your system has no usable API, we build a sync layer — and we will tell you during the fit assessment whether that is a two-week job or a two-month one, before you sign anything.

Eight to fourteen weeks. Configuration and integration take most of it; the app itself is largely built. Rollout is phased by branch or region rather than switched on everywhere at once, so problems surface with fifty agents instead of four hundred.

Mock-location detection is built in, photos carry capture metadata, and receipt numbers are issued server-side rather than generated on the device. No system makes fraud impossible, but supervisors see route deviation, timing anomalies and clustered receipts — which catches the patterns that actually occur.

Supported as scoped users. An agency sees only its allocated accounts, its own performance and its own commission statement — never your wider book. Agency-level recovery reporting and payout calculation are part of the platform.

Next step

Let your recovery head
try to break it.

Forty-five minutes on a live demo with realistic data. Bring the people who run collections and the phone your agents actually carry.

Request a demo See the lending core