When Outlook and Teams stalled on 12 November, nobody in the freight industry had the luxury of waiting for a fix. Microsoft traced the global outage to a fault left behind by a past network upgrade, Downdetector logged nearly 130,000 Outlook problem reports at the peak, and for many users the disruption lasted more than ten hours. In a typical office, that means a lost afternoon. In a freight forwarding operation, it means vessel cut-offs creeping closer, customs filings pending and customers asking where their cargo is, all without the tools that normally answer those questions.
It was not the first warning, either. Outlook and Teams were disrupted in January, and a separate Microsoft 365 outage stretched from 31 August to 3 September after a fault in a core authentication configuration. Digital communication will fail again at some point; the only open question is whether your team will be ready to keep shipments moving when it does.
Why Freight Forwarder Communication Is the First Thing to Break
Freight forwarding is a business of handoffs, and every handoff travels as a message: booking confirmations, bills of lading, delivery orders, status updates. When the channel carrying those messages disappears, the cargo does not stop moving; the information about it does. The practical goal in an outage is therefore not to restore email, but to keep decisions and instructions flowing by other means. Here is how forwarders can do exactly that.

Hour one: confirm, switch and triage
Begin by confirming the scope. Check the provider’s status page from a mobile connection and ask a colleague on another network whether they are affected, because a local fault and a global outage demand different responses. Within minutes, the team should move to its backup channel, with one named person coordinating. In the first hour, freight forwarder communication works best when a single coordinator owns the message flow, rather than ten people improvising in ten different places.
Next, divide the work. Assign one person to carriers and agents, one to customs brokers and one to customers, so that no call is duplicated and nothing slips through the gaps. Then triage: pull the most recent export of live bookings (a daily offline snapshot is well worth the minor effort) and rank shipments by deadline. Anything with a cut-off, a customs filing or a perishable-cargo clock inside the next 24 hours rises to the top. Everything else can wait for the systems to return.
Protect cut-offs and customs deadlines
Deadlines are where an outage becomes expensive, so they deserve phone calls rather than hopeful emails. Call carriers and agents directly to confirm space and gate-in instructions, and ask customs brokers to confirm filings by voice before the window closes. Where a deadline cannot be met, ask for an extension early: requests for flexibility land far better when they arrive before the problem, not after it.
Treat verbal agreements with the discipline of written ones. Repeat the details back, note the name of the person you spoke to, and keep a paper or offline log of every commitment with the time and what was promised. Once systems return, send written confirmations so that the record and the reality match. This simple habit prevents most of the disputes that tend to follow an outage.
Keep customers informed without the usual tools
Customers forgive delays far more readily than silence. Customer-facing freight forwarder communication during an outage should be proactive, honest and predictable: send a short SMS or make a call to key accounts before they ask, state what you know and what you are doing about it, and promise the next update at a fixed time. Prepared templates make this fast, and they keep the tone consistent across the team.
Shipment visibility need not vanish either, because carrier portals and tracking pages often run on separate systems from your own. Use them to check status manually, and use the table below to decide where to act first.
| Situation | Immediate action | Who to contact |
|---|---|---|
| Cut-off within 24 hours | Confirm space and gate-in by phone | Carrier booking desk or agent |
| Customs filing due today | Confirm submission by voice and ask about extensions | Customs broker |
| Perishable or temperature-controlled cargo | Verify storage and handling | Warehouse or terminal |
| Customer awaiting an ETA | Send a templated update with the time of the next one | Account manager |
Recover, reconcile and learn
When services return, resist the urge to simply carry on. Messages sent during the disruption may have been delayed, lost or duplicated, so reconcile bookings, confirmations and documents against your paper log and re-send anything unconfirmed. Tell customers and partners clearly that normal service has resumed.
Then hold a short review. How well did freight forwarder communication hold up? Which contacts were missing, which backup channels failed, and which decisions took too long? Note what the outage cost in delays, missed cut-offs and staff hours, since those figures make the strongest case for investing in better backups. Update the contact list, the templates and the escalation steps accordingly. A forwarder that learns something from every outage becomes a little harder to disrupt the next time.
Resilience is built before the outage
The Microsoft outage was a stress test that most of the industry never chose to take. The forwarders who handled it best were not necessarily those with the most sophisticated software; they were the ones who knew whom to call, what to say and which shipment came first. Those are habits, and habits can be built long before the next failure arrives.


