WISMO Automation for Shopify: A Practical Guide
WISMO ("Where is my order?") automation connects an AI agent to your Shopify order and carrier data so it can answer order-status questions instantly. It works best as a decision flow: find the right order, screen for risk, route by shipment type, translate the tracking state, and escalate exceptions. Measure it by contacts per 100 orders and 7-day recontact rate.
Most WISMO tickets are status checks that do not need a human. The hard part is automating them safely, so a canceled, refunded, or fraud-flagged order never gets a cheerful tracking link. This guide covers what triggers WISMO, a six-step automation flow with a carrier-status mapping table, the escalation rules that keep it safe, and the metrics that tell you whether it is working.
Key Takeaways
• WISMO is the most common ecommerce support question. Gorgias reports it at 18% of incoming requests on average across its customer data.
• Salesforce estimates each WISMO ticket costs $5 to $15 in agent time and overhead, so even a mid-size store spends thousands a month answering questions its systems already know.
• Safe WISMO automation follows a fixed order of operations: filter lookalikes, find the order, screen for risk, split domestic and international, map tracking states, then reply or escalate.
• Delivered-not-received, fraud-flagged, and canceled or refunded orders should leave the automated flow by design.
• Judge success by WISMO contacts per 100 orders, containment by tracking state, and 7-day recontact rate, not by ticket deflection alone.
What is WISMO?
WISMO stands for "Where is my order?" and refers to any customer message asking about order status, shipment location, or delivery time. It ranges from "Has my order shipped yet?" to "Tracking says delivered, but I didn't get it."
WISMO tickets usually fall into three types, and each needs different handling:
- Status checks: "Has it shipped?" or "When will it arrive?" These are pure information requests, answerable from Shopify and the carrier feed.
- Delay inquiries: "Why is my order late?" or "Tracking hasn't updated." These need context, an honest explanation, and a clear next step.
- Delivered-not-received: The carrier shows delivered, but the shopper cannot find the parcel. These need investigation and usually a human decision.
How much of your WISMO volume you can automate depends on how cleanly you separate these three. Status checks can be contained almost entirely. Delivered-not-received cases should be routed to people on purpose.
Why is WISMO so expensive for Shopify brands?
WISMO is expensive because it is high-volume, repetitive, and answered by hand. Gorgias reports that WISMO accounts for 18% of incoming requests on average across its customer data, and volume climbs further in peak season when carrier networks slow down.
On cost, Salesforce estimates that each WISMO ticket costs $5 to $15 in agent time and overhead. Your own number depends on handle time and wages. MetricNet's service desk cost-per-ticket analysis illustrates the point: the same ten-minute ticket can cost $10 at one support desk and $25 at another, purely because of labor rates.
To size your own opportunity, use a simple formula:
- Count WISMO tickets for the last full month.
- Multiply by your average handle time in minutes, then divide by 60.
- Multiply by your fully loaded hourly agent cost.
At the Salesforce range, a store handling 1,000 WISMO tickets a month spends $5,000 to $15,000 answering questions that already have an answer somewhere in Shopify or the carrier's system.
What triggers WISMO tickets?
WISMO tickets are triggered by predictable information gaps between checkout and delivery. The most common are the wait between order placement and the first carrier scan, tracking that stops updating, and delays the brand never communicated.
That makes a large share of WISMO preventable before any AI answers it. The parcelLab 2025 U.S. ecommerce shipping study notes that keeping customers informed about their orders reduces WISMO calls, and it found that only about 72% of the retailers it studied email customers when a package has been delivered. It also found that more than half of online shoppers describe the period between ordering and receiving as the most emotionally significant part of the purchase.
Three proactive messages close most of the gaps:
- "Your order is being prepared" right after purchase, with your typical handling time.
- A shipping confirmation with a tracking link that goes to a branded order status page.
- A delay alert that fires when tracking has not moved for a set number of days, before the shopper asks.
If you have not set up a branded tracking experience yet, start with our guide on enabling customers to track order status on Shopify.
How do you automate WISMO on Shopify?
You automate WISMO by running every order-status question through the same six steps, in the same order, before any reply goes out. Most WISMO automations fail because they skip steps and return a tracking link for an order that was canceled, flagged, or already delivered, which is worse than no automation at all.
Step 1: Filter out lookalikes
Not every "Where's my order?" is WISMO. Before touching tracking data, separate out messages that look similar but need a different flow:
- PR and influencer shipments: route to your creator or partnerships workflow.
- Post-delivery issues: missing items, damaged products, or wrong items need their own evidence and replacement policies.
- Return and refund status: "Where's my refund?" runs on different data and belongs in the returns flow.
Step 2: Find the right order
A surprising amount of WISMO frustration starts with the wrong order on screen. Customers mistype order IDs, paste old ones, or leave them out. Search by email first, since it is usually the more reliable identifier. Only use an order ID if it matches your store's pattern. When several recent orders match, default to the most recent unless the message points elsewhere. If nothing matches after every identifier, stop and hand off to a person.
Step 3: Screen for risk and exceptions
Before replying, check whether the order belongs in the flow at all. Orders carrying fraud or payment-risk tags route to a specialist queue. Orders that are canceled, voided, or fully refunded exit WISMO entirely: the shopper needs an explanation of what happened to their money, not a tracking update. If a finance or risk system flags an order as sensitive, automation does not override it.
Step 4: Split domestic and international
International shipments have longer transit windows, more carrier handoffs, and vaguer exception codes. Build at least two branches with different "late" thresholds. A domestic order with no scan movement in five days is a problem; an international order in the same state may be normal.
Step 5: Map tracking statuses to plain-language answers
Carrier jargon like "tendered to facility" or "processing exception" means nothing to shoppers. Map every tracking state to an honest, human answer and a clear escalation rule:
| Carrier status | What it usually means | What the AI should say | Escalate? |
|---|---|---|---|
| Unfulfilled / label created | Order is still being prepared or awaiting first scan | Share typical handling time and when to expect tracking | Only if past your handling window |
| In transit, on time | Parcel is moving normally | Restate the status in everyday language, give a delivery window, link tracking | No |
| No movement past threshold | Parcel is likely delayed | Acknowledge the delay, explain what happens next and when you will follow up | Yes, past your domestic or international threshold |
| Exception / action required | Carrier needs intervention (address issue, customs, damage) | Explain there is a carrier issue and that a teammate is on it | Yes, always |
| Out for delivery | Arriving today | Confirm today's delivery and suggest safe-place checks | No |
| Delivered, not received | Misdelivery, porch theft, or early scan | Suggest neighbors, reception, and safe places, then outline claim timelines | Yes, if not found after checks |
| Returned to sender / at pickup point | Failed delivery or held for collection | Explain common reasons, share the pickup address and deadline | Yes, for returned to sender |
Step 6: Set guardrails and escalation rules
Two rules keep WISMO automation safe. First, enforce the order of operations every time: find the order, check risk, identify the route, classify the tracking state, then reply. Second, write down the handoff triggers: fraud or payment risk, canceled or refunded orders, conflicting tracking, carrier exceptions, and a shopper who has already contacted you about the same order. Keep an audit trail and review a small weekly sample so CX leads can adjust thresholds before edge cases become patterns.
Where does WISMO end and returns begin?
WISMO ends when the parcel is delivered and the shopper's question changes from "where is it?" to "can I send it back?" or "where is my refund?" Those requests run on returns-app and refund data, not carrier tracking, so they need their own flow.
Keep the handoff clean. A shopper asking about a refund on a returned order should get the return-received date and refund status, never a tracking link for the original shipment. For the returns side, including eligibility checks and exchange-first logic, see our guide to AI for handling returns and exchanges. For how WISMO fits alongside cancellations, address changes, and claims, see our hub on Shopify post-purchase automation.
How to implement WISMO automation with Rep AI
Rep AI's AI Support Agent handles WISMO through Support Skills, individual automations you switch on and configure to match your policies.
Order Status skill
When a shopper asks about an order, the agent asks for an email or order number, finds the order in Shopify, and replies with the current status, fulfillment stage, carrier, and tracking links. You can choose fallback identifiers, such as phone number, address, or zip code, for shoppers who do not have their order number handy. The full list of Rep AI Support Skills covers how each one is configured.
Adjacent skills that filter lookalikes
- Cancel Order: processes cancellations in chat, with a time limit so orders already in fulfillment are protected.
- Returns and Exchanges: connects to Loop with your Loop API key to check eligibility and share the return link in the conversation.
- Change Order Address: updates street, city, or postal code on unfulfilled orders within an hour limit you set.
The agent separates these intents automatically. "I want to return this" enters the returns flow; "Where's my package?" enters Order Status.
Training, guardrails, and escalation
You can train the agent on shipping policies, carrier timelines, and handling procedures with files and URLs, and write custom instructions for how to respond to each tracking state. When a case should not be automated, such as a fraud-flagged order or conflicting tracking, the conversation escalates to your helpdesk with full context. Rep AI's integrations include Gorgias, Zendesk, Kustomer, Freshdesk, and Richpanel.
Post-WISMO segmentation in Klaviyo
Rep AI sends conversation attributes to Klaviyo profiles, so you can build post-purchase flows on what actually happened during delivery. A shopper who had a delayed parcel can receive a different follow-up from one whose order arrived early, instead of everyone getting the same timer-based review request.
How do you measure WISMO automation?
Measure WISMO automation by whether contacts are prevented and resolved the first time. Fewer tickets alone do not prove it works: a system that deflects tickets but leaves shoppers confused shows up later as recontacts and refund leakage.
| Metric | Formula | Target behavior |
|---|---|---|
| WISMO query rate | WISMO tickets ÷ orders shipped × 100 | Trending down as proactive messages and automation mature |
| Containment rate | WISMO conversations resolved with no human reply ÷ all WISMO conversations | High for in-transit states; intentionally low for delivered-not-received |
| First response time | Time from shopper message to first meaningful reply | Instant for status checks; fast human takeover for exceptions |
| Refund and reship leakage | Orders refunded while in transit, or both refunded and reshipped ÷ WISMO orders | Falling as tracking-state logic tightens |
| 7-day recontact rate | Shoppers who ask again about the same order within 7 days ÷ resolved WISMO conversations | Low; a rising rate means answers are not setting expectations |
| CSAT | Average rating on WISMO conversations | Read together with recontact rate, never alone |
Break containment down by route and tracking state. A strong overall number can hide a failing international branch. Track WISMO query rate and leakage in your helpdesk and order systems, and use your AI platform's analytics for AI-versus-human resolution and CSAT.
Common WISMO automation mistakes
- Sending a tracking link to every "where is my order?" even when the order is canceled, flagged, or already delivered. Always run risk and status checks first.
- Using one delay threshold for every route. International shipments need longer windows, or your agent will escalate normal transit times.
- Copying carrier wording into replies. "Processing exception" creates a second ticket. Translate every state into what it means and what happens next.
- Treating delivered-not-received as a status check. It is an investigation, and it needs a human path with claim timelines.
- Skipping measurement. Without recontact rate and refund leakage, you cannot tell whether automation is resolving issues or hiding them.
What to expect after automating WISMO
WISMO is structured, repetitive, and driven by a small set of signals, which makes it one of the safest support workflows to automate and one of the quickest to show results. Routine in-transit questions are contained almost entirely, while delivered-not-received and exception cases go to people by design.
Across its customers, Rep AI reports a 50–70% reduction in support tickets. As one example, VIBAe handles "Where is my order?" questions instantly in chat while supporting shoppers in 150 countries, with a 97% resolution rate and 99% customer satisfaction. The bigger shift is what your team does with the time: faster replies on complex tickets and tighter control over refund leakage in peak season.
FAQs
What does WISMO stand for?
WISMO stands for "Where is my order?" It covers any customer question about order status, shipment location, or expected delivery time, from simple status checks to delay inquiries and delivered-not-received cases. It is one of the most common and repetitive ticket types in ecommerce support, which makes it a strong candidate for automation.
How much do WISMO tickets cost?
Salesforce estimates each WISMO ticket costs $5 to $15 in agent time and overhead. Your actual cost depends on handle time and wages, so calculate it as monthly WISMO tickets times average handle time times your loaded hourly agent cost. At that range, 1,000 tickets a month costs $5,000 to $15,000.
Which WISMO tickets should not be automated?
Route fraud-flagged or payment-risk orders, canceled or refunded orders, conflicting or stalled tracking past your threshold, carrier exceptions, and delivered-not-received cases after initial checks to a human. The AI should collect the order details first so the agent can resolve the case quickly.
How do you reduce WISMO tickets before they happen?
Send three proactive messages: an order-being-prepared note with your handling time, a shipping confirmation with a tracking link, and a delay alert when tracking stops moving. The parcelLab 2025 shipping study notes that keeping customers informed reduces WISMO calls, and many retailers still skip the delivered notification.
How do you measure WISMO automation success?
Track WISMO tickets per 100 orders shipped, containment rate by tracking state and route, first response time, refund and reship leakage, and 7-day recontact rate on the same order. Pair CSAT with recontact rate, since a shopper who asks again was not really helped.
How does Rep AI handle WISMO on Shopify?
Rep AI's Order Status skill asks for an email or order number, finds the order in Shopify, and replies with fulfillment stage, carrier, and tracking links. Adjacent skills handle cancellations, address changes, and Loop-powered returns, and exceptions escalate to your helpdesk with full conversation context.
WISMO automation pays off when it follows a strict order of operations, escalates the right exceptions, and is measured on recontacts as well as deflection. To see how Rep AI handles order-status questions on your own store, start your 14-day free trial. No credit card is required, and you can cancel anytime.
More from REP AI
AI Shopping Assistant: How It Guides Ecommerce Shoppers in 2026
When a shopper hesitates, timely guidance can help them decide what to explore next. An ai shopping assistant can answer product questions, narrow choices, and guide product discovery without taking control of checkout. Shoppers get help comparing options, while still making the purchase decision th...
Benefits of Agentic Commerce: How AI Can Help Brands Sell and Serve Better
When a shopper hesitates, a useful answer can turn a moment of uncertainty into a chance to help, rather than a sale lost or a question left unanswered. The benefits of agentic commerce come from connecting shopper intent with timely action, then learning from those interactions to improve sales gui...
Want to see what your store would do with Rep?
Run your real Shopify catalog through the simulator before you commit to anything. No sales call required.
