How a South African fleet operator took WhatsApp out of fleet maintenance for good

Our client is a large South African road freight and logistics operator, running a fleet of more than a thousand trucks across South Africa and cross-border into neighbouring countries. The Lancea team supports the division responsible for maintaining that fleet.

The challenge

Before the current system existed, the operator ran a core part of its operation, the coordination of breakdowns, services and accidents across its entire fleet, on WhatsApp. What had started as a convenience had become the operations system by default: an operational process running on WhatsApp at a volume no one could reliably track, carrying the coordination of more than a thousand trucks operating across the country.

At that volume, the real constraint was human attention. Getting the right information in front of the right person, at the right time, inside an ordinary stream of messages, was a standing operational risk, because a general-purpose messaging app was never built to carry it.

Alongside WhatsApp, the parts of the process that did run through dedicated systems were disconnected from each other. Information had to be relayed by hand between the people involved. There was no single, shared record of what had happened on any given event. And none of it reached the underlying SYSPRO ERP without someone manually re-entering it on the other side.

Compounding the challenge, no standard maintenance or ERP product on the market carried the concepts this domain actually needed. A breakdown call, and the individual pieces of work inside it, did not map cleanly onto anything a standard system already had a name for.

The solution

The Lancea team replaced that landscape with two connected parts. The first is a purpose-built mobile application, developed specifically for this client so that it connects the people in the field to their SYSPRO data using their phones. It is built around one central concept: a call. Every breakdown, service or accident is logged as a call the moment it happens, and from that point it is assigned, progressed and closed inside the same system, on the device each person already has in hand, rather than being relayed by message between people. A controller sees the fleets that are theirs to manage. A technician sees the tasks assigned to them. No one needs a second channel to find out what is going on, or has to be the one who remembers to pass it on.

The second is Tempo Connect: more than 30 Tempo Action Dashboards, used on PC screens by the teams running the back office, also connected to SYSPRO to form one fully tailored solution built for this operator. The call centre function, service and booking management, risk administration, master data and management reporting all run through these dashboards, each a sizeable piece of functionality in its own right, operating as part of one coherent system rather than as separate tools bolted together. Management uses them to see the fleet-wide picture. The dashboards are built on TRX, Lancea's low-code configurable technology. TRX let the team prove the call and work item concepts against the client's real requirements before committing to a full build, and once those concepts held up, the same technology carried them through to production. Low-code technology is rarely expected to carry a system this size into production. Here it did, giving the client a fully tailored enterprise solution at a pace, and with a degree of validation along the way, that a conventional multi-year build could not have matched.

Sitting across the whole system is an event and escalation engine, purpose-built for this environment, that watches business rules and raises what needs attention on its own. A call that has sat too long in a queue, a service that has run past its expected window, an event still waiting on action after the point it should have moved forward: each surfaces automatically, as a notification to the person responsible, rather than depending on someone happening to notice it. Staff no longer have to watch their screens for something to go wrong.

In total, seven systems (the mobile application, Tempo Connect and its Action Dashboards, the warehouse and parts system, an integration layer to the client's operational logistics system, Power BI and Fabric reporting, the escalation engine, and the underlying SYSPRO ERP) operate as one integrated landscape. An event logged in the field flows through to the ERP without anyone re-capturing it by hand on the other side, so the operational record and the financial one move together instead of needing to be reconciled after the fact.

The results

WhatsApp has been eliminated from the operation entirely. An operational process that once ran on it at that scale no longer touches it at all, and the attention problem that came with that volume has gone with it. The whole process moved off a consumer messaging platform and into a purpose-built system, in full.

In its place is one integrated system carrying a single record of events, rather than a scatter of disconnected tools and manual handoffs. Every event a fleet has been through since the system went live is available in full, from a single place, to the person who needs to see it.

The system is fully integrated with SYSPRO end to end, operationally and financially.

Information now reaches the right person by design. Role-based visibility and rule-driven notification mean nobody has to notice the right message in the right place at the right time; the system already knows who needs to know, and tells them. Escalation happens by exception, so following up no longer depends on someone remembering.

The solution was delivered in phases, moving from an interim SYSPRO implementation through a first production release and a second phase covering services, risk and reporting, and it continues to extend today. Across the life of the engagement, a substantial part of the Lancea team, more than twenty people at various points, has worked on some part of this system.

Closing

What this operator has now is a live example of what happens when an operation stops working around the limits of a general-purpose tool and gets a system built for exactly what it needs to do. The scale of the change is easy to state: a core operational process used to run on WhatsApp, and it does not any more.