Delivered but Not Received: AI for Delivery Exceptions
A delivery exception is a parcel that tracking says is somewhere the customer says it is not. Marked delivered, and the customer has nothing. On its way back to the sender, and the customer never refused it. These are different from an ordinary "where is my order" message, which is answered by reading the tracking page. An exception needs someone to contact the carrier. This is how the system in our case study separates the two and handles the second.
Exception or status question?
The agent reads the carrier's tracking and classifies the request:
- Status question: the parcel is moving, or simply slow. The reply gives the latest status and the delivery time the policy states. See where-is-my-order requests.
- Exception: tracking shows delivered and the customer reports no parcel; or tracking shows the parcel being returned to the sender.
The line matters because the two get different replies. A customer whose parcel is moving normally should not be told that the carrier is being contacted. That sentence, sent as a habit, creates an expectation of a follow-up that nobody will write. In our system the carrier-check sentence appears only when tracking shows a real exception, and the definition of an exception is written in one place.
What the reply to an exception says
Three things, in this order:
- The latest tracking event, with its date and place, as the carrier shows it.
- That we will check with the carrier.
- That we will reply within 24 to 48 hours with what the carrier says.
The time window is stated because a customer with a missing parcel needs to know when to expect news. It is written in one place in the reply rules, and every part of the system refers to that place.
The reply does not ask the customer to chase the carrier, and it does not offer a refund or a reshipment at this point. Those are decisions for a person after the carrier has answered.
The promise creates a task
"We will check with the carrier" is only true if someone does. The reply and the task are tied together: a carrier check enters the execution list under delivery exception checks, which has a named owner. When an agent approved the reply, a short message also goes to the shipping team's group chat: one paragraph, once per case. The same order is not posted twice, and a correction does not produce a second post.
The AI sends this kind of reply on its own for the two clear cases, delivered-not-received and returned-to-sender. Those replies go through the "AI review" queue, and the carrier-check task is written to the execution list after the reviewer approves.
When tracking cannot be read
Carrier websites fail, and some refuse automated requests. When the lookup does not succeed, the agent has no current status. It does not write that there has been no movement since the last event it saw, because it does not know that. A reply built on a failed lookup is not sent automatically. It goes to a person.
Lookups also need a limit. During one test we queried a carrier's public tracking site dozens of times within 20 minutes, and the carrier blocked the server for a quarter of an hour, which also stopped lookups for live customers. Tracking results are now cached, and tests keep their request count low.
Telling the customer before they ask
The system also sends order-status notices on its own initiative, before the customer has written, and opens a ticket for each. In the 30 days to 19 November 2026, 738 tickets were opened by such notices. One rule we corrected: the clock for "unresolved for seven days" starts when the customer first replies, not when the notice was sent. A notice the customer never answered is not an overdue case.
After the carrier answers
The carrier's answer leads to a decision: wait, reship, refund, or file a claim. The agent drafts the reply with the proposed solution, and a person approves anything that costs money or sends goods. An approved reshipment goes to the execution list for reshipments and to the after-sales team's group chat. Each decision is recorded on its own line in the ledger.
In chat
The chat reads tracking and tells the customer what it shows. When the customer says the parcel marked delivered has not arrived, the chat does not promise an investigation result or a replacement. It creates a ticket with the order, the tracking status and the customer's statement, and gives the ticket number and the follow-up email address.
What to measure
- How many exception replies were followed by a second reply within the promised 48 hours.
- How many "we will check with the carrier" sentences were sent on parcels with no exception. The target is zero.
- Failed tracking lookups, by carrier.
- Exceptions by carrier and by destination country, which shows where parcels go missing.
Who this fits
Stores that ship large or high-value parcels, ship across borders, or use several carriers, where each missing parcel is expensive and the carrier has to be contacted by a person.
Related: connecting orders and shipping and address changes and cancellations. Send us your list of carriers and the free plan maps the exception flow within two working days.