WhatsApp vs TMS: What Dispatching on WhatsApp Costs

It’s 6:45 on a Monday. Twenty unread WhatsApp groups. One driver asking which load to pick up first. Another has sent a photo of a delivery note, and you’re not sure which order it belongs to. A client has called twice already asking where their delivery is. You open the spreadsheet; the last update was Friday. By the time the morning is straightened out, two orders have been double-booked and an invoice is a week late.

Nobody chooses this on purpose. WhatsApp and a spreadsheet are free, familiar, and need no training, which is exactly why almost every small transport operator starts there. The problem isn’t the choice you made when you had three trucks. It’s that the same setup keeps running once you have fifteen, and it wasn’t built to hold that much.

Where the Cost Actually Shows Up

None of this appears as a line item on your income statement, which is exactly why it’s easy to underestimate.

Orders get missed or duplicated. A request lands in a group chat, someone reads it and forgets to assign it, or two people book the same truck against it. Every missed or duplicated order is either lost revenue or an apology to a client.

Invoicing lags and errors creep in. When trip details live in chat threads and a spreadsheet, someone has to manually copy delivery data into an invoice, often days after the fact. Wrong quantities, wrong rates, and late submission all follow from that gap, and every day an invoice sits unsent is a day it isn’t earning you anything.

You can’t see what a route actually costs. Answering “what did that Durban run cost us, all in?” means digging through chats and cells rather than reading a number. Without cost-per-trip visibility, underperforming routes and unprofitable clients stay invisible until the damage is already done.

Compliance data is scattered. RTMS-relevant records, driver hours, vehicle checks, maintenance history, sit across WhatsApp photos and random folders instead of one place. There’s no single audit trail, which is a problem the day an auditor or a weighbridge stop asks you to produce one. Overloading enforcement itself carries real cost too; see the full axle limit and penalty picture for what’s actually confirmed versus commonly repeated online.

Disputes turn into “he said, she said.” A photo in a WhatsApp thread isn’t linked to a specific order, time, or signature. Without that link, a delivery dispute comes down to whoever argues harder, not what actually happened.

Fuel usage is a black box. At current wholesale diesel prices of roughly R25 a litre, even small unauthorised detours or idling add up over a month. Without trip and kilometre data tied together in one system, an unusual pattern has nowhere to surface.

“Where is my delivery” eats staff time. Every one of those calls means someone stops what they’re doing to chase a driver or check a group. It’s a small tax that compounds across a full day of calls.

We don’t have a verified, audited figure for what this adds up to across the SA operator base as a whole, and any specific percentage or Rand total you see quoted for “typical revenue leakage” (including in an earlier version of this page) should be treated as illustrative, not measured. What’s consistent, from the failure modes above, is that the cost scales with order volume, not truck count, which is why it sneaks up on growing fleets specifically.

Side by Side

Area	WhatsApp + spreadsheets	TMS
Order management	Orders in group chats; easy to miss or duplicate	Every order is a record, assigned and visible
Dispatch	Manual messages and calls	One dashboard, one view for the whole day
Tracking	”Where’s the truck?” = a phone call	Live tracking, often with telematics integration
Proof of delivery	Photos in chat, not linked to an order	Tied to the job: time, signature, photo
Invoicing	Manual entry from notes; delay-prone	Generated from the completed trip
Compliance	Scattered; audit prep is a scramble	Centralised, ready to produce on request

The Objections, Answered Honestly

“My drivers can’t use technology.” Most already use WhatsApp daily. A driver-facing TMS app built around a simple job list and a photo-capture button is usually a smaller leap than it sounds, and often easier than hunting through group chats for the right delivery note.

“It’s too expensive.” Thwala starts at R2,999 a month. Weigh that against the cost of one lost load or one client you lose over a billing dispute, and the maths for most small fleets isn’t close.

“We’re too small.” There’s no hard truck-count threshold here, but once a single dispatcher can no longer hold every job in their head without a group chat as backup, you’ve already crossed the point where a dedicated system starts paying for itself.

“Switching will be disruptive.” A reasonable rollout runs in parallel with what you’re already doing: import your trucks, drivers, and clients, pilot on a few routes, then expand. Nobody has to flip a switch on a Monday morning and hope.

Signs You’ve Outgrown WhatsApp Dispatch

• Orders are sometimes missed or double-booked because they only ever lived in a group chat.
• Invoicing regularly waits on someone manually updating a spreadsheet first.
• You can’t say what a specific route or client cost you last month without digging.
• Compliance documentation is scattered, and preparing for an audit feels like a scramble.
• You can’t prove what was delivered, when, or by whom, without hunting through chats.
• “Where is my delivery” turns into two or three phone calls instead of one quick answer.

Ticking several of these doesn’t mean you did anything wrong. It means the operation has outgrown the tools it started with, which is a normal and predictable place to land.

Thwala is transport management software built for South African conditions: it works through load-shedding and patchy connectivity, integrates with the tracking you already use, and keeps orders, dispatch, proof of delivery, and invoicing in one place. For the fuller picture of what a TMS covers, see what is a TMS. See how Thwala fits your fleet.

Frequently Asked Questions

Is WhatsApp good enough for fleet dispatch?

It works for casual communication, but it was never built for dispatch. Orders get lost in groups, messages aren’t linked to specific jobs, and there’s no audit trail for compliance or disputes. Past a handful of trucks, that gap starts costing real money.

How much does a TMS cost for a small fleet in South Africa?

Thwala starts at R2,999 a month. Pricing across the market varies by provider and feature set, but for most fleets the cost of one avoided billing error or lost load covers a meaningful chunk of a month’s subscription.

Can drivers used to WhatsApp adjust to a TMS app?

Generally yes. A well-built driver app is a simple job list with a tap-to-capture delivery flow, which most drivers find faster than searching a group chat for the right delivery note once they’re used to it.

At what point does a fleet need to move off WhatsApp and spreadsheets?

There’s no fixed truck count. The signal is whether one dispatcher can still reliably hold every order and trip in their head. Once orders start getting missed, duplicated, or invoiced late on a regular basis, the operation has already outgrown the tools.