Proactive shipping notifications are updates you send when something real happens to an order, before the customer thinks to ask. Done right, they cut where-is-my-order questions and build trust. Done wrong, they train people to ignore you.
Short answer: Send a notification at real milestones only: order confirmed, shipped, out for delivery, delivered, and any exception like a delay or a failed delivery attempt. Skip the internal scans in between. Every message should say what changed, what it means, and what happens next. The delay message is the most valuable one you will ever send, and it is the one most brands never send.
What counts as a real milestone
A milestone changes what the customer knows or what they should do. "Your order shipped" is a milestone. "Package scanned at sort facility 4" is not.
The test is simple: would the customer change a plan or feel calmer because of this message? If yes, send it. If not, hold it. Carriers emit between 10 and 115 raw statuses per journey, and forwarding them raw is noise dressed up as helpfulness. Collapse them into a few human events first, the same status normalization your tracking page needs.
The notification schedule that works
| Moment | Send | Why |
|---|---|---|
| Order placed | Confirmation with what happens next | Kills the "did it go through" ticket |
| Shipped | Tracking link + expected date | The single most opened message |
| In transit | Nothing, unless the date changes | Silence is fine while things are normal |
| Delay or exception | What happened, new date, what you are doing | The trust-maker. Beat the customer to the bad news |
| Out for delivery | Heads-up, delivery window if known | Lets people plan, cuts failed deliveries |
| Delivered | Confirmation + where it was left | Kills the "it says delivered but" panic ticket |
| Ready for pickup | Location, hours, deadline | Parcels sent back from lockers are pure cost |
Cross-border orders earn one extra message: a "customs processing is normal, typically a few days" note when the parcel enters the quiet stretch. It prevents the exact anxiety window where tickets spike.
The delay message, specifically
Most WISMO tickets are born in the gap between something going wrong and the customer finding out from a stale tracking page. The delay notification closes that gap: what happened, the new expected date, and what you are doing about it. Brands consistently fear this message and customers consistently reward it. A delay announced is service. A delay discovered is a complaint. This is the heart of reducing WISMO tickets, and the templates in our post-purchase email guide include ready-to-adapt wording.
Channel: email, SMS, or both
Email is the default for every milestone: cheap, expected, searchable. SMS earns its cost on the time-sensitive moments only: out for delivery, delivery window, pickup deadline, and delays. Let customers pick channels on the tracking page, and keep the story identical across channels and the tracking page itself: same milestones, same dates, same wording.
Notifications need a trigger, not a template
The hard part is not writing the message. It is knowing the moment. A delay message requires something watching every shipment's scans against its promise and firing when they diverge. That is why notifications built into the logistics layer beat notifications bolted onto it.
In Pango, the same record that carries the carrier scan carries the promise made at checkout, so a late scan triggers the message automatically, through Pango's own email and SMS or through your existing tools. The notification is a side effect of running the operation, not a separate system to maintain.
The bottom line
Notify at real milestones, stay silent in between, and never let a customer discover a delay by themselves. The prerequisite is an operation that notices the moment, not just a template library. See how notifications, tracking, and carriers run on one record on the post-purchase operations platform and book a demo.
