Writing Clear Shipping Emails
Freight runs on email. The people you write to receive over a hundred a day and read them on a phone between calls. Writing for that reality is a skill.
The subject line that gets opened first
You will learn to write subject lines that get your email actioned today rather than tomorrow.
The person receiving your email is triaging an inbox. Your subject line is competing with ninety others for attention, and it must do three jobs before it is even opened.
| Job | Why |
|---|---|
| Identify the shipment | So they can open the file before reading |
| State what is needed | So they know whether this is theirs to action |
| Signal urgency honestly | So genuinely urgent things get seen first |
WEAK BETTER
--------------------------------------------------------------
Quick question MEDU4471820 - need revised ETA
today
Shipment NG-4417 / Ningbo-Felixstowe -
collection not made, need slot
URGENT!!! MSCU8842190 - free time expires
Thu 14th, need release today
Re: Re: Re: Fwd: booking NG-4417 - VGM cut-off 12:00 tomorrow,
awaiting weights from shipper
Following up Q-2026-1184 - space on 9 Oct sailing,
decision needed by Tue
Using "URGENT" on anything that is merely important. It works twice. After that the reader learns your urgent means their normal, and genuinely urgent emails from you stop being treated differently. Reserve it for things where hours actually matter and say why.
Start a new email rather than replying to a chain when the subject has changed. A thread titled "Re: Re: Fwd: booking" that now concerns a damage claim is unfindable in six months, and you will need to find it.
- The subject must identify the shipment, state the need and signal urgency honestly
- Overusing "urgent" destroys its value permanently
- Start fresh threads when the subject changes
The four-line structure
You will learn a structure that works for almost every operational email you will write.
- Line 1 — the referenceContainer, booking or job number. So the reader opens the right file first.
- Line 2 — the situationOne sentence of fact. No history, no explanation of how you feel about it.
- Line 3 — the askExactly what you want them to do, and by when. One request per email.
- Line 4 — why the timing mattersThe consequence. This is what converts a request into an action.
WEAK
Hi, hope you're well. I wanted to check in regarding the
shipment we discussed last week which seems to have had some
issues with the collection, I think the driver may not have
turned up or there was some confusion at the site, anyway
could you let me know where things stand when you get a
chance? Thanks so much, really appreciate it.
STRONG
Subject: MSCU4471820 / NG-4417 - collection not made,
need slot today
Hi Marta,
MSCU4471820, our ref NG-4417, collection Valencia.
The collection booked for Tuesday 09:00 did not take place
and the driver has not been rebooked.
Please confirm a new collection slot today.
Vessel cut-off is Friday 14:00. If we miss it the cargo rolls
a week and the customer's production line stops.
Thanks,
One email, one subject. If you need three things, send three emails. A single email containing three requests reliably gets one of them answered, and you will not control which one. This feels inefficient and is the opposite.
Write the ask before you write anything else. If you cannot state in one sentence what you want the reader to do, you are not ready to send the email — you are still thinking, and the reader should not have to watch you do it.
- Reference, situation, ask, consequence — in that order
- One request per email, always
- If you cannot state the ask in a sentence, the email is not ready
Asking for something and getting it
You will learn why some requests get actioned immediately and others sit unanswered.
Four things that make a request easy to say yes to
- It is specific. "Please confirm the VGM has been submitted" beats "please update me on the booking".
- It is addressed to someone. A request to a shared inbox with no name attached belongs to nobody.
- It is possible. Asking a carrier to reverse a cut-off wastes both your time and your credibility.
- It has a deadline with a reason. "By Thursday, because the vessel cuts off Friday" not "ASAP".
On "please advise"
This phrase appears constantly in freight and asks for nothing. Advise on what? Decide what? By when? Every time you are tempted to write it, replace it with the actual question.
| Instead of | Write |
|---|---|
| Please advise | Please confirm whether the container gated in before the 14:00 cut-off |
| Kindly revert | Can you reply by 3pm today with the new ETA |
| Awaiting your feedback | I need your approval on the £340 reroute cost before I book it |
| Please expedite | Can this be prioritised for release today — free time expires tomorrow |
When you genuinely need something fast from someone who does not report to you, explain the consequence rather than asserting urgency. "If this slips past Thursday the container rolls a week" gives them a reason to help. "This is urgent" gives them nothing.
- Requests must be specific, addressed, possible and deadlined
- Replace "please advise" with the actual question
- Explain the consequence rather than asserting urgency
Giving bad news clearly
You will learn to deliver bad news in a way that preserves trust rather than eroding it.
The instinct is to soften, delay, or bury the bad part in the middle of a paragraph. All three make it worse, because the reader eventually finds it and realises you tried to hide it.
The structure
- State it plainly, first"The vessel has been delayed and your container will now arrive on the 22nd, not the 15th."
- Say what it means for themIn their terms, not yours. Not "the ETA has moved" but "this pushes your delivery to the week of the 24th".
- Say what you have doneNot what you will do. Actions already taken.
- Give the optionsEven if one of them is "wait". People accept bad news far better when they have a choice.
- Commit to the next updateA specific time. This is what stops them chasing you.
Subject: NG-4417 - vessel delayed, new ETA 22 Nov (was 15 Nov) Hi Sam, Your container has been delayed. New ETA Felixstowe is 22 November, seven days later than planned. For you this means delivery moves from the week of 17 Nov to the week of 24 Nov. What I've done: confirmed the new ETA directly with the carrier, checked there is no further transhipment risk, and provisionally held a delivery slot for Tue 25 Nov so we do not lose it. Options: 1. Accept the new date. Delivery Tue 25 Nov, no extra cost. 2. Air freight the urgent portion. If you tell me which SKUs you need first, I can quote this afternoon - likely 4-5 days door to door. 3. Split delivery - take what arrives and we run a second delivery for anything you need sooner. I'll update you Thursday once the carrier confirms berthing, or sooner if anything changes. Sorry this has happened - happy to talk it through.
Waiting until you have a solution before telling the customer. It feels responsible and it is not. A customer who learns about a delay four days late has lost four days of their own planning, and they will remember the silence longer than the delay.
Apologise once, briefly, at the end. Repeated apology reads as either guilt or performance, and it pulls attention away from the options. One sincere line is enough.
- State the bad news first, in plain terms
- Translate it into what it means for them, then give options
- Commit to a specific next update — it stops them chasing
Emails that create a record
You will learn to write emails that will still make sense to a stranger in two years.
Some emails are conversation. Others are evidence. Instructions, agreements, quotes, damage notifications, warnings and any decision involving money will be read later — possibly by a lawyer, an insurer, or a colleague trying to understand what happened.
What makes an email work as a record
- It names the parties and the shipment rather than relying on "your shipment" and "as discussed"
- It states facts with dates and times, not "last week" or "recently"
- It confirms verbal conversations in writing — "further to our call at 11:20 today, confirming that you have authorised..."
- It separates fact from opinion — "the POD was signed clean" is fact; "I think the warehouse rushed it" is opinion and should be flagged as such or left out
- It avoids speculation about blame before the facts are established
Confirming phone calls in writing is the single most useful documentation habit in freight. A two-line email — "confirming our call: you've approved the £340 reroute, proceeding now" — takes thirty seconds and settles disputes that would otherwise be one person's memory against another's.
Writing something in frustration that reads badly out of context. Assume every email you send could be read aloud in a dispute. This is not about being guarded — it is about not handing someone a sentence that makes your competent handling look careless.
When you are angry, write the email, then do not send it. Save it as a draft, do something else for twenty minutes, and reread it. You will almost always cut two sentences, and those two sentences were the ones that would have caused problems.
- Some emails are conversation; others are evidence — know which you are writing
- Confirm phone calls in writing, with times and specifics
- Separate fact from opinion and avoid speculating about blame
Standard phrases, and what never to write
You will learn the industry's shorthand and the phrases that create liability or confusion.
Useful standard phrases
| "Subject to space and equipment availability" | A rate is not a booking |
| "Rates valid until [date]" | Protects you from a late acceptance |
| "We reserve all rights" | Used in claim notifications before quantifying |
| "Without prejudice" | Has a specific legal meaning in settlement discussions — do not use it decoratively |
| "For your information" | Signals no action needed, which readers appreciate |
| "Please confirm receipt" | For anything where you need proof it arrived |
Phrases to avoid
| Never write | Why |
|---|---|
| "That's our fault, we'll cover it" | Admits liability before facts are known. Your insurer may treat this as prejudicing the claim. |
| "Guaranteed delivery on the 15th" | Almost nothing in freight can be guaranteed. Use "scheduled" or "expected". |
| "The carrier is useless" | Unprofessional, unhelpful, and permanently in writing. |
| "Just declare it as samples" | Suggesting a false declaration. Never, under any circumstances. |
| "Don't worry about the paperwork" | The paperwork is the job. |
| "I'll sort it, leave it with me" (with no follow-up) | Only say this if you will actually do it and update them. |
If a customer or colleague ever asks you in writing to mis-describe goods, undervalue an invoice, or backdate a document, do not reply with a soft refusal or a joke. Decline clearly and escalate to a manager. These requests are not jokes and your written reply is part of the record.
- Standard phrases carry specific meaning — use them precisely
- Never admit liability, guarantee dates, or suggest false declarations
- Decline improper requests clearly in writing and escalate
Module 1 review
You need three different things from the same carrier contact. What do you do?
A single email with three requests reliably gets one answered, and you will not control which. One email, one ask.
A delay is confirmed but you have no solution yet. When do you tell the customer?
Customers remember the silence longer than the delay. Telling them late costs them their own planning time.
A customer asks you in writing to declare goods as samples to reduce duty. How do you respond?
This is a request for a false declaration. A clear written refusal protects you, and escalation is appropriate rather than dramatic.
Talking to Carriers and Drivers
The people who physically move your cargo. How you deal with them decides whether you get help on the day you badly need it.
What a driver needs from you
You will learn what information prevents a failed collection or delivery.
Drivers work to the information they are given. Almost every failed collection traces back to something the office did not tell them.
| Information | Why it matters |
|---|---|
| Full address, with postcode | Industrial estates are badly signposted and satnav often fails |
| A live mobile number and a name | One call solves most on-site problems — if there is someone to call |
| The time window, and any booking reference | Sites turn away drivers without a slot reference |
| What they are collecting | So they can check count and condition |
| Who loads | Driver, site staff, or forklift — and whether help is expected |
| Access notes | Low bridge, narrow entrance, gate code, which entrance to use |
| What to do if something is wrong | Who to call, and authority to wait or leave |
A driver arrives at an industrial estate where three units share one entrance. He has an address but no unit number, no contact name and no phone number. He waits forty minutes, calls the office, gets voicemail, and leaves. The collection fails, a charge is raised, and the container misses its cut-off. The missing information was a mobile number.
Write collection and delivery instructions as though the reader has never been there and cannot ask you a question. That is frequently the actual situation — a subcontracted driver at 6am with your instruction sheet and nothing else.
- Most failed collections come from missing information, not driver error
- Always include a name, a live mobile number and access notes
- Write instructions for someone who cannot ask you a question
Phone calls that solve things fast
You will learn when to phone instead of emailing, and how to structure the call.
When to phone
- Something is happening now — a driver on site, a cut-off in two hours
- The situation needs back-and-forth that would take six emails
- Email has failed twice
- The conversation is sensitive and tone matters
When to email instead
- You need a record
- The information is detailed — numbers, addresses, lists
- It is not urgent and the other person is in a different time zone
1 IDENTIFY YOURSELF AND THE SHIPMENT (5 seconds)
"Hi, it's Sam from Containor, calling about container
MEDU4471820, our reference NG-4417."
2 STATE THE SITUATION IN ONE SENTENCE (10 seconds)
"The driver is on site now and the warehouse says there's
no booking reference on their system."
3 SAY WHAT YOU NEED (10 seconds)
"Can you check whether the slot was booked under a
different reference, while I hold the driver."
4 AGREE THE NEXT STEP AND TIMING
"You'll call me back within ten minutes - is that right?
My direct line is..."
5 CONFIRM IN WRITING AFTERWARDS
Two lines by email: what was agreed, and by when.
Always end an operational call by restating what will happen and who is doing it. "So you'll email the revised ETA this afternoon and I'll update the customer" takes five seconds and removes the most common cause of things falling between two people.
Phoning without knowing what you want. Calls where the caller thinks aloud waste the other person's time and train them to let your calls go to voicemail. Know the ask before you dial.
- Phone for now-problems and back-and-forth; email for records and detail
- Identify, state, ask, agree next step, confirm in writing
- Always restate who is doing what before hanging up
Chasing without arguing
You will learn to apply pressure that produces action rather than resistance.
You will chase carriers constantly. The difference between someone who gets prioritised and someone who gets ignored is almost entirely in how they chase.
The escalation ladder
- Polite and specific"Can you confirm the gate-in happened before the 14:00 cut-off?"
- Add the consequence"I need to confirm to the customer today — their production line depends on this sailing."
- Add a deadline and a next step"If I don't have confirmation by 4pm I'll need to escalate to your operations manager, which I'd rather not do."
- Escalate, as statedCopy the manager, stay factual, do not editorialise about the person you are escalating past.
Most chasing never needs to pass step two. The reason step three works is that you stated it at step three and then did it — not because you were forceful.
Never escalate without warning the person first. Copying someone's manager out of the blue turns a colleague into an adversary permanently, and freight is a small industry where you will meet the same people for decades. Warn, then escalate if nothing changes.
Keep goodwill in reserve. If you chase everything at maximum intensity, you have nothing left for the day something genuinely critical happens. The people who get real help in a crisis are the ones who did not cry wolf on routine bookings.
- Escalate in steps: specific, consequence, deadline, then act
- Always warn before escalating over someone's head
- Save intensity for what is genuinely critical
Escalating to the right person
You will learn who to approach when the normal contact cannot help.
| Problem | Who can actually fix it |
|---|---|
| Booking or space issue | The carrier's booking desk, then their commercial contact |
| Container not released at destination | The destination office, not origin |
| Rate or invoice dispute | The commercial or account manager, not operations |
| Customs hold | Your broker — the carrier cannot help |
| Demurrage waiver request | The carrier's commercial team, with a documented reason |
| Driver or collection failure | The haulier's traffic office, immediately |
| Damage claim | The carrier's claims department, in writing |
Escalating well
A good escalation is short, factual and contains everything needed to act. It does not require the reader to piece together a story from a forwarded chain of forty messages.
Subject: ESCALATION - MEDU4471820 - release not actioned,
demurrage accruing from today
Hi David,
Escalating this as agreed with Marta yesterday.
Container MEDU4471820, discharged Felixstowe 12 Nov
Issue Release not actioned despite payment confirmed
and telex release instruction sent 13 Nov
Chased 13 Nov (email), 14 Nov (email + call), 17 Nov (call)
Impact Free time expired today. Demurrage now accruing
at GBP 45/day, rising to 90/day from 21 Nov.
Needed Release actioned today, and confirmation by email.
Payment evidence and the original release instruction are
attached. Happy to call if that's quicker.
Thanks,
Include the chase history with dates. It shows you followed process before escalating, which makes the escalation reasonable rather than impatient — and it removes any argument about whether you gave them a fair chance.
- Match the problem to the team that can actually fix it
- Destination problems need the destination office
- Include the chase history — it makes escalation reasonable
Keeping goodwill for the day you need it
You will learn why relationships with carriers are a working asset, not a pleasantry.
Freight runs on discretion. Carriers decide who gets the last slot when a vessel is full, whose container gets prioritised for release, and whose demurrage waiver request gets considered. None of that is in a contract. All of it depends on who you are to them.
What builds goodwill
- Accurate bookings. Correct weights, realistic ready dates, no last-minute changes.
- Paying on time. More influential than most people realise.
- Not crying wolf. When everything is urgent, nothing is.
- Saying thank you when they help. Almost nobody does this, which is precisely why it is remembered.
- Being reasonable when something is genuinely not their fault.
What destroys it
- Blaming them in front of your customer for something outside their control
- Escalating without warning
- Repeatedly booking space and not using it
- Disputing invoices as a negotiating habit rather than when genuinely wrong
Two forwarders need space on the same full sailing during peak season.
Forwarder A books accurately, pays on time, and last month emailed to thank the carrier's team for pulling a container forward. The booking desk finds them a slot.
Forwarder B marks everything urgent, books speculatively and cancels, and escalated to a manager last week without warning. They are told the vessel is full.
Both statements are true — the vessel is full. Someone still got the slot.
Freight is a small industry with long memories. The booking clerk you deal with today may be the operations manager you need a favour from in six years. That is not a reason to be nice; it is a reason to be consistently professional even when you are annoyed.
- Carriers exercise discretion constantly, and it is not in any contract
- Accurate bookings, prompt payment and honest urgency build standing
- The industry is small and memories are long
Module 2 review
A carrier contact has not responded to two emails about a cut-off. What is the next step?
Warning before escalating keeps a colleague as a colleague. Escalating unannounced creates an adversary in an industry where you will meet the same people for decades.
A container is not being released at destination. Who do you contact?
Release happens at destination. Escalating at origin adds a hop and loses a day, while demurrage accrues.
Why does goodwill with carriers matter commercially?
Who gets the last slot on a full vessel is a judgement made by a person. Standing with that person is a working asset.
Keeping the Customer Updated
The habit that decides whether clients stay. Almost nobody does it well, which makes it the cheapest competitive advantage available.
The update nobody had to ask for
You will learn why proactive updates matter more than any other client-facing habit.
When a customer has to ask where their shipment is, two things have already happened: they have spent attention on something they hired you to handle, and they have learned that you were not watching it.
What a proactive update does
- Removes their anxiety before it becomes a phone call
- Demonstrates you are watching, which is most of what they are buying
- Surfaces problems while options still exist
- Reduces your own workload — one update prevents three chase emails
Subject: NG-4417 - on track, vessel sailed 9 Oct, ETA 12 Nov Hi Sam, Quick update on your Ningbo shipment, nothing needed from you. Container MEDU4471820 Sailed 9 October, as planned ETA 12 November Felixstowe Status On board, direct service, no transhipment Next steps from us: - We'll file the customs entry on 10 Nov - Delivery slot provisionally held for Tue 18 Nov One thing to note: we'll need your commercial invoice by 7 November for the customs entry. Could you ask your supplier to send it across when convenient? Next update from me on 10 November, or sooner if anything changes.
Notice the phrase "nothing needed from you" in the opening line. Busy clients triage emails looking for what requires action. Telling them immediately that this is information, not a task, means they actually read it rather than saving it for later.
Send an update at the three moments clients most want one: when it sails, when it arrives, and when anything changes. Those three, done consistently, put you ahead of most of the industry.
- If a client has to ask, they have learned you were not watching
- Proactive updates reduce your own workload, not increase it
- Sailed, arrived, changed — the three moments that matter
How often is too often
You will learn to match update frequency to what the client actually needs.
| Stage | Update frequency | Why |
|---|---|---|
| Booking confirmed | Once | Confirms it is in hand |
| Sailed or departed | Once | The first real milestone |
| Mid-voyage, on schedule | Every 1–2 weeks, brief | Presence without noise |
| Final week before arrival | Weekly, then on arrival | They need to plan receipt |
| Customs and clearance | When cleared, or if held | The riskiest stage |
| Delivery | Booked, then confirmed | They need staff ready |
| Anything goes wrong | Immediately, then as promised | Silence is what damages trust |
Match the client, not a rule
Some clients want everything; others want to hear from you twice. Ask at the start of the relationship: "How much do you want to hear from me — every milestone, or only when something needs your attention?" Almost nobody asks this, and the answer saves both sides considerable friction.
Sending an automated tracking notification and treating it as an update. Clients can read tracking themselves. What they cannot do is interpret it — your value is saying "this event means your delivery is still on for the 18th", not forwarding the event.
- Frequency should rise as the shipment approaches its critical stages
- Ask each client how much contact they want
- Interpret events; do not merely forward them
Explaining a technical problem simply
You will learn to explain freight problems to people who do not work in freight.
Your client runs a furniture business, not a shipping line. Explaining a problem in industry language transfers your confusion to them rather than resolving it.
| Industry version | Client version |
|---|---|
| "The box was rolled due to overbooking on the mother vessel." | "The ship was full and your container couldn't be loaded. It goes on next week's sailing instead — that's a seven-day delay." |
| "We're awaiting the telex release from origin." | "The shipper needs to release the paperwork before the port will hand over your goods. I've asked them to do it today." |
| "Customs have routed it for a physical exam." | "Customs have selected your container for inspection. They do this at random. It usually adds two to four days, and there's an inspection fee of around £350." |
| "Demurrage is accruing at tier two." | "The port charges storage once free time runs out, and the daily rate has just doubled to £90. We need to collect by Friday." |
| "The VGM wasn't submitted before cut-off." | "A required weight declaration missed its deadline, so the container couldn't be loaded. I'm sorting it for the next sailing." |
The three-part explanation
- What happened, in plain wordsNo acronyms, no passive voice hiding who did what.
- What it means for themIn days, money, or both.
- What happens nextWho is doing what, and when they will hear from you.
If a client asks a follow-up question that suggests they misunderstood, the explanation was not clear enough. Do not repeat the same words more slowly — explain it differently. The failure was yours, not theirs.
- Translate industry terms into consequences the client understands
- Say what happened, what it means, and what happens next
- A confused follow-up means your explanation failed, not their attention
Managing expectations before they form
You will learn to set expectations at the start so later news is never a shock.
Most client anger is not about what happened. It is about the gap between what happened and what they were led to expect. You control that gap at the quoting stage.
What to say up front
- Transit as a range, not a date. "32 to 36 days port to port, so delivery in the week of the 18th" rather than "arrives the 15th".
- Name what could go wrong. Customs selection, port congestion, peak season rolling. Once named in advance, they become known risks rather than your failures.
- Be explicit about what is excluded. Demurrage, examination fees, waiting time — by name, with rates.
- State what you need from them, and when. Documents, funds, decisions.
Two forwarders ship identical containers. Both are selected for customs examination, delayed four days, and charged an inspection fee.
Forwarder A said at quoting stage: "Customs select a proportion of containers for examination at random. If yours is chosen it typically adds two to four days and costs around £350. It is outside anyone's control." When it happens, the client says "ah, the thing you mentioned" and pays.
Forwarder B said nothing. When it happens, the client believes the forwarder made a mistake, disputes the fee, and questions the delay.
Same event, same cost, same delay. One is a known risk; the other is a failure.
Naming risks in advance feels like advertising your weaknesses. It is the opposite — it demonstrates that you know the territory. Clients who hear the risks up front trust the confident parts of your quote more, not less.
- Anger comes from the gap between expectation and outcome
- Quote transit as a range and name the realistic risks in advance
- A named risk is understood; an unnamed one looks like your failure
Weekly summaries for key accounts
You will learn to produce a weekly account summary that clients actually read.
Subject: Northgate Retail - weekly shipment summary, w/c 17 Nov
Hi Sam,
This week's position across your six live shipments.
NEEDS YOUR ATTENTION
NG-4419 Commercial invoice still outstanding from supplier.
We need it by Thu 20th or the customs entry slips
and demurrage starts Mon 24th.
ON TRACK
NG-4417 Delivered Tue 18 Nov, signed clean. File closed.
NG-4420 Sailed 14 Nov, ETA Felixstowe 16 Dec.
NG-4421 Booked for 21 Nov sailing, container positioned Wed.
NG-4422 Quote sent 17 Nov, valid to 28 Nov.
WATCHING
NG-4418 Customs selected for examination 17 Nov. Expect
release Thu 20th. Inspection fee approx GBP 350
will appear on your invoice.
COMING UP
- Peak season surcharge applies to bookings from 1 Dec.
If your December volume can sail in November, that saves
roughly GBP 240 per container. Happy to look at this.
Next summary Monday 24 Nov.
Why this format works
It is sorted by what the client must do, not by shipment number. The one thing needing their action is at the top and unmissable. Everything else is reassurance they can skim.
Listing shipments in reference order, so the urgent item sits fourth and looks identical to the routine ones. Sort by attention required, always. A client who has to hunt for the important line will eventually stop reading.
Include one forward-looking item each week — a surcharge coming, a seasonal pressure period, a saving opportunity. It shifts you from reporting the past to helping them plan, and it is the difference between a supplier and an adviser.
- Sort by attention required, not by reference number
- Put the client's actions at the top, unmissable
- Add one forward-looking item to shift from reporting to advising
Module 3 review
How should you explain "the box was rolled" to a furniture retailer?
Translate the event into a consequence in plain words. Industry language transfers your problem to the client rather than resolving it.
Why name risks like customs examination at the quoting stage?
Client anger comes from the gap between expectation and outcome. Naming realistic risks in advance closes that gap before it opens.
How should a weekly account summary be ordered?
If a client must hunt for the line that needs them, they will eventually stop reading the summary altogether.
Saying No and Pushing Back
Agreeing to everything is not service. It is how forwarders lose money and eventually lose the client anyway.
When the request is genuinely impossible
You will learn to distinguish difficult from impossible, and to say so early.
| Genuinely impossible | Merely difficult or expensive |
|---|---|
| Making a vessel that has sailed carry the cargo | Finding space on a full sailing |
| Clearing customs without a commercial invoice | Clearing quickly with incomplete data |
| Reversing a cut-off that has passed | Getting a container gated in at short notice |
| Shipping undeclared dangerous goods legally | Shipping DG at short notice |
| Delivering 40ft of cargo to a site that cannot take the vehicle | Arranging a transloading solution |
| Backdating a document | Expediting document issuance |
Say it immediately
The worst outcome is agreeing to try something impossible, spending two days on it, and then delivering the same no — but two days later, with the client's alternatives now closed off.
Subject: NG-4423 - cannot make the 21 Nov sailing, options
for the 28th
Hi Sam,
I want to be straight with you rather than leave this hanging.
The 21 November sailing cuts off tomorrow at 14:00. Your cargo
won't be packed until Thursday, so it cannot make that vessel.
That's a hard deadline set by the terminal, not something I can
negotiate.
Realistic options:
1. Next sailing, 28 November. ETA 30 December. No extra cost.
2. Air freight the urgent portion. Roughly GBP 3,400 for
400 kg, 5-6 days door to door.
3. Road-sea via a shorter route if you can accept a different
origin port - let me know and I'll price it today.
I'd suggest option 1 unless the December date genuinely doesn't
work, in which case option 2 for part of the volume.
Shall I hold space on the 28th while you decide?
Always attach the reason to the constraint rather than to yourself. "The terminal cuts off at 14:00" is a fact about the world. "I can't do that" sounds like a limitation of yours, and invites the client to find someone who says yes — usually someone who is wrong.
- Distinguish impossible from difficult and say so immediately
- Delayed refusal is worse than immediate refusal
- Attribute the constraint to the fact, not to yourself
Offering an alternative instead of a refusal
You will learn to turn a no into a decision the client can make.
A bare no ends a conversation. A no with options continues it, and the client usually chooses something workable.
The structure
- Acknowledge the real needNot the request. "You need stock on shelves before the 15th" rather than "you asked for the 21st sailing".
- State the constraint factuallyWhat cannot happen, and why.
- Give two or three genuine optionsWith cost and timing attached. Not one real option and two straw men.
- Recommend oneYou are the specialist. Clients want a view, not a menu.
- Ask for a decision by a specific timeTied to something real.
Step one matters most. Clients ask for solutions, not problems — "can you get it on the 21st sailing" is their proposed answer to an underlying need. If you address only the request, you may miss a much better solution. Ask what they are actually trying to achieve.
A client insists on air freighting a full consignment at considerable cost. The forwarder asks what is driving the date, and learns a retail launch needs display stock only — about a tenth of the volume. They air the display units and ship the rest by sea. The client gets what they needed at a fraction of the cost, and the forwarder looks like an adviser rather than a booking service.
- Address the underlying need, not just the stated request
- Give two or three genuine options with cost and timing
- Always recommend one — clients want a view, not a menu
Protecting your margin politely
You will learn to hold a price without damaging a relationship.
Clients will ask for discounts, absorbed charges and free extras. Some requests are reasonable. Agreeing to all of them turns a profitable account into an unprofitable one, slowly enough that nobody notices.
Three situations and how to handle them
| Request | Response |
|---|---|
| "Can you absorb the demurrage?" | "The demurrage was caused by the invoice arriving four days late from your supplier. I've asked the carrier for a goodwill reduction and I'll pass on whatever they give, but I can't absorb a charge we didn't cause." |
| "Your competitor is £200 cheaper." | "Can you send me their quote? I'd like to check we're comparing the same scope — ours includes destination haulage and customs entry, which often sit outside a headline rate." |
| "Can you do this one at cost as a favour?" | "I can do a reduced rate on this one given the volume you've sent this quarter. It would be £X. Below that I'd be shipping at a loss, which isn't sustainable for either of us." |
The principle
Explain the reason, offer what you genuinely can, and state the limit plainly. Clients respect a supplier who knows their numbers far more than one who folds instantly — because instant folding tells them the original price was inflated.
Discounting immediately to avoid an awkward conversation. It teaches the client that your prices are negotiable, so every future quote becomes an opening position. One firm, well-explained no is easier than a permanent negotiation.
When you do concede something, name it as a concession and attach it to a reason. "I'll absorb the waiting time on this one because we booked the slot late" preserves the value of the gesture. Silent absorption gets noticed by nobody and expected by everybody.
- Explain the reason, offer what you can, state the limit plainly
- Instant discounting signals the original price was inflated
- Name concessions explicitly so they retain value
Handling pressure from a large client
You will learn to manage a client who is important enough to be difficult.
Large accounts bring volume and leverage. Some use it well; some use it to push suppliers into commitments they cannot meet. The pressure usually takes one of four forms.
| Pressure | Holding position |
|---|---|
| "Just make it happen, I don't care how" | "I'll do everything possible. What I can't do is commit to a date I know isn't achievable — you'd plan around it and it would fail." |
| "We'll take our volume elsewhere" | "I understand, and I'd be sorry to lose it. I'd rather tell you the truth about this shipment than win it by promising something that won't happen." |
| "Your competitor says they can" | "They may know something I don't — if they can, take it. If it's based on the same cut-off I'm seeing, I'd want to understand how before relying on it." |
| "Can't you just describe it differently on the paperwork?" | "No. That's a false declaration and I won't do it. Let me find you a legitimate route to the same outcome." |
The fourth row is different from the others. Rate pressure and date pressure are commercial negotiations where you can weigh the relationship. A request to falsify a declaration is not negotiable at any volume, from any client. Decline clearly, in writing, and escalate internally.
A large client pushes a forwarder to confirm a delivery date the forwarder knows is unrealistic. The forwarder confirms it rather than risk the relationship. The date is missed, the client's own customer is let down, and the account is lost anyway — with the added damage that the forwarder is now the supplier who promised and failed.
Declining the date honestly might have cost the shipment. Accepting it cost the account and the reputation.
Being honest under pressure occasionally loses a shipment. It very rarely loses an account. Clients who leave over one honest no were usually going to leave anyway over the first failure — and buyers talk to each other about who tells them the truth.
- Commercial pressure is negotiable; requests to falsify documents are not
- Confirming a date you know will fail costs more than declining it
- Honest refusals rarely lose accounts; failed promises usually do
Module 4 review
A client insists on air freighting a full consignment at high cost. What is your first question?
Clients state solutions, not needs. Understanding the underlying requirement often reveals that a small part needs to fly and the rest can sail.
A major client asks you to describe goods differently on the customs paperwork. What do you do?
Rate and date pressure are commercial negotiations. A false declaration is not, at any volume, from any client.
Why is instantly discounting when challenged on price a mistake?
Clients respect a supplier who knows their numbers. One firm, well-explained no is easier than a permanent negotiation.
Handling Complaints
A complaint is a client still talking to you. Handled well, it produces a more loyal account than a shipment that went perfectly.
Listening before defending
You will learn why the first response decides how the whole complaint goes.
The instinct when accused is to explain. Explaining first reads as defending, and defending tells the client you are more interested in your position than their problem.
The first response
- Let them finishInterrupting to correct a detail early costs you the whole conversation. The detail can wait.
- Acknowledge the impact"That's put you in a difficult position with your own customer" — this is not admitting fault, it is recognising reality.
- Confirm you understandSummarise their complaint in your own words and check you have it right.
- Say what you will do and when"I'm going to check exactly what happened and come back to you by 3pm."
- Then investigateNot before.
Acknowledging impact is not admitting liability. "I understand this has caused you a real problem" is about their situation. "This was our fault" is about responsibility. Keep them separate — you can and should do the first immediately, and the second only once you know the facts.
Explaining the cause while the client is still angry. Even a completely correct explanation lands as an excuse at that moment. Acknowledge first, investigate, then explain when they are ready to hear it.
- Listen fully before explaining anything
- Acknowledging impact is not admitting liability
- Commit to a specific time, then investigate
Separating fact from feeling
You will learn to identify the real issue underneath an emotional complaint.
A complaint usually contains three things mixed together: what actually happened, what the client believes happened, and how they feel about it. All three are real, and they need different responses.
WHAT THE CLIENT SAID
"This is a shambles. Nobody told us anything, the goods are
a week late, we've had to apologise to our biggest customer,
and now you're charging us extra for the privilege. Frankly
I'm wondering why we use you at all."
FACTS (verifiable)
- Goods arrived 7 days later than scheduled
- An additional charge has been raised
- Client informed their customer of a delay
BELIEFS (may or may not be accurate)
- "Nobody told us anything" -> check: what was sent, when?
- "You're charging us extra" -> check: was it excluded and
disclosed at quoting?
FEELINGS (real regardless of facts)
- Embarrassed in front of their own customer
- Feels ignored
- Questioning the relationship
WHAT ACTUALLY NEEDS ANSWERING
1. The communication gap - this is the real complaint
2. The charge - explain or credit
3. The relationship - address directly, not by ignoring it
Note: the delay itself may be nobody's fault. The client is
not really complaining about the delay. They are complaining
about finding out late and being embarrassed.
The loudest part of a complaint is rarely the important part. Look for the sentence about their own customer — that is usually where the real damage is, and addressing it directly resolves more than winning an argument about the facts.
- Complaints mix facts, beliefs and feelings — separate them
- Check beliefs against your records before accepting or disputing them
- The real complaint is often the communication, not the event
What you can promise and what you cannot
You will learn the boundaries of what to offer while a complaint is live.
| You can offer | You cannot offer |
|---|---|
| To investigate and report back by a specific time | An admission of liability before the facts are known |
| To waive or reduce your own fees | To waive a carrier's or authority's charges |
| To pursue a claim on their behalf | A guarantee that a claim will succeed |
| A specific process change going forward | A promise it will never happen again |
| To escalate internally and involve a manager | Compensation beyond your authority |
| A written summary of what happened | Blame directed at a named individual |
On "it won't happen again"
Never say this. Vessels will be delayed again, customs will select containers again, suppliers will send invoices late again. What you can promise is a specific change: "I'll be checking the loading event on every one of your sailings from now on, and you'll hear from me the same day if anything moves."
Be clear about your own authority. If you cannot approve a credit, say "I'll need to get this approved and will come back to you today" rather than implying agreement you cannot deliver. A retracted offer damages a relationship far more than a delayed one.
Offering a process change is often worth more to a client than money. A credit resolves one shipment; a change tells them the next fifty will be different. And it costs you nothing except the discipline to actually do it.
- Offer investigation, your own fees, and specific process changes
- Never promise it will not happen again — promise a named change
- Do not imply authority you do not have
A written response that does not accept liability
You will learn to write a complaint response that is warm, honest and legally careful.
Subject: NG-4418 - our response, and what we're changing Hi Sam, Thank you for calling yesterday. You were right to raise it and I've looked into everything you mentioned. WHAT HAPPENED The vessel was delayed by four days due to port congestion at transhipment, and your container was then selected by customs for physical examination, adding a further three days. Neither was within our control or the carrier's. WHERE WE FELL SHORT We knew about the vessel delay on 11 November and did not tell you until the 14th. That's three days you could have used to warn your own customer, and we took that away from you. That part is on us and I'm sorry. THE CHARGES The GBP 350 examination fee is levied by the authority and we have no discretion over it. I've attached the documentation. The GBP 90 waiting time charge I am crediting in full, as our delivery notification to you was late. WHAT WE'RE CHANGING From now on, on all Northgate shipments: - I check vessel schedules every Monday and Thursday - You hear from me the same day any ETA moves, even by a day - Weekly summary continues, with anything needing you at the top I'm not going to promise delays won't happen again - they will, and they're often outside anyone's control. What I can promise is that you'll hear about them from us first. Happy to discuss any of this.
Why this works
- It separates what was outside anyone's control from what the forwarder got wrong
- It apologises specifically and once, for the actual failure
- It credits what is fair and explains what cannot be credited, with evidence
- It commits to named changes, not vague assurances
- It is honest about the limits of what can be promised
Apologising for everything, including things you did not cause. It sounds generous and reads as either incompetence or an admission. Apologise precisely for what you got wrong — it is more credible and it protects your position on the rest.
- Separate what was outside control from what you got wrong
- Apologise specifically and once, with evidence for what you cannot credit
- Commit to named changes rather than vague reassurance
Turning a complaint into a retained client
You will learn why well-handled complaints strengthen accounts rather than ending them.
A client who never complains has never tested you. One who complains and sees it handled properly has evidence about how you behave when things go wrong — which is the only thing that genuinely distinguishes one forwarder from another.
What turns it around
- SpeedResponding within hours rather than days signals it matters to you.
- Honesty about your own partClients can tell the difference between an explanation and an excuse. Owning your share buys credibility for the parts that genuinely were not yours.
- Something concreteA credit, a process change, or both. Sympathy alone changes nothing.
- Follow-throughThe change you promised, actually implemented, visibly. This is where most recoveries fail.
- A check-in laterTwo or three shipments on: "How has it been since we changed the update process?"
A client threatens to move their volume after a badly handled delay. The forwarder responds within four hours, credits their own fee, explains what was outside their control with documentation, and commits to twice-weekly schedule checks with same-day notification.
Six weeks later they email the client: "We've had two ETA changes since — you heard about both the same day. Has that worked for you?"
The client stays, and later increases volume. The reason they give is not the credit. It is that the forwarder followed up unprompted to check the fix was working.
Log every complaint, even small ones, with what caused it and what you changed. After a year you will see that three or four root causes generate most of them — and fixing those is worth more than handling complaints well ever will be.
- A complaint is evidence of how you behave under pressure
- Speed, honesty, something concrete, and follow-through
- Log complaints — a few root causes generate most of them
Module 5 review
A client is mid-complaint and one of their factual claims is wrong. What do you do?
Interrupting to correct a detail costs you the whole conversation. The detail can be addressed accurately once you have checked and they are ready to hear it.
What should you never promise in a complaint response?
Vessels will be delayed again and customs will select containers again. Promise a named, specific change instead — it is credible and deliverable.
In the case study, what did the client say persuaded them to stay?
Follow-through is where most recoveries fail. Checking unprompted that the change worked is what proves the response was real rather than performance.
Course Assessment
Twelve questions covering all five modules. You need 10 of 12 correct to meet the 80% pass mark. You can retake it as often as you like.
Complete all 25 lessons to unlock the final assessment.