WISMO automation: a “where is my order” ticket means your customer found out first.

A WISMO ticket reads like a simple question. “I ordered two weeks ago and the tracking hasn't moved. Did it ship?” For most Shopify brands it's the biggest pile in the inbox, and it shows up every day whether sales are up or down.

Most teams file it under support volume and try to answer it faster. That's the wrong read. By the time someone writes in, they've usually checked the tracking page already and seen nothing new. The package stalled days ago. The ticket is just the moment the news finally reaches you, and it arrives with a customer who's already irritated.

Start with what Shopify already gives you. Make sure the shipping confirmation, shipping update, out for delivery, and delivered notifications are all switched on, state your processing and shipping times plainly in your shipping policy and at checkout, and make the order status page easy to reach from every email. If any of those are missing, fix that first. It costs nothing, and it heads off the tickets from customers who simply didn't know where to look.

The limit is that all of it only repeats what the carrier reports. When a package stops getting scanned, the status page keeps showing the last update, and nothing tells anyone the order has gone quiet.

Past the basics, most brands add a branded tracking page, an order-lookup bot, and a saved reply your team can send in ten seconds. Those help too: tickets close quicker, and some never get opened because the customer finds the tracking link on their own.

But every one of them waits for the customer to get worried first. And a worried customer doesn't read a tracking page the way you do. “In transit” for four days reads as lost. A bot that cheerfully says “your order is on its way” when it plainly isn't moving makes the next message angrier.

Pull a month of order-status tickets and sort them by what actually happened to the order. Most of them land in four buckets, and each one leaves a trace in data you already have. The leftovers tend to be address mistakes, backorders, and customs holds, which are worth their own messages but show up far less often. Peak season and international orders make every bucket bigger, so it pays to measure November and December separately.

The hard part is knowing what normal looks like. A single fixed rule like “flag anything with no scan in three days” fires constantly on a slow ground service and misses real trouble on a fast one. Each carrier and each warehouse has its own pace, and the check has to know it. Your own shipping history already has that pace in it, carrier by carrier. Pull the numbers, then refresh them every month or so.

A Wednesday morning, before the support inbox opens:

• Overnight tracking events come in for every open order, whether that's one store or several.
• Fourteen orders have gone longer without a scan than their carrier normally does. Feeds sometimes pass scans along late, so the system asks each carrier directly. Five had scans the feed hadn't delivered yet and drop off the list. Nine are still stuck.
• Two of the nine are repeat customers on large orders. Those go to a person, with the order history and tracking already attached.
• The other seven get a delay email drafted in the brand's voice, with the carrier's new estimate filled in where there is one.
• One split shipment turns up where box one landed yesterday. Its customer gets the tracking for box two.
• Someone on the team skims the drafts, approves them, and they go out before the support inbox opens.

None of those customers had to ask. Most will read the email and wait for the next update.

Catching the delay only helps if the email that follows is good. A vague “your order has been delayed, we apologize for any inconvenience” email can create the ticket it was meant to prevent, because it raises the question without answering it.

The version that works tells the customer what happened, when they'll hear from you next, and what you'll do if it doesn't fix itself. Something like this:

• Say what happened in plain words. “Waiting at a carrier facility” is clearer than “experiencing a delay.”
• Give a date. If the carrier won't give one, give the date you'll check back.
• Say what you'll do next, so the customer doesn't have to ask.
• Sign it from a person, and let replies go to a real inbox. If they can reply to Jess, they get a quick answer. A no-reply address just pushes them to open a ticket.
• Keep it short enough to read on a phone in the checkout line.

To see whether any of this is working, track one number, your WISMO rate: order-status tickets divided by orders shipped, every week. Split it by carrier and by the four signals above, and it will show you which one is driving your volume.

• Order and fulfillment data from Shopify, every store in one place, so an order is one record even when it ships from two warehouses.
• Tracking events straight from the carriers, through their own tracking feeds, so a stalled package shows up the same day rather than whenever someone checks. Tracking isn't perfect. Handoffs between carriers, regional carriers, and labels made outside Shopify can lag or go quiet, which is why the check asks the carrier again before anything gets sent.
• A normal pace for each carrier and each warehouse, measured from your own shipping history.
• Message templates written in your voice, with the dates filled in from tracking and a fallback line for when the carrier gives no estimate.
• An approval step. At first someone reviews every message. Once the team trusts it, the routine ones go out on their own and only the odd cases wait.

Shopify gives you the order data. Everything else, the monitoring, each carrier's pace, and the drafts, is what gets built on top.

We run this for a multi-store e-commerce brand today: shipment monitoring across every storefront, carrier exceptions caught early, and delay emails drafted before the customer notices. It's the proactive half of our e-commerce customer support automation. It also shares its data with Shopify inventory forecasting, since supplier delays and carrier delays both push back the date the customer was promised.