Silicon Tundra
OperationsLogisticsexceptionstrackingcustomer-communication

Logistics Shipment Exception Notice

Turn a raw exception event into a clear customer notice with next steps and revised ETA.

When to use this

Use this the moment an exception hits — weather, mechanical, customs — to get ahead of the shipper before they call you. Clear proactive notices protect the relationship more than a fast recovery does.

The prompt

You are the operations assistant for a logistics/freight company. Using the exception event details
below, write a notice to the shipper.

Exception details: [SHIPMENT_ID], origin [ORIGIN], destination [DESTINATION], original ETA
[ORIGINAL_ETA], exception type [EXCEPTION_TYPE: e.g. weather delay, mechanical, customs hold],
revised ETA [REVISED_ETA], action needed from shipper [ACTION_NEEDED_IF_ANY], contact
[OPS_CONTACT_NAME].

Produce, in this order:
1. A subject line naming the shipment ID and exception type.
2. An email (under 130 words) stating what happened, the revised ETA, and any action needed from
   the shipper.
3. A one-line SMS/tracking-portal update version.

Rules: state the revised ETA as an estimate, not a guarantee; do not speculate about cause beyond
[EXCEPTION_TYPE]; clearly separate "informational" from "action needed" content.

Replace the [BRACKETED] placeholders with your business's details, then paste into ChatGPT, Claude, or the AI tool you already use.

How to customize it

  • Separate 'informational' from 'action needed' — the prompt structures those distinctly so nothing gets missed.
  • State [REVISED_ETA] as an estimate, not a promise you might miss again.
  • Do not speculate beyond [EXCEPTION_TYPE]; the prompt sticks to what you actually know.
  • Send the one-line version to the tracking portal or SMS for a quick heads-up.

Want workflows like this running on autopilot?

We build AI agents that handle follow-up, reactivation, and intake automatically — no copy-pasting required.