WISMO stands for "Where Is My Order?", the single most common question in e-commerce support. WISMO tickets commonly account for 25-50% of total ticket volume (industry reporting). Each one is a customer anxious about money already spent, and each is almost perfectly automatable, because the answer lives in your order system.
Why do customers send so many WISMO messages?
WISMO is not a customer patience problem; it is an information gap. The customer paid (or committed to pay on delivery), and now their money is in limbo. Typical triggers:
-
No tracking, or tracking that never updates. "Shipped" for four days with no movement generates a message on day two.
-
Vague delivery promises. "3-7 business days" invites a check-in on day three.
-
COD anxiety. With around 45% of Middle East shoppers preferring cash on delivery (Go-Globe), many customers have committed to a doorstep payment and want certainty about when to be home.
-
Marketplace-trained expectations. Customers used to hour-by-hour tracking apply the same standard to independent stores.
In MENA inboxes the question arrives in every register at once: "Where is my order?", "الأوردر فين؟" (el order fein?, Egyptian), "وش صار على طلبي؟" (wesh sar 3ala talabi?, Saudi), or in Arabizi: "el order wesel fein?".
What does WISMO actually cost a store?
-
Agent time. At 25-50% of volume, WISMO is usually the largest single block of repetitive work. Every lookup, copy, paste cycle is minutes an agent does not spend on a sale or a complaint.
-
Queue contagion. WISMO floods slow down every other ticket, so complaints and pre-sale questions (the messages that need humans) wait behind status checks.
-
Trust erosion. A slow answer to "where is my money's worth?" reads as evasion. Slow WISMO handling is a common root of chargebacks, cancellations, and refused COD deliveries, which sting doubly in a region where COD returns run roughly 12-13x card returns in the UAE (Quiqup).
How do stores fix WISMO?
1. Prevent it: proactive updates. Confirmations, shipping notifications with tracking, and out-for-delivery alerts on the channels customers actually read (in MENA, that means WhatsApp and Instagram, not just email) remove the reason to ask.
2. Automate the answer. The remaining questions should be answered by a system connected to live order data. The bar is: customer asks in their own words and language, system identifies the order, and replies with the real status and date in seconds. Keyword bots that reply "please check your email for tracking" do not clear the bar; they convert one WISMO message into two.
3. Route the exceptions to humans. Lost parcels, wrong addresses, and courier disputes are not WISMO; they are incidents. Good automation recognises the difference and hands over with context.
For MENA stores there is a language gate in front of all of this: a WISMO bot that cannot read Gulf dialect or Arabizi will miss most real WISMO messages. That gap is why generic tools underperform here; see Arabic AI Customer Support: Why Dialects Matter.
How does ReplAi handle WISMO?
ReplAi connects to Shopify and answers order-status questions from live fulfilment data, in the customer's own language: Egyptian, Gulf, or Levantine Arabic, English, or Franco-Arabic, with gender-aware phrasing, on Instagram DMs, Messenger, WhatsApp Business, and WebChat. Replies average under 14 seconds, 24/7, and across our merchant cohort 80% of messages are fully automated (Q1 2026). For stores doing 1,000+ orders a month, where WISMO volume is heaviest, that translates to 70-80% automation and 4-8 team hours saved per day.
A customer can write "وش صار على طلبي" at 1am and get the actual courier status in Saudi dialect before she puts the phone down. Setup takes about 10 minutes; book a demo or see pricing.
Frequently asked questions
Is WISMO really worth automating before anything else?
Usually yes, for arithmetic reasons: it is the largest homogeneous slice of tickets (commonly 25-50%), it needs no judgment, and the data to answer it already exists in your store backend. It is the fastest automation win with the least risk, which is why it is the standard entry point.
Does proactive notification eliminate WISMO completely?
No, it roughly thins it. Some customers do not open notifications, some ask before the first update, and delivery exceptions always generate questions. Prevention plus automated answers together get you to the point where only genuine incidents reach humans.
How is WISMO different in COD-heavy markets?
The stakes are higher on both sides. The customer plans to hand cash to a courier, so timing certainty matters more, and the store risks a refused delivery if the customer loses confidence or is not home. Fast, accurate WISMO answers directly reduce failed COD deliveries, one of the costliest failure modes in MENA e-commerce.
What metric tells me my WISMO handling improved?
Watch the WISMO share of total tickets reaching humans (should fall toward zero), median time to a status answer (should drop to seconds), and repeat-ask rate (customers asking twice about the same order). Downstream, watch refused COD deliveries and support CSAT; both track WISMO quality closely. For measuring satisfaction in chat, see What Is CSAT and How Do You Measure It in Chat Support?