Sales Force Automation Cloud Software Built for Egypt's Logistics and Field Service Teams

A single app covers the account handlers chasing B2B freight and 3PL contracts, the last-mile riders working delivery runs, the field service engineers closing job tickets, cold-chain crews, and the key account managers overseeing enterprise clients. Rather than one generic screen, each role opens to a layout built for its own job, its own KPIs and its own dashboard, keeping a coordinator in Cairo and an engineer near Port Said from ever looking at the same view.

A depot or sortation-point geofence paired with a selfie match confirms who has actually clocked in, not just who claims to have. Engineers instead check in against their first job of the day, and riders against the depot before setting off. Where the connection is weak, inside a warehouse, a container yard, or a stretch of patchy connectivity through Upper Egypt or the Delta, the check-in still records locally with its timestamp, position and selfie, then uploads once signal returns. A late clock-in or a selfie that does not match gets flagged for the supervisor straight away.

The lead goes into the app carrying the account's expected volume, its route mix and the SLA tier under discussion. Pricing can be built from slab rates, a fuel-cost adjustment and EGP figures, and none of it goes live until a commercial manager signs off. From there the contract moves into the CRM automatically, with a reminder set well before renewal, timed to fit around Egypt's ETA e-invoicing cycle.

A ticket is tagged with the skill it needs, the parts it is likely to require and an SLA clock. Assignment weighs certification, who is already stretched thin and who is physically closest, whether that means a technician working Greater Cairo, Alexandria or a satellite hub like 6th of October City. Closing the ticket means logging what was found, what was swapped out, photos of the job before and after the work, and a signature from the customer, captured in either Arabic or English.

There is. Bringing on a sub-contractor or a last-mile rider works through a set workflow: registration and tax paperwork, vehicle documents, consent handled in line with the PDPL, and a payout method chosen from InstaPay, Fawry, Meeza or a bank account, followed by contract sign-off and adding the crew to the system. A coordinator can see exactly where each new partner sits in that process from a single screen, rather than tracking it by hand.

Coverage is mapped against the Suez Canal corridor and the ports that feed it, Alexandria, Damietta and Port Said, then inland through Cairo, Giza and satellite zones such as Obour City and New Cairo. Formal addresses run out fast on many industrial-zone streets, so the system pins stops by landmark and GPS coordinate instead. A geofenced check confirms the visit really happened, and a coverage score catches whatever got skipped so it lands on the following shift.

They can. In-house drivers, contracted engineers, gig motorcycle riders, franchise operators and 3PL businesses all work from the same backend, but each sees only its own people through screens kept separate by role. What rolls up across the whole network, without any partner seeing another's numbers, is SLA performance, first-attempt delivery rates and payout exposure.

A claim goes in for fuel, tolls, parking or an unplanned out-of-hours callout, valued in EGP. The system reads whatever proof comes with it, an InstaPay or Fawry confirmation, a bank-transfer notice or a paper receipt, pulling the merchant, the amount and the date automatically, and GPS mileage can back a per-kilometre top-up where that applies. From there it moves through the hub lead, the operations manager and finance before it is paid out.

A hub lead's screen stays close to the day: who is present, how jobs are progressing, what is at risk of breaching SLA and what exceptions need attention right now. An operations manager works a level up, looking at on-time performance by corridor, first-time-fix and first-attempt delivery rates, how productive each rep has been, and how every partner is scoring. Either one can ask 1Voice AI something like which hub is falling behind this week and get an answer without waiting on a report to be built.

No. The app is built to keep working with zero connection, inside a warehouse, a container yard, or out on a delivery run through parts of Upper Egypt or the Delta with no coverage at all. Riders and engineers can still log who's on shift, confirm a delivery with a photo, note any cash taken and write up a service report, all held on the device until a connection comes back, at which point it uploads on its own. Nothing recorded offline gets lost in the gap.