Private platform

Run credit recovery from one system.

RecoveryOS is a management and automation platform for recovery agencies that work for several banks. It covers the whole job: cases, people and money.

Management dashboard: recovery today and this month, promises to pay, field visits, unreconciled items and the exception work queues.
The management dashboard, from the product design. Sample data. Click any screen to enlarge it.
  • 10steps in a case’s life, on one path
  • 12screens designed so far
  • 6roles, each with its own scope
  • 14rules the system never breaks

How agencies run today

  • Bank apps
  • Excel sheets
  • WhatsApp groups
  • Phone calls

With RecoveryOS

One system, one record for each case, and a queue of what needs a decision.

Case lifecycle

From the bank’s file to closure.

Ten steps, one path. Nothing depends on someone remembering to update a sheet.

  1. 01Bank file import
  2. 02Assignment
  3. 03Calling
  4. 04Promise to pay
  5. 05Follow-up
  6. 06Field visit
  7. 07Collection
  8. 08Bank confirmation
  9. 09Reconciliation
  10. 10Closure

Modules

A screen for every part of the job.

Eight of the workspaces, in the order the work happens. These are the product designs, shown as they are.

01 Cases

Load the bank’s file once, safely

Every bank sends its accounts in its own format. You map each bank’s columns once, and every later file is checked before anything is saved.

  • Excel and CSV files, with a column mapping per bank
  • Validation and duplicate detection, with a preview before you confirm
  • The bank’s original values are kept exactly as supplied
  • An error report and a history of every import
Schema workbench: the banks and their schema versions, a source-to-canonical column mapping, delinquency buckets, a dry-run parser and the version history.

02 Cases

One record for every account

Search and filter the whole portfolio by bank, bucket and status, assign in bulk, and open any account to see everything that has happened to it.

  • Customer and employer profile, with the amount outstanding
  • Call logs, promise-to-pay history, field trail and ledger
  • Log a promise, assign a visit, record a payment or escalate from one place
  • An audit log for the account that nobody can edit
Accounts and cases: the case list with bucket filters and bulk allocation, a collections trend, and one account opened with its contact, promise and audit memo.

03 Cases

A workspace built for calling

A telecaller sees only the cases assigned to them: the queue on the left, the account in the middle and the outcome on the right.

  • A work queue ordered by what is due, broken or new
  • The account’s call history and promise history in view while calling
  • One-tap call outcomes, with the promise amount and date
  • Save and move to the next case without leaving the screen
Telecalling workspace: shift performance, queue segments, the assigned account ledger, the selected account with its contacts and the case interaction trail.

04 Cases

Field visits and the cash they collect

Visits move through a clear pipeline, and cash collected in the field is tracked until it is deposited and the bank has it.

  • Visits assigned, accepted, started, completed or failed
  • Cash awaiting deposit, with the receipts behind it
  • A registry of every visit with its outcome
  • Authorization before cash counts as deposited
Field operations: visit counts by stage, the day’s cash vault, officer status, the live visit queue and a visit dossier with its field evidence.

05 Money

Reconcile against the bank’s paid file

The bank’s paid file is the only source that confirms a payment. RecoveryOS compares it with what your team recorded and raises what does not match.

  • Upload the paid file and watch the matching run
  • Exceptions with an owner, a status and the evidence
  • Mismatched amounts, missing records and unmatched bank credits
  • A financial audit trail of every match and override
Reconciliation: bank statement feeds, the settlement trajectory, the authoritative recon ledger and an audit dossier with its checkpoints.

06 Money

Targets, incentives and payroll you can reproduce

Targets are set per bank and bucket. Each person sees what is achieved and what it means for their incentive, and the same month always produces the same pay.

  • Target progress and the daily run-rate for every bank
  • Incentive slabs configured per bank, counted only on bank-confirmed collections
  • A payout simulator that shows its inputs
  • An audit checklist and a period lock before the payroll run
Targets and incentives: agency target velocity, the recovery trajectory, commission slabs, the officer incentive ledger, an incentive simulator and the audit checklist before the payroll run.

07 People

Attendance and activity, fairly read

See who is present, who is in the field and who has gone quiet, without treating a gap in the data as proof that someone did nothing.

  • Live workforce status across telecallers and field staff
  • Attendance and shift start for every employee
  • A leave approval queue
  • No activity, low activity, blocked work, leave and system issues are told apart
Workforce attendance: live workforce counts, the daily attendance ledger, verification breakdown, an employee inspector and payroll readiness.

08 Control

Exceptions with a clock on them

Broken promises, undeposited cash, field exceptions and bank confirmations land in one feed, each with a severity, a deadline and the next step.

  • Severity and an SLA on every alert
  • The account, the people involved and the trail so far
  • Reassign, escalate, override with a reason, or dismiss
  • Every resolution recorded in the audit trail
Notification and triage: alert counts, an alert taxonomy, the live alert feed with actions, and one account’s dossier with its history.

More of the platform

And the parts that hold it together.

Roles

Each person sees their own work.

Access is scoped by role, bank, team and branch, on every screen and every search.

  • Owner

    Sees the whole agency. Sets up banks, campaigns, roles and targets, and authorizes the overrides nobody else can.

  • Manager

    Works within their own banks, teams or branch. Assigns cases, watches workload and promises, and handles escalations.

  • Back office

    Imports bank files, processes paid files and deposit receipts, and clears reconciliation exceptions.

  • Telecaller

    Sees only assigned cases. Calls, records the outcome, logs promises to pay and schedules follow-ups.

  • Field executive

    Accepts visits, records what happened at the address and reports any cash collected.

  • HR and payroll

    Looks after attendance, leave, salary and incentives. An optional role for agencies that want it separate.

For management

Answers without calling anyone.

The test for RecoveryOS: management can answer these without opening several Excel files or phoning the team.

Workforce

  • Who is present, and who is absent?
  • Who is working in the field?
  • Who has pending or overdue work?

Recovery

  • How many accounts are assigned and contacted?
  • How many promises to pay exist?
  • Which visits are pending, and what was escalated?

Collection

  • How much was collected, and how much is bank-confirmed?
  • What cash is waiting to be deposited?
  • What remains unreconciled?

Targets

  • What is the target, and what is achieved?
  • What remains this month?
  • Where does each bank and bucket stand?

Rules the system holds

Money and audit history are not negotiable.

These are designed in from the start, so a bank audit finds the same facts you see.

  • The bank confirms payments

    A payment is never marked bank-confirmed without the bank’s own paid file.

  • History is kept

    Promises to pay, calls, assignments and corrections are added to, never overwritten.

  • Imports are safe to retry

    Loading the same bank file or paid file twice does not create duplicates.

  • Pay can be recalculated

    Incentives and salaries are reproducible from the stored inputs and rules.

  • Access follows the role

    Each person sees and changes only the banks, teams and cases in their scope.

  • Chats are not evidence

    WhatsApp messages and phone updates are working notes, never the bank audit record.

AI

Automation first. AI after the data is reliable.

Plain rules do the routine work. AI assistance comes later, reads only what the person asking is allowed to see, and never changes a financial record by itself.

  • Rules before models

    Assignment, reminders and escalation run on rules you configure for each bank.

  • Assistance, not decisions

    AI summarises and suggests. It separates facts from inference and logs what it does.

  • A person approves

    Sensitive changes wait for someone with the authority to make them.

Reports: report catalogues, the daily report volume, the generated report ledger, a report inspector and an AI executive brief.

The reports screen with its AI executive brief, as designed. AI is the last phase of the build.

Roadmap

Built in six phases.

The core workflow comes first. Each later phase stands on data the earlier ones made reliable.

  1. Phase 1

    Core operations

    • Sign-in and access control
    • Banks and bank file import
    • Accounts and assignment
    • Calling, promises and follow-ups
    • Basic field work and collection
    • Management dashboard and audit
  2. Phase 2

    Workforce

    • Attendance and leave
    • Productivity
    • Employee dashboards
    • Field tracking
  3. Phase 3

    Financial operations

    • Paid files and cash deposits
    • Reconciliation
    • Targets and incentives
    • Payroll and month-end lock
  4. Phase 4

    Reporting and compliance

    • Bank, daily and management reports
    • Compliance checks
    • Exception management
  5. Phase 5

    Automation

    • Notifications
    • Follow-up and promise reminders
    • Assignment rules
    • Daily management briefing
  6. Phase 6

    AI

    • Management assistant
    • Follow-up and reconciliation agents
    • Compliance and reporting agents

Questions

What agencies ask first.

Does RecoveryOS replace the bank’s own systems?

No. The bank’s systems stay the authority. RecoveryOS runs the agency’s side of the work and never overrides a bank record with something an employee typed.

We work for several banks, each with a different file. Is that a problem?

That is the case it is designed for. File formats, buckets, statuses and incentive slabs are configuration for each bank and campaign, not something built into the software.

Can AI change a payment or a settlement?

No. Financial changes follow fixed rules, need the right authority and are audited. AI is planned to summarise, suggest and prepare work, and sensitive actions wait for a person to approve them.

What happens to our Excel sheets and WhatsApp groups?

The work they carry moves into one system. People can still message each other, but a chat message is a working note. It is never the record a bank audit relies on.

Can we use it today?

RecoveryOS runs as a private platform. It is not open for sign-up or trial. If you run a recovery agency, talk to us about how your agency works today.

Running a recovery agency?

RecoveryOS is a private platform. If this is the system you have been missing, tell us how your agency works today.

Talk to us