Friendly South African courier
Dispatch notes
We build short, practical reason codes so your customers understand handovers and returns. Avoid confusion, protect your week, and handle setbacks with fairness.
Short returns language that feels fair. Reason codes customers accept is the note we wish courier businesses had before the week turned loud.
Pair this update with Hello Return. Operated by Astros Marketing (Pty) Ltd, Sunnyrock 1401.
Reason codes are short, standard phrases you add to your courier notes or returns slips to explain why a delivery or collection could not happen. Instead of spinning lengthy stories, you get straight to the cause: gate closed, recipient unavailable, incorrect parcel, or site power out. Our checklists back these up so that everyone understands the reason, right from the workshop or storeroom to the customer doorstep, across hubs from Germiston to Durban.
Most days, these codes save time for small teams that cannot afford to triple-check every message or risk losing track of where a bag went. The aim is not to defend every outcome, but to set a language your customer will accept and your operator can use without rewriting it each trip. This helps keep your returns process fair, your team calm, and your follow-ups simple.
Reason codes work well for growing teams delivering under twenty bags a day, especially where responsibilities overlap across shifts or product types. If your ops lead is still the backup for every role, or your systems are a patchwork of chat, folders, and printed slips, this approach makes sense. SME manufacturers, field service teams, medical couriers, and independent retailers across Gauteng, Cape Town, and coastal cities use them weekly.
They are less useful if your customers expect long written explanations, demand a signature for every outcome, or you are running high-value shipments with insurer or compliance paperwork that mandates extra detail. In those cases, reason codes still help as a first step, but you may need to attach a fuller note. For single-bay shops or solo traders who see every handover in person, these codes can feel like extra admin.
On most South African floors, the process is practical and tied to real conditions. When a driver attempts a delivery and something blocks it, the driver writes the code on the job slip or ticks it on a printed lane card. If the address is inside a gated estate, and the guard refuses entry over a missing access code, 'No estate access - code not supplied' is recorded. A quick photo of the filled-out card can be sent to the ops lead or dropped straight into the customer group chat.
This note protects both the customer relationship and the operator’s sanity when the week gets noisy, especially during load-shedding, school holidays, or weather delays on the Highveld. The main benefits are reducing arguments, keeping a clean record, and letting the next shift pick up where you left off. Save time for your ops lead and avoid confusion when the next parcel is packed.
Suppose your Gauteng workshop ships components to a fabrication site in Midrand. The driver arrives at the industrial park, but the security station will not allow entry because the customer’s contact person has not left their name with the front gate.
Instead of a dozen phone calls, the driver marks 'Site access denied - customer contact not at gate' and takes a photo of the log card. This image is sent to the ops lead and the customer. Everyone knows the next step: the customer needs to update the gate list, and the trip is rebooked as soon as the all-clear arrives. The handover is documented, nobody is left guessing, and the team’s rhythm continues with minimal disruption. You can see similar practices on other rhythms and lane cards drivers actually use.
To make reason codes work for your team, pull together a few essentials before you use our contact form: a clear list of the scenarios that block your typical week, and the wording on your current handover slips. It also helps to share your busiest lane or delivery corridor - for example, Durban to Pietermaritzburg, or multiple stops across Bloemfontein.
If you have tried codes before, mention which ones got pushback from customers or where confusion still happens. Being concrete about your actual routes, handover times, and common estate, mall, or campus problems makes it far easier for our team to tailor the codes for you.
The main traps with reason codes are over-complicating the list and leaving explanations too vague. If you use twenty codes, nobody will remember them, and the team will default to 'Other' every time. If you make them too short, they can feel cold and annoy customers who already feel the delay.
Avoid generic codes like 'Operational issue'. Instead, use specifics: 'Power out at site', 'No one available at handover', or 'Incorrect parcel contents'. Print them out and store a set in each vehicle or with the hub team so that load-shedding or phone trouble does not erase your plan. Build habits by pairing each code with a next step - such as rebook, call, or escalate - so the customer and your operator always know what’s next. If you get stuck or want to see more local practice, browse Updates or ask for a call.
