How the Kweli Load Exchange Works
A Step-by-Step Workflow That Turns Load Matching into Trust
Kweli is designed to make load matching feel natural, lightweight, and familiar — because it runs in the phone browser every operator already has, and it is WhatsApp-integrated — so a notification brings you straight back to the job.
There is nothing to download from an app store, no platform to learn, and no artificial friction.
Value is created through real participation and real outcomes.

Step 1: Sign Up and Join Corridors
Users join at lx.kweli.co.za, in a browser. A WhatsApp link takes you to the same place.
Nothing to download from an app store
No complicated registration
No upfront commitments
During onboarding a transporter adds a truck and the corridors that truck runs. The lanes sit on the vehicle, not on the company, so each truck in a fleet carries its own set and you can change them as the work moves. A shipper posts a load instead, and is never asked for a truck.
This ensures that all activity, visibility, and trust signals are route-relevant from day one.
Kweli is corridor-aware by design.
Once registered, operators can declare their vehicle types, preferred routes, and availability windows. Shippers describe the freight they need moved, including cargo type, pickup and delivery points, and timing requirements. This information is structured by corridor, so the operators most likely to want a load are the ones shown it first. It orders the board; it does not close it — you can still see work off your usual lanes, and you can still apply for it.
Step 2: Say What You Need First
Kweli does not ask you to pick a role. It asks one question — what do you want to do first?
I am looking for loads — find cargo for the trucks you run
I have loads to move — find trucks for your cargo
You get both sides either way. A transporter who also has cargo of his own does not need a second account, and a shipper who buys a truck does not start again.
Your record is kept per side. How you perform hauling is measured as a transporter; how you pay and load is measured as a shipper.
One side does not quietly lift or sink the other.
Step 3: Conduct Transactions on Kweli LX
Most daily load matching actions happen directly on Kweli LX:
Posting or responding to loads
Confirming availability
Updating execution status
When clarity, documentation, or structured input is required, Kweli uses Webcards — mobile-friendly web pages where the actual work happens. Every action lives on the webcard, not in a chat, which is what makes a step recordable rather than a message somebody has to remember.
Webcards are used for:
Load details and confirmations
Document submission
Structured workflows
Kweli LX is where the work happens.
Webcards handle complexity without disrupting flow.
Step 4: Track Behaviour and Outcomes
Kweli observes what actually happens — not what is claimed about load matching ability.
As users participate, execution data accumulates, including:
Confirmed vs cancelled loads
Timeliness and follow-through
Consistency of engagement
This is recorded in your performance record, kept separately by:
Role
Corridor
Time
Kweli does not judge intent.
It records outcomes.
This behavioural data is scoped by corridor and role, ensuring that an operator’s track record on the Durban–Harare route is assessed separately from their performance on other routes. The system captures completion rates, response times, and consistency patterns that would be invisible in traditional freight channels.
Step 5: Trust Emerges Over Time
Trust in Kweli load matching is not instant and not purchased.
Over time, Kweli surfaces:
Reliability patterns
Consistent execution behaviour
Corridor-specific performance signals
Visibility improves based on relevant execution history, not raw activity, popularity, or volume.
Trust is earned through consistency.
Participants who consistently follow through on commitments gain higher visibility within their corridors. This creates a self-reinforcing cycle where reliability is rewarded with better access to freight opportunities, encouraging all participants to maintain high standards of execution and communication throughout every corridor they serve.
The Flow, Simplified
Load Exchange → Webcards → Your Record → Trusted Execution
Every step reinforces the same principle:
Execution creates memory.
Memory creates trust.
Trust creates opportunity.
The load matching process is designed for operators, shippers, and brokers who work across SADC corridors including Durban–Harare, Johannesburg–Lusaka, and Beira. Unlike traditional load boards, Kweli runs on the phones that are already the dominant communication tool in Southern African freight markets.
Each load matching interaction is recorded, building a comprehensive picture of reliability over time. This approach ensures that the best operators become visible based on actual performance rather than paid advertising or social connections or paid placement. Learn more about what Kweli is and explore Kweli features to see what the platform offers.
Getting started with Kweli is free. You sign in with the WhatsApp number you already use, tell us what you drive and the roads you run, and you come out with your trucks and their lanes on the board. There are no registration fees, no commissions on loads, and no hidden charges. The platform earns value from the trust data it creates, not from extracting fees from operators or shippers who already work on thin margins.
Kweli Load Exchange
Now find a load for your truck — or a truck for your load
Free for transporters and shippers. No commission, no subscription.
Local
and cross-border
See
who you are dealing with
R0
commission, always
List your truck and its corridors, or post a load. Your corridors decide which loads we show you first — they do not lock you out of the rest. Body, weight, fit, papers: we show them, and you decide.
WhatsApp-integrated · your number is your account. Nothing from an app store — you finish with your trucks and their corridors on the board.
New to Kweli? See what the network does → — load exchange, driver registry and the Pulse community.
