WISMO (Where Is My Order?) refers to customer service inquiries asking about order status or tracking information. WISMO tickets represent the largest category of ecommerce support volume, often accounting for 40β60% of all inquiries. Reducing WISMO is achieved through proactive shipping notifications and self-service tracking tools.
WISMO tickets are the silent drain on ecommerce operations. They consume support resources, frustrate customers, and represent work that shouldn't exist in the first place. The solution isn't hiring more agents or responding faster: it's eliminating the need for customers to ask by providing information proactively. ShippyPro Notifications help merchants reduce WISMO by up to 65% through automated shipping updates via Email, SMS, and WhatsApp, triggered by real-time carrier tracking events across 190+ carriers.
WISMO stands for "Where Is My Order?" β the question customers ask when they don't know the status of their purchase. It's the most common customer service inquiry in ecommerce, representing the single largest category of support volume for most merchants.
A WISMO inquiry can take many forms:
Each of these questions represents the same underlying problem: the customer lacks visibility into their order status. They're asking because they don't know, and they don't know because the information wasn't provided proactively.
It's important to distinguish between WISMO (informational inquiries) and actual delivery issues:
WISMO tickets are requests for information that already exists. The order shipped, it's in transit, the tracking is available β the customer simply doesn't have easy access to it or doesn't understand what it means.
Delivery issue tickets involve real problems: lost packages, damaged goods, incorrect addresses, customs holds. These require investigation and action.
The distinction matters because WISMO tickets are entirely preventable through better communication, while delivery issues require problem-solving. Most merchants conflate the two, treating all shipping-related tickets as inevitable. In reality, 40β60% of shipping inquiries are pure WISMO β questions that could have been prevented with proactive notifications.
Understanding why customers contact support is the first step to eliminating those contacts. WISMO inquiries fall into several categories:
Carrier tracking pages are notoriously confusing:
Customers don't speak carrier language. When they can't interpret what they see, they contact support for translation.
Some customers check tracking obsessively regardless of how much information you provide:
Anxiety drives behaviour. When customers feel uncertain, they seek reassurance β even if the shipment is progressing normally.
Sometimes there's a real problem:
These are legitimate support tickets. The issue isn't that customers ask β it's that they often don't know a problem exists until they proactively investigate.
Customers have learned to distrust tracking information:
This scepticism leads them to contact support for "real" confirmation.
WISMO isn't just annoying β it's expensive. Understanding the full cost helps justify investment in prevention.
Most merchants calculate WISMO cost based on average handling time alone. But the real figure includes delayed responses to genuine delivery problems (which escalate into refunds and negative reviews), repeat contacts from the same customer, and the opportunity cost of every hour your team spends on information retrieval instead of value-adding work. A conservative calculation typically reveals 2β3Γ the headline cost.
Each WISMO ticket requires:
Average handling time: 3β5 minutes per WISMO ticket. For delays or exceptions, the same ticket often resurfaces over multiple days, compounding the cost further.
| Weekly WISMO Volume | Monthly Agent Hours | Monthly Cost (at β¬20/hr) | Annual Cost |
|---|---|---|---|
| 30 tickets/week | ~10 hours | ~β¬200 | ~β¬2,400 |
| 100 tickets/week | ~33 hours | ~β¬660 | ~β¬7,920 |
| 300 tickets/week | ~100 hours | ~β¬2,000 | ~β¬24,000 |
| 500 tickets/week | ~167 hours | ~β¬3,340 | ~β¬40,080 |
Industry benchmark data (reported by enterprise merchants in ShippyPro's pilot cohort) puts the all-in cost at approximately β¬4 per tracking-related support ticket β accounting for agent wages, tooling overhead, and escalation handling. A mid-size merchant with 300 tracking tickets per week faces a support cost of roughly β¬57,600 per year on WISMO alone.
Beyond agent time, WISMO creates hidden costs:
Delayed response to real issues: When support queues are filled with WISMO, customers with actual problems wait longer. This affects satisfaction and increases escalations.
Customer frustration: Customers shouldn't have to ask. Even when they get a quick, helpful response, they've experienced friction that shouldn't exist.
Repeat contacts: One WISMO inquiry often leads to more. "Thanks for the tracking link" followed by "It still says in transit β any update?" followed by "When should I expect it?"
Negative reviews: "Hard to get tracking information" and "Had to email support just to find out where my order was" appear in reviews, affecting conversion.
Every hour spent on WISMO is an hour not spent on:
WISMO reduction isn't just cost savings β it's resource liberation.
ShippyPro automates proactive shipping notifications across Email, SMS, and WhatsApp β so customers always know where their order is before they think to ask.
The fundamental solution to WISMO is simple: tell customers what they want to know before they ask.
This requires a shift from reactive to proactive communication:
Customer wonders where their order is. They search for the tracking email, can't find it, open a ticket. Agent looks up the order, retrieves tracking status, writes a reply. Customer follows up with a second question. Repeat.
Carrier event fires. ShippyPro automatically sends a branded SMS or email with tracking status and estimated delivery. Customer knows where their order is. No ticket opened. No agent time spent.
Effective WISMO reduction requires notifications at key moments:
Each notification answers a predictable question at the moment customers would start wondering. ShippyPro's shipping notifications trigger automatically from real carrier events across 190+ carriers, so the communication is always accurate and timely.
Proactive notifications work because they:
Reduce uncertainty: Customers know what's happening without having to investigate.
Build trust: Communication demonstrates that you're watching out for them.
Transfer control: Information gives customers agency β they can plan around delivery.
Prevent anxiety escalation: Small worries don't have time to become big concerns.
Create positive touchpoints: Each helpful notification is a mini-interaction that reinforces your brand.
Not all notifications are created equal. These four have the highest impact on WISMO:
What it communicates: "Your order is on its way."
WISMO it prevents:
What to include:
Timing: Send when label is created or when carrier picks up the package.
Channel: Email β customers want this in a format they can reference later.
ShippyPro Notifications: Automatically triggered when shipment status changes to "shipped" across any of 190+ carriers.
What it communicates: "Your package arrives today."
WISMO it prevents:
What to include:
Timing: Send as soon as carrier marks package "out for delivery" β typically morning.
Channel: SMS or WhatsApp β this is time-sensitive. Customers need to see it now, not when they eventually check email.
What it communicates: "Your package has arrived."
WISMO it prevents:
What to include:
Timing: Send when carrier confirms delivery.
Channel: Email β this is a milestone notification, not urgent. Also a good opportunity for follow-up engagement.
What it communicates: "Something happened with your delivery β here's what's going on."
WISMO it prevents:
Why this is critical: Exceptions are when customers worry most. Without proactive communication, they discover problems by repeatedly checking tracking or by noticing their package never arrived. By then, frustration has built up.
What to include:
Timing: Send as soon as exception status appears.
Channel: SMS or WhatsApp for urgent exceptions requiring action. Email for informational delays.
| Channel | Open Rate | Best For | Watch Out For |
|---|---|---|---|
| 20β40% | Shipped, Delivered, detailed exception explanations | Spam filters, crowded inboxes, not real-time | |
| SMS | 98%+ | Out for Delivery, failed delivery attempt, urgent exceptions | Per-message cost, character limits, opt-in requirements |
| 90%+ | Out for Delivery (with media), exceptions requiring customer action | Template approval process, requires WhatsApp Business API |
Strengths:
Weaknesses:
Best for:
Strengths:
Weaknesses:
Best for:
Strengths:
Weaknesses:
Best for:
The optimal approach uses multiple channels strategically:
ShippyPro supports all three shipping notification channels from a single interface, with workflow logic to route notifications appropriately.
Proactive notifications reduce WISMO significantly, but customers also need a destination for self-service tracking. A branded tracking page complements notifications by:
Instead of hunting through emails or carrier websites, customers have a single destination. Include tracking page links in all notifications and make it accessible from their account page.
Your tracking page can show:
Generic carrier tracking pages are a dead end. Your branded tracking page can include:
Customers visit branded tracking pages an average of 3β4 times per order. That's high-intent attention you already have. Use that space to surface complementary products, a loyalty programme prompt, or a review request triggered after confirmed delivery β all of which ShippyPro's Track & Trace supports natively.
Your tracking page provides visibility into customer behaviour:
This data helps optimise notification timing and content.
European merchants face specific WISMO challenges:
European logistics involves many carriers:
Each carrier has different tracking formats and notification capabilities. Without centralised management, customers have inconsistent experiences β some get helpful updates, others get nothing. ShippyPro's shipping platform normalises tracking data from 190+ carriers into consistent notification workflows, regardless of which carrier handles each shipment.
International orders within Europe generate specific WISMO inquiries:
Cross-border shipments benefit from additional notification touchpoints and clearer explanations of international shipping stages. When those notifications still don't prevent a ticket from opening β especially in markets with high WISMO sensitivity like Italy and Spain β the ability to resolve that ticket automatically inside Zendesk becomes particularly valuable (see the section below on Tracking Solver).
European merchants often serve customers in multiple languages. WISMO increases when customers receive notifications in languages they don't understand or when tracking pages display foreign-language status updates. Multi-language notification templates ensure every customer receives updates in their preferred language. Tracking Solver, ShippyPro's Zendesk AI agent, also generates draft replies in the language of the incoming ticket β useful for teams managing support across multiple markets from a single queue.
Cash on Delivery remains popular in Italy, Spain, and other European markets. COD shipments generate specific WISMO:
Pre-shipping confirmation notifications reduce COD-related inquiries and failed deliveries.
Understanding industry benchmarks helps set goals and measure progress:
Implementing WISMO reduction doesn't require a massive project. Here's a practical roadmap:
Count your weekly support tickets, classify what percentage are WISMO vs. real delivery issues, note your average response time, and document what notifications (if any) customers currently receive. This baseline lets you measure improvement and calculate ROI.
Review what customers receive today. Are you sending shipping confirmation with tracking? What do those notifications look like? Where are the gaps β moments where customers receive nothing?
Integrate your ecommerce platforms (Shopify, WooCommerce, Magento, PrestaShop, marketplaces) and carriers (DHL, UPS, FedEx, GLS, DPD, BRT, Poste Italiane, Correos, Royal Mail) with a notification system. ShippyPro provides native integrations with 80+ sales channels and 190+ carriers.
Start with: Shipped (Email), Out for Delivery (SMS or WhatsApp), Delivered (Email), Exception (SMS for urgent, Email for informational). Don't over-complicate the first implementation β get these four working before adding complexity.
Content matters: "Your order is on its way" not "Shipment manifest created." "There's been a delay β here's what's happening" not "Exception: 5110." Include the tracking link, estimated delivery, and what to do if there's a problem.
Place test orders through each sales channel, ship via each carrier, verify notifications trigger correctly. Then roll out and track: notification open rates, WISMO ticket volume (should decrease within 1β2 weeks), customer satisfaction scores.
Use data to improve. Adjust timing if notifications arrive too late. Refine content based on tickets that still come through. Add channels or notification types as needed. A/B test subject lines and content.
Proactive notifications prevent the majority of WISMO tickets from opening in the first place. But some will always get through β customers who miss notifications, prefer to confirm with a human, or contact support before a status update has fired. For those tickets, the conventional workflow is expensive: agents switch between Zendesk, carrier portals, and ShippyPro, piece together a tracking status, and write a reply from scratch. Each ticket takes 5β10 minutes of handling time. For delays or exceptions, the same ticket resurfaces over multiple days.
ShippyPro's Tracking Solver addresses this with a native Zendesk integration that closes the loop automatically β without agents leaving their helpdesk.
When a WISMO ticket arrives in Zendesk, Tracking Solver:
The AI agent analyses the ticket content and identifies it as a tracking-related inquiry. For tickets outside its scope, it generates an escalation note rather than a reply draft.
Tracking Solver connects to ShippyPro's carrier integrations and fetches the current shipment status in real time β no manual lookup across carrier portals required.
A carrier-accurate, plain-language reply is generated in under 30 seconds β in the language of the incoming ticket. The agent never leaves Zendesk.
The agent reviews the draft, makes any adjustments, and sends. The full loop β from ticket arrival to reply β takes seconds rather than minutes.
The ROI on Tracking Solver compounds the savings from proactive notifications. Notifications prevent most tickets. Tracking Solver dramatically reduces the cost of the tickets that still come through.
| Metric | Without Tracking Solver | With Tracking Solver |
|---|---|---|
| Handling time per WISMO ticket | 5β10 minutes | Under 1 minute (review + send) |
| Agent context-switching | Zendesk β carrier portal β ShippyPro β Zendesk | Stays in Zendesk throughout |
| First-response time | Minutes to hours (queue-dependent) | Draft ready in under 30 seconds |
| Multi-language support | Requires bilingual agents or translation step | Draft generated in the ticket's language |
| Peak season capacity | Linear: more tickets = more agents | Scales without headcount increase |
For a merchant with 300 tracking tickets per week, an estimated 30% automated resolution rate (based on pilot data from ShippyPro's early adopter cohort) and 50% draft acceleration on the remaining tickets translates to roughly 12.5 agent-hours recovered per week.
Tracking Solver's 30-day free trial starts with no credit card required, and the concierge onboarding (which includes Zendesk integration setup and quality verification) is handled by ShippyPro's product team. Starting the trial before your peak season means the system is calibrated and running before your ticket volumes spike.
Book a demo and we'll walk you through the Zendesk integration, show you a live draft from a real ticket, and answer your questions about onboarding.
Automated Email, SMS, and WhatsApp notifications triggered by real carrier events across 190+ carriers.
Explore Notifications βBranded tracking pages that keep customers in your ecosystem and surface post-purchase revenue opportunities.
Explore Track & Trace βTrigger-based workflow automation for carrier selection, label generation, and operational rules β without manual intervention.
Explore Automation βConnect 80+ sales channels and 190+ carriers in one place β Shopify, WooCommerce, Magento, marketplaces, and more.
Browse Integrations βSelf-service returns management for orders originally shipped via ShippyPro β reduce return-related tickets alongside WISMO.
Explore Easy Return βGuides, case studies, and operational playbooks for ecommerce shipping β all in one place.
Visit Resources βWISMO stands for "Where Is My Order?" β the most common customer service question in ecommerce. It refers to any inquiry where customers ask about order status, tracking, or estimated delivery. WISMO typically accounts for 40β60% of all ecommerce support volume.
The primary strategy is proactive shipping notifications β telling customers about order status before they ask. The four highest-impact notification types are: Shipped (Email), Out for Delivery (SMS/WhatsApp), Delivered (Email), and Exception alerts. For tickets that still come through despite notifications, tools like ShippyPro's Tracking Solver can draft carrier-accurate replies inside Zendesk in under 30 seconds.
The "Out for Delivery" notification has the highest single impact because it answers the most pressing question β "When will my order arrive?" β at exactly the moment customers start wondering. Sending it via SMS or WhatsApp (rather than email) maximises the chance it's seen in time to prevent a ticket.
Tracking Solver is a native Zendesk integration that reads incoming WISMO support tickets, retrieves live tracking data from ShippyPro's carrier connections, and drafts a ready-to-send reply β all inside Zendesk, without the agent needing to switch tabs or look up the shipment manually. Drafts are generated in under 30 seconds and in the language of the incoming ticket. It operates on a per-billable-ticket metered model (from β¬0.49 per draft) with a 30-day free trial.
Use both strategically: Email for milestone notifications (Shipped, Delivered) that customers want to reference. SMS or WhatsApp for time-sensitive alerts (Out for Delivery, Exceptions) that require immediate attention. SMS has a 98%+ open rate versus 20β40% for email, making it significantly more effective for urgent communications.
Each WISMO ticket costs 3β5 minutes of agent time. Industry benchmark data puts the all-in cost at approximately β¬4 per tracking ticket at enterprise scale, when accounting for agent wages, tooling overhead, and escalation handling. A merchant handling 300 tracking tickets per week faces roughly β¬57,600 per year in WISMO-related support costs.
Yes. ShippyPro normalises tracking data from 190+ carriers into consistent notification workflows, enabling uniform customer communication regardless of which carrier handles each shipment. This is particularly important for European merchants using a mix of national postal services, regional specialists, and international carriers.
WISMO is informational β customers asking about status that already exists in your system. Delivery issues are real problems: lost packages, damage, incorrect addresses, customs holds. WISMO is preventable through proactive communication; delivery issues require investigation and action. Most merchants conflate the two, but the distinction matters because each calls for a different response strategy.
Most merchants see meaningful WISMO reduction within 1β2 weeks of implementing proactive notifications. The full impact becomes clear over 30β60 days as notification habits establish and customers learn to expect updates. Tracking Solver's impact on the tickets that do come through is immediate from day one of the trial.
Yes. Tracking Solver generates reply drafts in the language of the incoming ticket, which is particularly useful for European merchants managing cross-border shipments and multilingual support queues from a single Zendesk instance.
ShippyPro automates proactive shipping notifications across 190+ carriers, gives customers a self-service branded tracking page, and β for teams using Zendesk β drafts carrier-accurate replies to the tickets that still come through. Try it free for 14 days.