09:14 on a Thursday morning at a nine-person freight forwarder off Second Avenue in Boston, Bellville. Two clients on hold. One has a forty-foot from Ningbo sitting at Cape Town's Duncan Dock, stopped for a SARS query about the tariff heading on a stainless-steel kettle line. The other has a SAHPRA import permit for a small air-freight consignment landing at OR Tambo tomorrow morning — the permit expired at midnight, nobody phoned him, and the consignee is a Sandton clinic that has already invoiced the patient. Three consols are out for delivery. The operations manager is on WhatsApp with a Maersk local rep about a discharge slot. The two junior entry clerks are chasing a house bill of lading from an origin agent in Shanghai and rekeying a commercial invoice into CargoWise for tomorrow's SAD500 submissions. The MD is on Teams to a Piet Retief manufacturer who has been asking for the same duty-and-VAT breakdown three times this month because he keeps losing the email.
Anyone who has run a small SA freight forwarder recognises this Thursday. The clients are not being difficult — they want to know where their container is, what it will cost by the time it clears, and whether their production line stops next week. The port does not cooperate. Cape Town has been congested since March. Durban has its own problems. The origin agent in Shanghai is nine hours ahead and sends documents at 04:00 SAST if he sends them at all.
Freight forwarding is a paper business dressed up as a logistics business. The margin lives in your disbursement notes, not your handling fee, and most of the operational week goes on making sure the right document arrives from the right party at the right stage of a fifteen-step lifecycle. Some of that work is judgement. Most of it is chasing, formatting, translating, re-sending.
AI cannot cut a SARS release for you. It cannot argue with an examining officer at Durban Container Terminal about a tariff heading. What it can do is take the mechanical layer — the tracking updates, the document-chasing, the first draft of a client message — off the clerks so they spend their hours on the shipments where the money actually lives.
Where a freight-forwarding week actually goes
Not on the physical shipment. The shipment moves itself, mostly. The hours live in a narrow set of tasks around it.
- Tracking questions. "Where is my container." "Has it discharged." "When will it clear." A mid-sized forwarder fields two to four of those per open shipment per week. On a book of eighty open shipments, that is two hundred phone calls a clerk answers instead of processing entries.
- Document chasing. Bills of lading, commercial invoices, packing lists, certificates of origin, phytosanitary certificates, health certificates. Every one of them needed at a specific stage, from a specific party, in a specific format. Ninety percent arrive on time. The other ten percent devour the week.
- Duty-and-VAT quotes. A manufacturer in Piet Retief who imports two containers a quarter is not going to build a landed-cost model. He wants a WhatsApp saying "R48,720 duty, R76,340 VAT, R14,200 clearing and disbursements, R139,260 total, please transfer before Friday to release."
- Permit chasing. ITAC permits for regulated goods, SAHPRA for pharma, DALRRD for agri, department-of-mineral-resources for anything scheduled. Expiries, extensions, amendments.
- Post-clearance admin. Delivery orders, PODs from the transporter, disbursement statements to the client, storage-and-demurrage tracking on port charges the client would rather not pay.
None of that is skilled clearing work. All of it is where the office actually spends its time.
Tracking that ends the phone call
The most common leak at a small SA forwarder is the "where is my container" call. It takes ninety seconds and it happens seven times a day per operations person. That is over an hour of skilled staff time gone on a question that has one answer, which the client could have read for himself if the answer were in a place he was willing to look.
The fix is not a client portal. Clients do not log in. The fix is a WhatsApp update pushed the moment the shipment state changes, in the client's own words. Vessel departed Ningbo, ETA Cape Town 14 September. Container discharged at CTCT, awaiting clearance. SARS release received, awaiting transporter dispatch. Delivered, POD attached, invoice to follow.
The state changes come from your operating system — CargoWise, Descartes, whatever you run — and the AI layer wraps each event in the language your client actually uses. Not "MSC OSCAR VSL v2437W berthed 12 Sep 04:22 SAST at Berth 601 QC-11". A sentence. If the client replies with a question, the AI drafts a short answer against the shipment file and the clerk approves it before it goes.
Two things matter here in my experience. Clients want the update pushed to them, not pulled by them. And the clerk staying in the loop for anything past a factual state change is what stops a bot promising a delivery slot it cannot keep.
Documents: the ten percent that eats the week
The document cycle is what a forwarder actually sells. It is also where AI earns the most quiet time back.
An origin agent in Shanghai emails a scanned commercial invoice. The clerk opens it, checks the values, keys the line items into CargoWise, cross-checks against the packing list and the bill of lading, flags any mismatches, and files it against the shipment. Twelve minutes per entry at best. A well-scoped AI reader takes the same email, extracts the header data and every line item, matches it against the packing list, and pre-populates the CargoWise entry. The clerk reviews and corrects rather than typing from scratch. Three minutes per entry, at a reasonable accuracy floor.
The compounding effect is where this pays. Two hundred entries a month at nine minutes saved each is thirty hours back on a single clerk's desk — hours that pay for the tool many times over and free the clerk to work on shipments where a human eye is genuinely needed.
The chasing layer sits behind it. When a document is outstanding at a stage where it blocks the next action — a house B/L not yet released, a certificate of origin missing before entry can be lodged — the system drafts the follow-up to the origin agent, tuned to that agent's usual response pattern (Shanghai will reply to a short, specific WhatsApp before an email), and the clerk sends it. No follow-up gets missed because no follow-up depends on a human remembering to check.
SARS, SAD500 and the line the bot does not cross
The place where AI has no business at a South African forwarder is the customs declaration itself. A SAD500 is a legal document lodged in your name against a Customs client number, and the entry clerk who signed the training exam is the person who must sign the entry. Full stop.
The framing that works in practice is a draft-and-sign flow. AI prepares a draft entry from the commercial invoice, packing list, bill of lading and any permits, populates the tariff heading it believes applies based on the description, flags every field where the source documents are ambiguous, and hands the draft to the entry clerk. The clerk verifies, corrects, and lodges. The bot never touches EDI. The clerk's judgement stays on the tariff heading, the valuation method and the permit checks. What the bot removes is the twenty minutes of rekeying and the missed cross-reference between the invoice and the packing list.
Most consultancies will tell you AI can auto-classify tariff headings. In practice, the accuracy on complex or unfamiliar goods is not good enough to sign an entry against — and if SARS challenges a heading, your clerk is the one signing the affidavit. Use AI to propose a heading. Never to decide one.
Client comms in the forwarder's own voice
Freight forwarding is a relationship business. The Piet Retief manufacturer stays with you because you phone him back on a Saturday when a container is stuck at the port, not because you have the cheapest sea freight rate. Anything that automates comms in a way that erodes that relationship is a net loss, however much time it saves.
The version that works is voice-preserving. AI drafts, the operations person edits, the client sees the operations person's usual tone. Duty-and-VAT quotes go out with a personal line at the top and the breakdown below. Weekly shipment summaries land on Sunday evening in the same rhythm the MD has been sending them for six years. The bot never sends anything the client would recognise as a bot.
The exception, again, is the factual state-change push. That one is welcomed as informative and not read as impersonal, because it is not a substitute for the phone call — it is the reason the phone call is no longer needed.
Where a bot has no place here
A short list.
Rate quoting. Freight rates are relationship pricing, negotiated per client per lane per season. A bot quoting a rate without a human is a bot losing you margin or losing you the client, depending on which way it errs.
Disbursement disputes. When a client argues that a demurrage charge should not be on their disbursement note, the operations manager takes the call. The bot pulling storage-and-demurrage from the port statement is fine; the bot arguing about whether the client should pay it is not.
Anything with SARS, DALRRD, SAHPRA or ITAC on the other end of the line. Regulatory conversations are had between named humans on both sides. A bot in that loop invites a mistake nobody wants on their file.
Where to start
The temptation with a forwarder is to buy a platform that does everything. The forwarders that get value from AI do the opposite. Pick the single loop costing you the most clerk-hours, wire it in properly, and let it run for a month before adding the next.
For most nine-to-fifteen-person SA forwarders, that loop is the tracking-and-comms push — the pushed WhatsApp state changes and the drafted replies. It is the highest-volume interruption in the office, it plugs directly into the operating system you already run, and it does not touch the customs declaration.
Once that runs quietly, the document-reader layer for commercial invoices and packing lists earns its place next, because the accuracy floor on standard shipping documents is high enough for a review-and-approve workflow to be a genuine time-saver. The SAD500 drafting layer comes after that, and only for goods your clerks handle every week — a first draft on unfamiliar cargo helps nobody.
Small SA freight forwarders that build the tracking layer first report the same shift. The phone stops ringing with "where is it" calls. The clerks recover an hour and a half a day between them. And the MD, at 09:14 on a Thursday, is on the Teams call to Piet Retief about a duty-and-VAT quote he can actually send now — not fighting three fires at once.