Skip to content
attpro
Book a demo

Platform

attpro CollectOS is an operating system, not a toolbox

A multi-tenant collections platform built in-house. It runs our own 325-person operation today, and lenders licence it to run theirs: one borrower record, one strategy engine, one evidence ledger, and every channel is just a way the loop reaches out.

Book a demoRead the architecture
contact channels
20
languages plus Hinglish
10+1
in-call voice tools
14
record per borrower
1

The loop

One drawing, run per borrower

Portfolio in, strategy, contact, response, and the response feeds the strategy. Money and evidence fall out of every pass.

  1. 01PortfolioLMS export in
  2. 02StrategyAllocation and flow
  3. 03ContactSix channels out
  4. 04ResponseDisposition, payment
  5. Response feeds back into strategy
A borrower is never “done” after one contact. Every disposition and every signal feeds back into the flow, which decides the next step for that one account.

Architecture

How it fits together

Five bands, left to right. Dispositions and signals from the fourth band feed back into the second; that arrow is the platform.

  1. 01

    Data in

    • Lender LMS export
    • Upload wizard: map, preflight, commit

  2. 02

    Decisioning

    • Master data
    • Allocation engine
    • Campaign windows
    • Flow: the playbook

  3. 03

    Contact

    • AI voice agent
    • Human telecaller
    • SMS, WhatsApp, email
    • Field officer, portal

  4. 04

    Response

    • Disposition
    • Payment or PTP
    • Signals: DLR, read, keypress, visit

  5. 05

    Evidence

    • Audit log, hash-chained
    • QA sampling
    • Recordings, transcripts
    • Archive, purge, legal hold

Dispositions and signals feed back into decisioning

Capabilities

The ten working parts

Every part is a page with its own moves, controls and outputs. Open one; the whole system is included in every plan.

The engine

Why it scales to a lakh borrowers

A flow is the recovery playbook. The engine dispatches one node at a time per borrower, and a node that triggers a real-world action never blocks.

  1. 01

    A node that acts never blocks

    A call, a visit or a message parks the run and resumes when the webhook, the lifecycle event or the timeout comes back. A lakh runs cost a lakh rows, not a lakh threads.

  2. 02

    Waiting guard

    A run only resumes if it is actually waiting, so a duplicate webhook cannot double-advance it.

  3. 03

    Prefix guard

    A late delivery receipt cannot resume a run that has already moved on to a different wait.

Node families

does

  • comm.*Contact the borrower on a channel
  • logic.*Branch, gate, split, join
  • wait.*Park until a signal arrives or the timer expires
  • data.*Enrich, score, capture a form, call a webhook
  • alloc.*Re-allocate, suppress, build a cohort
The flow builder

Built for India

Not a western dialer with a Hindi voice pack

The defaults assume Indian lending, because that is the only thing this platform does.

10+1languages plus Hinglish
Voice agents that speak the borrower's language, not a call centre's.
₹lakh and crore, everywhere
Amounts spoken and printed the way people actually say them.
UPINACH · Razorpay · Cashfree
Indian rails by default. DPD buckets and DRA-aligned conduct as defaults.
INdata residency
Deployment and storage in-country, with your own provider credentials.

Integration

Plugs into the stack you have

A nightly LMS export over SFTP is enough to start. REST and webhooks when you want same-day state. Your MIS keeps working.

Your systems

  • LMS / core banking
  • CSV over SFTP
  • REST + webhooks

attpro

  • The recovery loop
  • Every channel
  • Evidence ledger

Your reporting

  • MIS / CRM / BI
  • Webhooks out
  • Extracts on demand

Payments reconcile through Razorpay and Cashfree callbacks. Every integration is listed on the integrations page.

The surfaces

What the operator sees

Recreated in miniature. The demo runs the real thing on a cohort shaped like yours.

Flow builderillustration
Illustration of the flow builder: an AI call node branching on promise, no answer and dispute into a payment wait, a retry ladder and a human queue, each with its own outcome
Borrower 360illustration
Illustration of the borrower record: identity, outstanding, promise status and the contact timeline in one view
Operations dashboardillustration
Illustration of the operations dashboard: cured, promise-kept rate, cost per account and at-risk counters, recovery by day rising across the week, and resolution by DPD bucket

Day one

What you get, running our own book on it today

Every capability below is in production, not planned. Multi-tenant, flow engine, AI voice and the audit trail are the floor, not the roadmap.

10 Indian languages plus Hinglish

Hindi, Tamil, Telugu, Marathi, Bengali and more - and the Hinglish borrowers actually speak - natively, not translated.

Sub-second voice

Real-time, interruptible conversation that does not feel like an IVR menu.

True omnichannel

Voice, WhatsApp, SMS, RCS, email, self-serve and field on one journey and one record.

Compliance by design

RBI, DPDP and TRAI rules enforced by the system on every single touch.

Self-serve, one-tap pay

Borrowers resolve on their own terms, at any hour, in a couple of taps.

Field and legal, one journey

Doorstep visits and legal steps flow from the same automation, fully tracked.

Live analytics and QA

Every call, promise and payment measured, with automatic quality sampling.

One record per borrower

Whichever channel touched them, and whoever asks for the evidence.

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.

Book a demoTalk to an engineer