How to reduce WISMO tickets with clearer order tracking and AI support
Reduce repeat delivery questions with a practical WISMO workflow: clear tracking, verified order answers, exception handoffs and a measurement plan.
A customer asks where their order is. Your team copies a tracking link. The customer opens it, sees that a label was created two days ago, and asks again. The first reply was fast, but the uncertainty survived. WISMO means 'where is my order'. Reducing these tickets starts with explaining what is known, what is still missing and what happens next.
Find the uncertainty behind the ticket
Review a sample of recent delivery conversations and record the reason behind each one. Was the tracking email missing? Was the parcel still awaiting a carrier scan? Did a customer mistake a dispatch estimate for an arrival promise? Count conversations about the same order together when checking repeat contacts. This gives you a manageable list of fixes rather than a single 'shipping' category.
Some of those fixes belong outside chat. Put the tracking route in the order confirmation, make the order-status page easy to find, and explain dispatch times before checkout. If an order is waiting on stock, a confident chatbot cannot make it move faster. Give the team a route for finding the actual cause and telling the customer what to expect.
Fix the tracking path before adding automation
Shopify's order-tracking documentation explains how tracking added to a fulfilled order reaches the order-status page, shipping notifications and Shop. Check that your fulfillment process supplies the tracking information these surfaces need. AI support complements that existing route when a shopper needs an explanation; it does not replace missing fulfillment data.
On either Shopify or WooCommerce, test the journey from the customer's side. Open the confirmation on a phone, follow the tracking link, and check a split shipment and an order that has not shipped yet. A useful status message separates the order's processing state from the carrier's delivery state. 'Your label is ready' and 'your parcel is on its way' describe different events.
Choose what AI can answer and what needs an owner
| Situation | Useful AI response | Human next step |
|---|---|---|
| Tracking available and progressing | Explain the latest available status and link to tracking | Review only if the customer raises a separate concern |
| Label created but no carrier scan | Explain the visible state without claiming dispatch | Investigate after your documented waiting threshold |
| Delivered but customer cannot find parcel | Acknowledge the discrepancy and collect the issue | Investigate with the warehouse or carrier |
| Address change or refund requested | Explain the process and preserve the request | Authorize any supported change through the approval workflow |
Suggested operating rules. Waiting thresholds and available actions depend on your store, carrier and configured integration.
Keep identity verification ahead of private order details. A public shipping-policy answer needs no order access. An answer about a particular purchase does. Use the verification flow supported by your integration, reveal only the entitled customer's information, and hand off if verification fails. An order number alone should not become a shortcut around that boundary.
Also define a handoff owner. If a customer reports a lost parcel, give the next agent the question, available order context and what the assistant already said. Avoid making the customer explain the discrepancy again. Outside office hours, state the expected follow-up process instead of promising an immediate investigation.
Measure fewer problems rather than fewer messages
- Delivery contact rate: delivery-related conversations divided by orders in a consistently defined cohort.
- Repeat contact rate: orders with another delivery contact within your chosen window, divided by orders with an initial delivery contact.
- Completed AI resolutions: conversations solved without a human reply, reviewed after the settling window.
- Exception response time: how long the customer waits once a delivery issue needs a person.
Compare equivalent periods and check carrier incidents, promotion traffic and delivery regions. For example, 120 delivery conversations across 2,000 orders is six conversations per 100 orders; 90 across 2,000 is 4.5. That illustrative change deserves investigation, but it does not prove AI caused the reduction. Tracking emails or faster fulfillment may have contributed. Keep those changes in the report.
Start with one store and one delivery workflow
CustomerEagle's Shopify support setup and WooCommerce support setup separate the storefront widget from connected store data. Store-data access requires Standard or higher and the relevant authorization. Shopify return preparation and WooCommerce approval workflows have different action boundaries; check the applicable setup before promising changes. Refunds are not something the assistant should execute on its own.
Bring a normal delivery question, a missing-scan question and a delivered-but-missing question to a product demo. Check the source, verification and handoff for each. Then use our resolution measurement guide and the AI-to-human handoff playbook to define a small pilot your team can review.
What is a WISMO ticket?
A WISMO ticket is a customer conversation asking where an order is or when it will arrive. It can reflect missing tracking, unclear delivery information or a genuine fulfillment problem, so the right response depends on the cause.
Can AI answer order-tracking questions?
AI can explain order information when a supported store connection supplies it and the customer passes the required verification. When data is missing or contradictory, the useful response is a clear handoff rather than an invented delivery promise.
Will a tracking page remove all delivery questions?
A tracking page gives customers a route to available shipment information, but exceptions still need explanation and ownership. Split shipments, absent carrier scans and delivered-but-missing parcels are examples that can still require support.
How should we measure WISMO reduction?
Track delivery contacts relative to order volume, repeat contacts for the same order and the time to handle exceptions. Compare consistent cohorts and record other changes, such as a new carrier or notification flow, before attributing the result to AI.
Resolve more tickets automatically.
Connect your help centre, test answers on your own questions, and review handoffs before rolling it out.