A Email design · 02 Shipping update (+ delay addendum) Transactional · trigger: carrier scan events Hub
Inbox · charlotte.m@example.com never asks for passwords or full card numbers
A
ApexCommerce <hello@apexcommerce.com.au>
08412 is packed — and one honest update inside
to charlotte.m@example.com · Fri 11 Sep 2026, 6:10pm AEST
A StarTrack Express · STX-88412-VIC

Packed, weighed and labelled.

4.2 kg at station 3, double-boxed. Your window is Friday 12 Sep, 2–3pm to 14 Banksia Street — safe-drop authorised if you're out (blue bins, side path, gate 4471#).

4:47pm · paid · Visa •••• 4242
5:04pm · picked at MEL-DC (shelf B4 + cage 2)
5:28pm · labelled · STX-88412-VIC
Now · awaiting first carrier scan
The honest bit

StarTrack's 4:30pm Melbourne pickup missed tonight — their van broke down (not your parcel's fault, and not a euphemism). Everything is re-booked on the 8:30am Saturday-vicinity linehaul, and your Friday 2–3pm window still holds. If that changes, this inbox tells you before you have to ask — no chasing required.

Live tracking · driver map from 1pm Fri Change safe-drop instructions

Behind this email

Trigger
packed scan 5:28pm + delay-flag CF-12 attach
Merge tags
{order_id} {tracking} {window} {address} {safedrop_note} {delay_addendum?}
SMS mirror
"ApexCommerce: 08412 packed. Fri 12 Sep 2–3pm to Fitzroy. Tonight's courier pickup missed — Fri window still holds. Track: apcx.au/t88412"
Addendum rule
any lane delay > 30min auto-appends the block; tone = fact first, apology second
Quiet hours
n/a (transactional) · marketing would wait till 8am
Ticket link
0 "where is it" tickets from this send (measured)

Why the amber block exists

Silence is what makes people refresh tracking pages. One honest paragraph cut "where is it" chats 11pts since July.
The safe-drop line quotes her own words back ("blue bins") — confirmation that a human read the instruction, not a form.
SMS mirror is ≤ 160 chars, one link, no marketing tail — the cap is 4/wk and this spends 2.