A store selling a few hundred orders a week has one person handling support. She estimates that most of her day is order status.
The information exists. It is in the order record, the fulfilment system and the carrier's tracking. None of it is reachable by a customer who is looking at the store's website at nine in the evening.
So they email. She answers each one by opening three tabs and copying a tracking number that was already sent to them in an email they did not see.
The first failure: the tracking email is missed
Filtered, buried under marketing messages or sent to an address the customer does not check. The single largest source of the question.
The second failure: the carrier page is not understandable
A page of scan events with no plain statement of when the parcel will arrive leaves the customer no better informed than before.
The third failure: nothing happens when a parcel stalls
The customer notices before the store does. A silent gap of three days generates a worried email and frequently a refund request.
The fourth failure: delays are not communicated
The single most preventable cause of anger. Customers accept a delay they were told about and do not accept one they discovered.
The fifth failure: status is not available on the store itself
The customer is on the site, and must go to their email to find a link to a third party page. Each step loses people into the inbox.
The sixth failure: the pre purchase version is ignored
When will it arrive, asked before buying, which is the ground in shipping cost questions before the cart.
The seventh failure: the split shipment is unexplained
A customer receiving one of three items assumes an error, and without an explanation this becomes a complaint rather than a question.
The eighth failure: the international orders generate more of everything
Customs delays, duties and longer transit, all of which produce status enquiries that a domestic process never anticipated.
The ninth failure: the enquiries arrive outside working hours
Evenings and weekends, when people are at home thinking about their parcels, and nobody is there to answer.
The tenth failure: the same customer asks three times
Because nothing changed between asking and no update was offered, which is entirely avoidable with a single notification.
The eleventh failure: the support person becomes a lookup service
Skilled time spent copying tracking numbers, which is the pattern described in where is my order questions that flood dtc inboxes.
The twelfth failure: the returns window interacts with the delay
A customer whose parcel arrived late is measuring the return period from a date they did not expect, and a store that handles this rigidly turns a delivery problem into a refund dispute. Stating how the window works when something was delayed defuses it entirely.
The thirteenth failure: the discount and returns questions pile up behind it
A queue full of status enquiries delays everything else, including the ones in discount code questions and why they backfire.
The fix: answer on the store, and let notifications tell people before they ask
An assistant on the store that explains when orders despatch and how long delivery takes, tells customers which email the tracking link arrives in and to check their spam folder, explains split shipments and how the returns window works after a delay, and collects the order number and email for anything specific removes a large share of a support inbox. It cannot look up an individual order or message the customer when something changes, so those updates still come from your store and carrier notifications, but nobody has to email just to get the general answer. Adding it to the store is covered under integrations. The mechanics are set out in how to use a chatbot for order tracking. Start at try, see features, and the sector view sits under ecommerce.