The order shipped Monday; by Wednesday the tracking shows nothing new; by Thursday the customer is messaging. The mid-transit silence is the anxiety window — technically normal, experientially broken. The communication that bridges it.
Why tracking goes quiet
The parcel's linehaul leg generates few scans — loaded, moved, unloaded at the destination hub. Two days of 'in transit' means it's on a truck; the customer reads it as 'lost'. The data is normal; the display is alarming.
The mid-transit update
An automated 'your parcel is in transit, expected [date]' on day 2–3 fills the silence — no new information needed, just reassurance it's moving. The ticket-deflection value is real: sellers who send mid-transit pings report meaningfully fewer WISMO messages.
The ETA display
Showing 'expected delivery [date]' prominently answers the real question — customers don't want scan events, they want the date. An ETA that updates from carrier data (rather than a static promise) is the honest display.
The escalation threshold
If the parcel exceeds expected-transit by a margin (day 5 on a 3-day lane), proactive outreach beats waiting for the ticket — 'we've flagged a delay, chasing the courier, here's the new ETA'.
Pakka Parcel runs the whole stack described here — one place for every carrier.
See how →The playbook
Send a mid-transit update
Day 2–3 'still moving' message fills the silence.
Show the ETA, not just scans
'Expected Thursday' is what they actually want.
Flag true delays proactively
Day+3 silence earns an honest flag.
Update the ETA live
Carrier data flowing into the display date.
