The field service platform, set up again for a sales force.
At an electronic payments company in Egypt, each sales representative looks after a set of merchants and their payment terminals. In 2024 we gave the company its own installation of the field service platform we had built for another payment company. Then we reshaped it around a sales team: every merchant has its representative, its targets and its visits.

From a service team to a sales force.
The first company's version sends each job to whichever agent in the zone has room for it. This company works differently: every merchant belongs to one sales representative, and supervisors and managers sit above them in layers.
We kept the tickets, the zones and the app, and built the rest around that structure.
What we added for this company:
- Its own installationA separate copy of the platform with the company's name, colours and data.
- Hierarchy from one fileOne spreadsheet loads the managers, supervisors, representatives, merchants and terminals.
- Each merchant's own representativeA ticket goes straight to the representative who owns that merchant, not to a pool.
- Merchant ticketsA ticket can be about the merchant, such as a visit, and not only about a device.
- TargetsTargets are uploaded from Excel, and each merchant's achievement is shown to its representative.
- New merchantsA representative proposes a new merchant from the app, and the office approves or rejects it.
- A team's own viewEach manager sees the representatives under them and those representatives' merchants.
- A new appRebuilt in 2025 with the representative's tickets, merchants, targets and performance in one place.
- Laravel
- PostgreSQL
- PostGIS
- Kotlin Multiplatform
- Firebase
