Where Is My Order (WISMO): Cut Tickets With Updates

How do you reduce where-is-my-order tickets?

You reduce WISMO tickets by closing the information gap between your carrier data and your customer: send a message for each delivery state, flag orders that stop moving before the customer notices, and answer the rest automatically with real tracking data.

Start by measuring your own baseline. Tag a sample of last month's tickets by reason and count how many are order-status questions. That number is your target, and it is better than any industry average. The work below connects the fulfillment steps that produce tracking to the helpdesk that answers it.

Why do customers ask where their order is?

Customers ask because the order went quiet. Between the confirmation email and the doorstep there is usually a stretch where nothing reaches them, and silence reads as risk.

Four situations produce most WISMO tickets:

• No news after purchase: the order is still in picking or waiting for stock, and nobody said so.
• A label with no scan: tracking exists, but the carrier has not picked the parcel up.
• A parcel that stopped: it was scanned, then sat for days.
• A failed or held delivery: the carrier tried once, or left the parcel at a depot, and the customer has no clear next step.

How do you detect stalled parcels before the customer does?

Detect stalled parcels with a scheduled check that compares each open shipment's last tracking event with a threshold you set per carrier and service. The check needs only the tracking data you already collect.

Shopify warns that tracking event sources, accuracy and timing vary by carrier, so treat any single scan as a clue and set thresholds from your own history. A simple build looks like this:

1. List every fulfilled, undelivered order with a tracking number, once or twice a day.
2. For each, read the last tracking event and its date from your carrier or tracking provider.
3. Compare against thresholds: days from label to first scan, days without movement, and days past the promised delivery date. Set them from your last few months of delivered orders, by carrier and service.
4. When an order trips a threshold, tag it with the problem type, such as no first scan, no movement, exception or past due. A workflow tool can do this: Shopify Flow has an action that adds a tag to an order.
5. Route the tagged orders to one queue with an owner, who contacts the carrier and decides on a reship or a refund.

What should a branded tracking page do?

A branded tracking page should answer the customer's question without sending them to a carrier site: where the parcel is, when it should arrive, what to do if it does not, and how to reach you. Treat it as the home of your delivery promise.

Shopify says its customer email notifications can be customized with your logo and brand colors. Build the page so each state reads clearly:

• Show the status in plain words, the carrier, the tracking number and the expected date.
• Explain what each status means for the customer, such as "label created, not yet picked up".
• For exceptions, offer a next step: correct the address, book a second try, or contact support with the order number prefilled.
• Use any extra space for care instructions or setup steps for what is arriving. Keep offers off the page for an order that is late or stalled.
• Check how the page looks on a phone, because that is where most customers open it.

Which message should you send for each delivery state?

Send one message per state, written for what the customer needs in that moment, and stop when the state is resolved. Shopify provides four shipping notifications as a base: Shipping confirmation, Shipping update, Out for delivery and Delivered.

Per Shopify's notification page, the Out for delivery and Delivered notices are sent when a matching tracking event arrives from the carrier or fulfillment app, and they are not available for local delivery orders. Add your own messages for the states Shopify does not cover:

• Order confirmed but delayed in processing: a short note with the new ship date and the reason in plain terms.
• Shipped: the tracking link, the carrier and a realistic window.
• Stalled: say you noticed, say what you are doing, and give a revised expectation. Do not wait for the customer to write.
• Failed delivery attempt: ask for the one thing needed, either a corrected address or a time for a second try.
• Past due: a message from a person or a clearly human-reviewed template, with the reship or refund option set by your policy.
• Delivered: a short note with the care or setup help, and a way to reach support if the parcel is missing.

Why pause marketing on problem orders?

Pause marketing on a problem order because a customer worried about a missing parcel reads a cheerful cross-sell as a brand that has not noticed. The review request, the referral ask and the replenishment offer should all wait until the order is delivered.

The stalled-parcel tag from the detection step is the switch. In your email or SMS tool, exclude profiles whose latest order carries that tag from post-purchase campaigns and flows, and remove the tag when the parcel is delivered. Check how your own tool handles tag or property filters, because the setting differs by vendor. Then test it with a dummy order so you know the pause works before a real customer depends on it.

How can helpdesk auto-replies use live tracking?

Helpdesk auto-replies use live tracking by reading the customer's order when a ticket arrives, then choosing a reply based on whether the order has tracking and how old it is. This clears routine status questions without an agent.

Gorgias documents this pattern in its auto-reply rule templates for Shopify. The template has four branches:

• A recent purchase (under 20 days) with tracking: the reply includes a tracking link and the ticket is closed.
• A recent purchase (under 6 days) with no tracking: the reply says the order is still being processed and the ticket is closed.
• An older purchase (over 5 days) with no tracking: no reply is sent, and the ticket is tagged urgent or not-shipped for a person.
• A customer with no orders: an automatic reply asks for more information.

How do you keep helpdesk auto-replies from making things worse?

Keep auto-replies safe by checking the stalled-parcel tag before the rule sends a tracking link and closes the ticket. A tracking link on a parcel that stopped moving for six days will bring the same customer back, angrier.

Gorgias notes that auto-reply rules cannot be applied to ChannelReply tickets or tickets with only an Internal Note. Add these guards on top of the template:

• Skip the auto-close when the order has a stalled, exception or past-due tag. Send it to the queue with the order details attached.
• Replace the generic link with the status you hold: the last scan, the date and what you are doing about it.
• Review a sample of auto-closed tickets every week. If customers reply to the closed ticket, the rule is answering the wrong question.
• Keep a person on anything that mentions a refund, a complaint or a damaged parcel.
• Consider an agent that can read the order and tracking data and draft the reply for the cases the rules cannot cover, such as a support agent grounded in your own answers.

Sources

Every vendor fact in this guide was read on the vendor's own page on November 11, 2026. Check the page before you rely on a setting.

• Shopify Help Center, Customer notifications. The four shipping notifications, when each is sent and the note on carrier tracking events.
• Shopify Help Center, Shipping notifications. Customer emails customized with a logo and brand colors.
• Shopify Help Center, Shopify Flow action: Add order tags.
• Gorgias Docs, Auto-Reply common Rule templates. The Shopify order status rule with its four branches.
• Gorgias Docs, Auto-reply Rule best practices. Order status rules with and without tracking, and the ChannelReply limit.

Frequently asked questions

What does WISMO stand for?

WISMO stands for "where is my order". It describes any customer contact asking for the status of a shipment, whether by email, chat, phone or a social message. Tag these tickets as one reason in your helpdesk so you can count them and see whether your updates are working.

How many WISMO tickets should I expect?

It depends on your carriers, your shipping times and how often you update customers, so measure your own. Tag a sample of recent tickets by reason, count the order-status share, and repeat the count after you change your messages. A falling count on the same ticket tagging is the proof that the updates work.

Should I proactively email customers about delays?

Yes, when the delay is real. Tell the customer you noticed, what you are doing and when to expect the order, before they write to you. Keep the message short, ask for one step only if one is needed, and hold marketing for that order until it is delivered.