WISMO Tickets Eating 40% of Your Support Queue? Here's How to Automate Them on Shopify

"Where is my order?" It is the single most common customer support question in e-commerce, and it is also the most automatable. WISMO tickets follow a nearly identical pattern every time: customer asks, agent looks up tracking, agent pastes the status into a reply. That repetitive loop consumes a disproportionate share of your support team's time, and every minute spent on it is a minute not spent on work that requires actual human judgment.

This guide covers exactly how to automate WISMO tickets from start to finish, including the workflow logic, carrier integrations, edge case handling, and guardrails that make it safe to let AI resolve these at scale.

What Percentage of Support Tickets Are WISMO?

WISMO tickets account for 30-40% of all customer support volume in e-commerce, making them the single largest ticket category for most Shopify stores. During peak shipping periods like holiday season or major sales events, WISMO volume can spike to 50% or more of total inbound inquiries.

That percentage is staggering when you consider its implications. If your store handles 2,000 tickets per month, between 600 and 800 of those are customers asking about their order status. At a cost of $8-$15 per human-handled ticket, you are spending $4,800 to $12,000 per month on what is essentially a data lookup task.

The irony is that WISMO tickets are almost never complex. The customer wants to know where their package is. The answer lives in your carrier's tracking system. The only thing standing between the question and the answer is the manual effort of looking it up, formatting a response, and sending it.

This is precisely why WISMO is the ideal starting point for AI automation. The workflow is structured, the data sources are well-defined, and the resolution rarely involves monetary decisions. Brands that automate WISMO first typically see their overall AI resolution rate jump to 40-50% immediately, with room to grow as they add more ticket types.

How Do You Automate Order Tracking Responses?

Automating order tracking responses requires connecting your AI support platform to your carrier data (via AfterShip, ShipStation, or direct API), building a classification layer that identifies WISMO intent, and configuring response templates that deliver tracking details in your brand voice. The full workflow executes in under 5 seconds.

Here is the step-by-step workflow that runs every time a customer sends a WISMO inquiry:

1. Customer sends a message via email, chat, or your contact form asking about their order status
2. AI classifies the intent as WISMO based on the message content, distinguishing it from related but different intents like CANCELLATION or RETURN
3. AI extracts the order identifier from the message, or matches the customer's email address to their most recent order in Shopify
4. AI queries the carrier via AfterShip or ShipStation to pull real-time tracking data, including current status, location, and estimated delivery date
5. AI evaluates the tracking status against a decision tree: Is the package in transit? Delivered? Stuck? Returned to sender? Lost?
6. AI generates a response in your brand voice that includes the specific tracking details, a tracking link, and the estimated delivery date
7. AI sends the response and marks the ticket as resolved

Each of these steps happens automatically, with no human involvement. The customer gets a personalized, accurate response within seconds of sending their inquiry, any time of day.

What Makes This Different from a Tracking Page

You might wonder why customers contact support at all when most stores have an order tracking page. The reality is that customers reach out for several reasons beyond simple tracking:

• They cannot find their order confirmation email
• The tracking page shows a status they do not understand ("in transit to next facility")
• The estimated delivery date has passed and they are concerned
• They ordered multiple items and only received a partial shipment
• The tracking shows "delivered" but they have not received the package

A simple tracking page cannot address these scenarios. An AI workflow can, because it interprets the tracking data in context and responds appropriately to each situation. "In transit to next facility" becomes "Your order is currently moving through the carrier's network in Dallas, TX and is expected to arrive by Friday, March 28th." That is the difference between self-service and actual resolution.

Setting Up the WISMO Workflow

The most effective WISMO automation is not a single rule. It is a branching workflow that handles the five distinct tracking states a package can be in.

State 1: Pre-Shipment

The order has been placed but not yet shipped. This happens when you have processing time before fulfillment, or when the warehouse has not yet created a shipping label.

AI response logic: Confirm the order details, explain that the order is being prepared for shipment, and provide the expected ship date based on your fulfillment SLA. If the customer placed the order within the last 24 hours, reassure them that processing is underway.

State 2: In Transit (On Schedule)

The package has been shipped and tracking shows normal movement toward the destination.

AI response logic: Provide the current tracking status, the carrier name, a clickable tracking link, and the estimated delivery date. Format this in your brand voice with the customer's name and order number. This is the most straightforward state and resolves instantly.

State 3: In Transit (Delayed)

The tracking shows the package is still moving, but the estimated delivery date has passed or the package has been at the same facility for an unusually long time.

AI response logic: Acknowledge the delay proactively. Provide the last known tracking update and location. Set a new estimated delivery window based on the carrier's updated data. If the delay exceeds your configured threshold (for example, 5 business days past the original estimate), offer the customer a choice: continue waiting or receive a replacement/refund.

This is where guardrails matter. Claro lets you configure monetary thresholds for each action. Replacements for orders under $50 can be auto-approved. Orders between $50 and $200 route to your Needs Review Queue where a human approves with one click. Orders above $200 are blocked from automatic action and assigned to an agent.

State 4: Delivered

Tracking shows the package has been delivered, but the customer is saying they have not received it.

AI response logic: Confirm the delivery details (date, time, location such as "front porch" or "mailroom"). Ask the customer to check with household members, building management, or neighbors. If the customer confirms they still cannot find the package after 24-48 hours, escalate to the lost package workflow.

This state requires careful handling because "delivered but not received" often involves porch theft, misdelivery, or driver error. The AI should gather information before offering a resolution, not immediately issue a refund.

State 5: Exception or Lost

Tracking shows an exception (returned to sender, customs hold, address issue) or has not updated in a period that exceeds the carrier's normal delivery window.

AI response logic: For exceptions with clear causes (wrong address, customs rejection), explain the situation and offer to reship to a corrected address. For packages with no updates beyond the expected window, classify as potentially lost and trigger the resolution workflow.

Claro's pre-built WISMO workflow template handles all five states out of the box, including carrier queries, threshold-based guardrails, and brand-voice responses. See the workflow builder →

Can AI Detect Lost Packages?

AI detects lost packages by monitoring the gap between a carrier's last tracking update and the expected delivery date, then cross-referencing carrier-specific transit time benchmarks. When a package has no movement for 7+ business days past the expected delivery window, the AI flags it as lost and initiates your configured resolution workflow.

Lost package detection is one of the highest-value capabilities in WISMO automation because it allows you to be proactive rather than reactive. Instead of waiting for a frustrated customer to contact you 10 days after their expected delivery date, the AI can identify potentially lost shipments and trigger outreach before the customer even reaches out.

Here is how the detection logic works:

1. AI monitors all open shipments with tracking numbers against their estimated delivery dates
2. When a delivery window passes without a "delivered" scan, the AI checks for recent tracking updates
3. If no updates exist within a carrier-specific threshold (typically 5-7 business days for domestic, 10-14 for international), the shipment is classified as potentially lost
4. AI initiates a carrier investigation if your integration supports it (filing a trace request with USPS, UPS, or FedEx)
5. Simultaneously, AI contacts the customer with a proactive message acknowledging the delay and offering options

The resolution options the AI offers depend on your configured guardrails:

• Under your auto-approval threshold: AI offers a full replacement or refund and executes immediately upon customer selection. The replacement order is created in Shopify, or the refund is processed through Stripe, without human involvement.
• Between your approval thresholds: AI presents the options to the customer, then routes the ticket to your Needs Review Queue with a summary, the customer's preference, and a one-click approval button for your team.
• Above your maximum threshold: AI acknowledges the situation, promises follow-up, and assigns the ticket to a human agent for manual resolution.

This tiered approach balances speed with safety. Low-value lost packages get resolved in minutes. High-value cases get human attention.

Carrier Integrations That Power WISMO Automation

The quality of your WISMO automation depends entirely on the quality of your carrier data. Without real-time, accurate tracking information, the AI cannot provide useful responses.

Two integrations handle the bulk of carrier connectivity for Shopify stores:

AfterShip aggregates tracking data from 1,200+ carriers worldwide into a single API. It normalizes tracking statuses across carriers (every carrier uses different terminology) into a standardized set of states. This normalization is what allows a single WISMO workflow to work regardless of whether you ship via USPS, UPS, FedEx, DHL, or a regional carrier.

ShipStation provides similar carrier connectivity with additional shipping management features. If you already use ShipStation for label generation and shipping rules, connecting it to your AI platform gives the AI access to both tracking data and shipment metadata like weight, dimensions, and shipping method.

Claro integrates with both AfterShip and ShipStation, along with 50+ other tools in the Shopify ecosystem. The integration pulls tracking data in real time, so the AI always responds with the latest status rather than cached information from hours ago.

Measuring WISMO Automation Performance

Once your WISMO workflow is live, track these metrics weekly:

AI Resolution Rate (WISMO-specific): What percentage of WISMO tickets does AI resolve without human involvement? Target: 85-95%. If you are below 80%, review the tickets that required human handoff. Common causes include customers providing no order information (fixable with better order lookup logic) or multi-order inquiries.

First Response Time: How quickly does a WISMO customer receive their tracking information? AI should respond in under 30 seconds. If you are seeing longer times, check your carrier API response latency.

Customer Satisfaction (WISMO-specific): Compare CSAT scores for AI-resolved WISMO tickets against human-resolved ones. In most cases, AI scores equal to or higher than human scores because customers value speed over personality for informational requests.

Escalation Rate: What percentage of WISMO tickets escalate from AI to human? Target: under 10%. High escalation rates indicate gaps in your workflow's edge case handling.

Cost per Resolution: Compare your WISMO cost per resolution before and after automation. The reduction should be 80-90% since WISMO tickets are the cheapest to automate.

Getting Started with WISMO Automation

If you have never automated a support workflow before, WISMO is the safest and highest-impact place to start. Here is the sequence:

1. Connect your carrier data. Integrate AfterShip or ShipStation with your AI platform so the system has real-time access to tracking information for every order.

2. Configure the WISMO workflow. Use a pre-built template if your platform provides one. Map each tracking state (pre-shipment, in transit, delayed, delivered, exception) to a response pattern and an action set.

3. Set your guardrails. Define monetary thresholds for automatic actions. Start conservative: auto-approve replacements and refunds only for orders under $30, require human approval for everything above that. You can raise the thresholds as confidence grows.

4. Run in shadow mode. Let the AI process WISMO tickets and generate responses for 5-7 days without actually sending them. Compare the AI's responses and decisions against what your human agents did. Look for accuracy, tone, and completeness.

5. Go live with monitoring. Activate the workflow and monitor closely for the first two weeks. Check your dashboard KPIs daily: resolution rate, response time, escalation rate, and customer satisfaction.

6. Iterate and expand. Once WISMO is running smoothly at 85%+ resolution rate, move on to your next highest-volume ticket type: returns and exchanges, cancellations, or refund status inquiries.

WISMO is 30-40% of your ticket volume, and it resolves at the highest AI accuracy rate of any ticket type. Automating it first gives you the biggest immediate impact with the lowest risk.

Every day you spend manually answering "where is my order?" is money spent on a data lookup that AI handles in seconds. Claro's pre-built WISMO workflow connects to AfterShip or ShipStation, covers all five tracking states, and responds in your brand voice with the exact tracking link and delivery estimate your customer needs. Shadow Mode lets you watch it handle your real WISMO tickets for a week before going live.

WISMO is the easiest win in support automation. Start resolving yours with Claro →

Once WISMO is running, expand to returns and refunds and the rest of your automatable ticket types.