"Where is my order?" is a design problem, not a support problem

A typical store sends an order confirmation, then nothing until a shipping notification with a tracking number, then nothing again. Between those gaps the customer has no idea whether anything is happening, and the natural response to uncertainty about money already spent is to ask. Filling the silence with three honest updates removes most of the contacts: dispatch expectations at order time, a real notification when it ships, and a heads-up if something slips.

• Confirmation that states when dispatch will happen
• A shipping notification with a link that actually works
• A proactive message when something is delayed
• A delivery confirmation that invites the next step

A raw carrier tracking number pasted into an email asks the customer to leave your store, find the right carrier site and paste it into a form. Many will get it wrong, and the ones who succeed end their journey on somebody else's page. A tracking page on your own domain, with order status, carrier updates, the expected date and a link back into your catalog, keeps the visit yours and gives you a legitimate touchpoint on a page a waiting customer opens three or four times before the parcel arrives. Below roughly 100 orders a month it is not worth building; a well-written shipping email does the same job.

Most WISMO contacts would be resolved by a page the customer can reach without logging in: order status, items, delivery estimate, tracking, and links to start a return or contact support with the order already attached. Guest checkout makes this harder and more important. A secure order-lookup link in the confirmation email covers customers who never created an account, which in most stores is the majority. Building this well belongs in the same layer as the rest of the storefront, and it is one of the highest-return pages you will ever add.

A delay you announce is an inconvenience. A delay the customer discovers by waiting is a broken promise. Detect exceptions (no carrier scan within 48 hours of dispatch, a carrier-reported problem, an address issue) and message first with what you know and what you are doing. Doing this consistently heads off refunds requested out of frustration, because most people are reasonable about delays and unreasonable about silence.

A delivery confirmation gets opened, because the recipient is genuinely interested at that moment and nothing else in your sending schedule can say that. That makes it the natural place for care instructions, a complementary product suggestion or a reorder reminder for consumables. Time the review request to arrival plus a few days, not to the order date: asking about a parcel somebody has not opened is how you collect two stars about shipping. Used well, the post-purchase sequence turns into a retention channel where it used to be a cost, the same argument made in email and retention.

Reliable tracking numbers written back into the order, ideally by an integration and not by somebody pasting them; order statuses that reflect physical reality, where most reflect an internal workflow; transactional email that actually arrives, which means a sending service with SPF, DKIM and DMARC configured on the domain, never PHP mail from the web server; and a status page that loads fast on a phone, since that is where it will be opened. None of this is exotic, and all of it fails quietly if nobody checks it after a plugin update.

If your fulfillment is same-day, your volume is small and WISMO messages are rare, a good confirmation email and a working tracking link are enough. This becomes worth real investment when order volume makes support time expensive, when delivery times are long enough to create anxiety, or when you sell internationally and the wait is measured in weeks. Count your WISMO contacts for two weeks before deciding. The number usually settles the argument by itself.