Platform / Field operations
Field visits that end as data, not diary entries
The FOS app puts the day's allocations, directions and scripts on the officer's phone, works without signal, and returns geo-tagged visit records the flow can act on.
How it runs
Field operations end to end
The same shape on every account: the flow acts, the world answers, the account is written. Nothing depends on someone remembering.
- 1AllocateCases go out by beat, capacity and the strategy that put them there.
- 2PlanThe officer opens the day's list with addresses, history and the script for each visit.
- 3VisitCaptured on the doorstep, offline if the network is not there.
- 4EvidenceLocation, time and outcome recorded together, so the record stands up in a dispute.
- 5SyncThe disposition reaches the flow the moment the phone finds a signal.
Visited, paid, promised, not found, wrong address: each is a branch the flow already knows.
What it does
The working parts
Each part is a real record in the platform, not a feature on a slide. 5 of them make up field operations.
Allocation on the phone
Each officer sees their accounts, addresses and history. Supervisors see coverage and outcomes.
Offline first
Visits, PTPs and receipts are captured without network and sync when signal returns. Field work does not wait for 4G.
Geo-tagged evidence
Every visit carries location, time and the captured outcome - evidence that stands up in a dispute.
The flow reacts
A completed visit is a signal like any other: the flow branches on visited, paid, promised, or not found.
The FOS App by ATTPRO
Android and iOS from one codebase, distributed privately to your officers. The whole day on one phone, with or without signal - see the app page for the officer's view.
- Offline
- Geo-tagged
- Numbered
Field work does not wait for 4G.
Location and timestamp on the record, not on a claim.
Field payments post like any other payment.
Controls and outputs
What you set, and what you get back
Every control is a setting in the admin app with an audit trail; every output is a record on the borrower, not a spreadsheet.
Settings are per tenant and per campaign, and every change is attributable. Outputs are written as the work happens, not assembled afterwards.
Part of one system
Field operations does not work alone
The signals it produces are read by the rest of the platform the same second. These two are the closest neighbours.
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 before publish, and...
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 paymentsQuestions
Before a pilot on field operations
The questions a collections head or an infosec team asks first. Anything else, an engineer answers on the demo call.
Which phones does the FOS app run on?
Android and iOS from one codebase, distributed privately to your officers. It is built for the budget Android phones a field team actually carries.
How are officers and beats managed?
Beat planning and allocation rules sit in the admin app; supervisors see coverage, outcomes and productivity per officer, and can re-route a beat during the day.
Can receipts be trusted?
Receipt numbering is controlled by the platform, every receipt carries the officer, the location and the time, and the amount reconciles against the payment rail the same day.
Further reading
Notes that go deeper
Written for practitioners, ungated, and specific to Indian lending.
Alternate MetaData in India: when to spend, and what to expect back
Tracing is bought as a magic answer to unreachable accounts and usually delivers a partial one. Used with a rule about when to trigger it, it is one of the better rupees a collections operation spends.
ReadDPD buckets, and why each one needs a different conversation
Days past due is the oldest number in collections and the most casually used. The buckets are not a reporting convention. They are four different problems that happen to share a book.
ReadBring 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.