Shipping notifications are the most-read messages your business will ever send. A customer who has spent money and is waiting for a parcel opens tracking updates with an attention no marketing email will ever earn. That makes every notification a rare opportunity — and a rare risk. Done well, they build quiet confidence. Done badly, they generate anxiety and support tickets.
The two failure modes
Notifications fail in two opposite directions, and most businesses manage to hit both.
The first is silence. A customer books, receives one confirmation, and then hears nothing for days. Silence breeds anxiety, and anxious customers check the tracking page compulsively and call support to ask where their order is.
The second is noise. Overcompensating, some businesses fire a message for every micro-event — every scan, every hub, every hop. The updates become meaningless, the customer mutes them, and the one notification that actually mattered gets lost in the flood.
Notify on meaning, not on events
The fix is to notify on meaningful milestones, not raw events. A customer doesn't care that a parcel was scanned at a sortation hub at 3:47am. They care about the handful of moments that change what they should do:
- Booked and confirmed — you have my order
- Picked up / dispatched — it's really on its way
- Out for delivery — be ready today
- Delivered — with proof
- Exception — something needs your attention, and here's what to do
That's roughly five messages for a normal journey. Everything else is noise dressed up as transparency.
Say what to do, not just what happened
A status is only half a message. "Delivery attempted" tells a customer what happened but leaves them stranded. "We missed you — reschedule for tomorrow in one tap" tells them what to do next. The second version prevents a support call; the first guarantees one.
Every notification should answer the customer's real question, which is almost never "what is the status?" It's "what does this mean for me, and what should I do now?"
Timing and channel
The best content, sent at the wrong time or on the wrong channel, still fails. An "out for delivery" alert is gold at 8am and useless at 8pm. A delivery exception deserves an immediate, interruptive channel like SMS or WhatsApp; a routine "picked up" is fine as a quieter email.
Matching urgency to channel is a form of respect for the customer's attention — and respected customers stay subscribed to your updates instead of muting them.
Make it feel like you
A tracking notification is a brand touchpoint, whether you treat it as one or not. Generic carrier jargon — "consignment tendered to delivery agent" — erodes the experience. Clear, human language on your own branded tracking page turns a delivery into a moment that reinforces why the customer chose you.
Measuring notification health
Notifications are one of the few parts of an operation where you can measure trust almost directly, and yet most businesses never look. The signals are right there in the data, and they'll tell you honestly whether your updates are helping or annoying.
The first metric to watch is the opt-out or mute rate. If customers are actively turning off your notifications, you're sending too many, at the wrong times, or with too little value. A rising mute rate is the clearest possible signal that your messages have crossed from helpful to noise. The second is open and engagement rate: shipping notifications should have engagement far above marketing email, because the customer is genuinely waiting. If yours don't, the content or timing is off.
The most valuable metric, though, is ticket deflection. Every "where is my order?" support contact is, in a sense, a notification that should have been sent and wasn't — or was sent but didn't answer the customer's real question. Tracking the volume of status-check contacts against your notification changes tells you whether better updates are actually reducing support load. When you get it right, the two move in opposite directions: notifications up in quality, support tickets down in volume.
- Mute / opt-out rate — is the volume or timing wrong?
- Engagement rate — is the content actually useful?
- Status-check support contacts — are notifications answering the real question?
- Failed-delivery rate — are "out for delivery" alerts landing in time to help?
Treating these as a dashboard rather than an afterthought turns notification design from guesswork into a feedback loop. You change a message, watch the mute rate and the ticket volume, and let the customers tell you whether you improved their experience. That loop is how a good notification programme stays good as your volume and audience grow.
The unsubscribe is a feature, not a failure
It sounds counterintuitive, but giving customers easy, granular control over their notifications makes your programme stronger, not weaker. A customer who can turn off the updates they don't want is a customer who keeps the ones they do — and who trusts you more for respecting their attention. The businesses that hide the unsubscribe, or make it all-or-nothing, are the ones that drive people to mute everything or mark it as spam, taking the important messages down with the noise.
Granularity is the key. Some customers want every milestone; others want only "out for delivery" and "delivered." Letting them choose turns notifications from something done to them into something they've opted into, which is exactly the relationship you want. Respecting that choice also keeps your sender reputation healthy, so the messages that matter actually arrive. Treating the unsubscribe as a feature to design well, rather than a leak to plug, is a small shift in mindset that pays off in exactly the trust these messages are meant to build.
The takeaway
Trust is built by sending fewer, better-timed, more useful updates — each one answering "what should I do now?" in language that sounds like you. Get that right and your notifications stop being a cost centre of support tickets and start being one of the most reliable loyalty tools you own.
