Not every unusual tracking event needs the same response. A missing scan on an international route may need observation, while a failed delivery may need an address check today.
Four useful exception groups
Review delays, long periods without a scan, delivery failures, and delivered-but-not-received complaints as separate groups. The distinction gives support a clear next step.
Use the latest checkpoint and dwell time
BestTrack shows the latest checkpoint, destination, transit time, and dwell time. These fields help support explain what happened without copying a carrier code that customers cannot interpret.
Set a review time for each group
Review delivery failures first. Recheck long no-scan periods on a schedule. Keep delayed orders visible until they receive a new event or pass the store’s promised delivery window.
Keep the message tied to the action
Tell customers what the store is doing and what they can do next. A failed delivery may need an address confirmation. A normal transit delay may only need a new review time.
Build one exception queue
Filter Exception, Delivery Failure, and Not Found orders in BestTrack. Give each group an owner and a next review time, then use the same structure in your customer replies.
