Capturing a visit with GPS and promise-to-pay
Without a verifiable record, an institution cannot confirm an agent actually reached a borrower — and a verbal promise to pay gives collections nothing to act on. The Ustawi app captures both: a GPS location and timestamp at the visit, and a structured promise to pay when the borrower cannot settle in full.
The two accountability gaps this closes
First, without a verifiable visit record, a lender simply cannot confirm that an agent reached a given borrower. Second, an unrecorded verbal promise — “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 moments into hard data.
How visit capture works
- 1Open the borrowerFrom the worklist, at the point of visit.
- 2Capture the locationThe device's own GPS records latitude, longitude and a timestamp against the visit — typically accurate to around 10 metres in the open. No third-party mapping provider is required for the capture itself.
- 3Record the outcomePaid, promise to pay, or no contact.
- 4Log the promise to payWhen the borrower cannot pay in full, capture an amount and a committed date as a structured record, not a free-text note.
Why this feeds delinquency management
A logged promise to pay becomes a structured input the dunning ladder can act on. If the committed date passes unpaid, the broken promise is flagged automatically. This linkage into the Collections & Delinquency app is real product architecture: the field visit is not a dead-end note, it drives the next collections action.
The field agent app is in active development; GPS capture and promise-to-pay logging are described here as intended, grounded capabilities of the offline-first design.