GPS-verified visits and recorded promises to pay.
Without a verifiable record, an institution can't confirm an agent actually reached a borrower — and a verbal promise to pay gives collections nothing to act on. The Ustawi app captures both: location and timestamp at the visit, and a structured promise to pay when the borrower can't settle in full.
The accountability problem this solves
Two accountability gaps hurt field collections. First, without a verifiable visit record, a lender simply cannot confirm that an agent reached a given borrower. Second, an unrecorded verbal promise to pay — 'I'll bring it Friday' — gives the collections team nothing structured to follow up on.
Capturing a GPS location with a timestamp, and a structured promise-to-pay, turns both of those soft, unverifiable moments into hard data.
How visit capture works
At the point of visit the app captures the coordinates and a timestamp alongside the borrower record. When the borrower can't pay in full, the agent logs a promise to pay — an amount and a committed date — as a structured record, not a free-text note.
Capture uses the device's own GPS to record latitude, longitude and a timestamp against the visit, with a typical accuracy of around 10 metres in the open; no third-party mapping provider is required for the capture itself.
Why this feeds delinquency management
A logged promise to pay becomes a structured input the dunning ladder can act on — for example, flagging a broken promise automatically when the committed date passes unpaid. This linkage into the Collections & Delinquency app is confirmed, real product architecture: the field visit is not a dead-end note, it drives the next collections action.
Visit & PTP flow
- 1Arrive at borrowerOpen the borrower from the worklist.
- 2Capture locationCoordinates + timestamp recorded with the visit.
- 3Record outcomePaid, promise to pay, or no contact.
- 4Log PTPAmount + committed date captured as structured data.
- 5Feed dunning ladderA broken promise flags automatically if the date passes unpaid.
Step by step
Related features
- Offline Cash CollectionRecord a collection with zero connectivity; idempotency-key-safe sync when it returns.
- Digital Receipts & SyncEvery collection gets a receipt, online or offline, finalized on sync.
- EOD Cash ReconciliationPhysical cash reconciled against the digital collection log at close of day.
- Device Security & EnrolmentA phone must be enrolled and trusted before it can transact.
- Worklist & RoutesThe agent's daily list of borrowers/installments due, synced from /sync/bootstrap.
See the field agent app in a live walkthrough.
FAQ
What does a visit capture?
The borrower's location as GPS coordinates plus a timestamp, recorded against the visit — turning an otherwise unverifiable field call into a hard record.
What is a promise to pay (PTP)?
A structured record of an amount the borrower commits to pay and the date they commit to — not a free-text note — logged when they can't settle in full at the visit.
How does a promise to pay affect collections?
It becomes a structured input to the dunning ladder in the Collections & Delinquency app; if the committed date passes unpaid, the broken promise is flagged automatically.
Which mapping provider or accuracy radius does it use?
Capture uses the device's own GPS to record coordinates plus a timestamp, with a typical accuracy of around 10 metres in the open; no third-party mapping provider is required for the capture itself.
Which phones or operating systems does the app run on?
The field app is available on Android; an iOS version is planned.