Routing field agents by signal, not guesswork.
- Year
- 2023
- Role
- Backend architecture, streaming pipeline
- Timeline
- 2023 · Ippopay
- Stack
- Google Maps, Redis
The system
Overview
A field intelligence platform for collections teams: live location events, geo-fenced zones, and behavioural data fused into routing that tells every agent where to go next, and gives managers a live map instead of an end-of-day spreadsheet.
problem
The problem
Field agents covered loan-collection beats on intuition. Routes overlapped, high-value visits were missed, and managers had no live view of coverage: the source of truth was a spreadsheet reconciled after the day was already over.
strategy
Strategy
Treat the field as a stream. Every location ping, geo-fence crossing, and visit outcome becomes an event that updates the routing picture, so the day's plan can adapt while the day is still happening.
development
Development
WebSocket ingestion feeds Redis streams; a geo-fence engine evaluates zone crossings in real time; a routing layer scores each candidate visit by distance, payment history, and time windows before it reaches the agent's app.
- 100K+ location events a day, sustained
- In-memory geo-fence evaluation on Redis
- Visit scoring from behavioural data
- Live coverage dashboard for beat managers
results
Results
Travel time per completed visit fell 35%. Managers moved from end-of-day reconciliation to live course-correction, and coverage stopped depending on who knew the neighbourhood best.
Key takeaways
Routing is a data problem before it is an algorithm problem.
Make the field visible first; optimisation is easy once you can see.
Streams beat batch when the decision window is measured in hours.