Answering tracking requests automatically: the status in the reply
Published on October 9, 2026

Monday morning, 9:12. An email with the subject “Order #4711” is waiting in the inbox. Content: “Hi, I ordered last week and haven't received anything. When will the parcel arrive?” You know what comes next: find the order, copy the tracking number, open the carrier’s site, read the status, write a reply. Four minutes if nothing gets in the way. And the next email with the same content is already sitting underneath.
According to Gorgias, delivery questions are the most common category in e-commerce support, at 18 percent of incoming requests on average. They are also the category that automates most cleanly, because the answer is not in your head but in two systems: Shopify and the carrier. This article shows how Humane brings those two sources into one reply, what happens when the carrier does not know anything yet, and which delivery questions still end up with you.
If you first want to know why so many of these requests exist at all, and what you should fix in your shipping email before automating anything, read “Where is my order?” – reducing WISMO requests first. This article is about the part after that: the requests that come in anyway.
What a good reply to a delivery question contains
Before we get to the mechanics, a look at the goal. A reply to “Where is my parcel?” is good when the customer does not write again afterwards. For that it needs four things:
- The current status in one sentence, translated out of carrier jargon. “Your parcel arrived at the Hamburg sorting centre yesterday evening” instead of “Shipment arrived at destination facility”.
- An expected date, if there is one. A window is better than nothing, a date is better than a window.
- The direct link to the shipment, so the customer can check for themselves without writing again.
- One sentence about what happens if the date passes. That is how you decide when the customer gets back in touch.
An autoresponder can deliver none of these. A canned text with the tracking number inserted manages the third. For the other three, someone or something has to actually read the status.
How Humane assembles the reply
The sequence when the email above arrives:
- Categorise. The agent reads the email and classifies it as a delivery question. This is the message categorisation that runs for all tickets, not just tracking.
- Find the order. Using the sender address or the order number in the text, the agent fetches the order from Shopify. That is where the order date, items, dispatch date and the tracking number recorded at fulfilment live.
- Fetch the status. With the tracking number, the agent requests the current shipment status. Humane uses a tracking service that aggregates carriers, so DHL, DPD, Hermes or GLS are queried the same way.
- Write the reply. From status, date and your stored tone-of-voice rules, the reply is written. It sounds like your other emails, not like a form.
For the email above, it could look like this:
Hi Ms Berger, thanks for your message. Your parcel has been on its way since Friday and arrived at the delivery depot in your region this morning. Expected delivery is tomorrow, Tuesday. You can see the current status here at any time: [link to shipment]. If nothing has arrived by Wednesday evening, just reply to this email and we will take care of it.
In most cases the ticket is done with that, minutes after it arrived, not in the afternoon.
The case most tools get wrong: no scan yet
Now for the hard part. A large share of delivery questions arrives in the first one or two days after dispatch. The label is printed, the shipping email has gone out, but the carrier has not scanned the parcel yet. The tracking service has nothing.
A simple bot replies anyway in this situation: “Your shipment is on its way.” That is a claim without basis. If the parcel is in fact still on a pallet in the warehouse, you have just told the customer something false, and they will notice at the latest on their next look at the tracking page.
Humane does something different here, and this is the part we call deferral.
How deferral works
If the agent finds a tracking number that has no status yet, it does not write immediately. It registers the number with the tracking service and defers the reply. As soon as the carrier delivers the first scan, Humane receives a notification, and only then is the reply written, with the real status. In many cases that is the same evening or the next morning.
If no scan arrives within a fixed period, the agent does not wait forever. A label that is never scanned never produces a notification either. Once the period expires, the agent replies with what is true: the shipment is registered, the carrier has not picked it up in its system yet, and that usually changes by the next working day. No “on its way”, no invented date.
Two details matter to us here:
- A placeholder draft never goes out automatically. A text like “We are currently checking the status of your shipment” is a promise, not an answer. Drafts like that are not sent automatically.
- A later scan does not silently overwrite the honest reply. If the first status does arrive after the deadline, a second draft with the real status is created, which you or the agent can send. The customer does not receive contradictory emails.
That sounds like a small detail. It is the difference between a customer who believes you and one who from now on double-checks every status email.
Which delivery questions end up with you
Only what the agent can match with certainty, and what you have approved for that category, is answered automatically. Everything else is prepared as a draft and waits for you. For delivery questions, these are typically the cases:
- The order is ambiguous. Two open orders under the same address, an order number that does not exist, a request from a different email address than the one on the order.
- There is no tracking number. The order is marked as fulfilled in Shopify but without a shipment number. There is nothing to query here; you have to look.
- The status points to a problem. Delivery failed, recipient not found, shipment returned. That is no longer a status question, it is a case.
- Status “delivered”, customer has nothing. The most common conflict case in deliveries. It needs questions, a trace request with the carrier, and in the end a decision about replacement or refund.
- The customer writes a second time. Whoever asks twice is no longer curious. From here on, no canned text, but someone who takes over the case.
- The tone is angry. Humane recognises frustration and anger in the message and treats such tickets differently. Depending on your rules, they go to you.
How approval per category works, and which tickets are never answered automatically, is covered in Auto-send: which tickets Humane answers without approval.
What to check in Shopify beforehand
The automatic reply is only as good as the data it is built from. Three things are worth a look before you approve delivery questions:
- Tracking numbers are recorded at fulfilment. If your warehouse or fulfilment provider does not write the shipment number back to Shopify, the agent has nothing to work with. Then every delivery question lands with you.
- The right carrier is set. A DPD number marked as DHL returns no status.
- The shipping email names a date. The more precise your own promise, the less often people ask, and the easier it is for the agent to refer back to that promise.
How the tracking page, shipping emails and support fit together in a Shopify store is described in more detail in Order tracking in your Shopify store.
What automation cannot do here
Honestly: the agent can only read what the carrier provides. If the scan says “out for delivery” and the parcel stays in the van anyway, nobody knows until the customer writes. The agent cannot file a trace request, call a driver or dispatch a replacement without your approval. What it can do: answer the ninety identical delivery questions so that you have time for the ten that need something from you.
What you can do now
- For one week, count how many of your tickets are delivery questions, and how many of those would have needed only a standard reply with a status.
- Check whether fulfilled orders in Shopify consistently carry tracking numbers and the right carrier.
- Fix the shipping email before you automate: a date instead of a window, one sentence about the first scan.
- Approve delivery questions as the first category for automatic replies, and deliberately keep the conflict cases with you.
If you want to see how a delivery question gets answered with a real status in your own inbox: try 100 customer requests for free, no credit card, connecting your shop takes a few minutes.