Skip to main content
RoutMe

Playbook

How to reduce WISMO tickets

By the RoutMe team. Last updated .

WISMO, short for "where is my order", is the support question shoppers ask after buying and before delivery. To reduce WISMO tickets, tell customers proactively when status changes, make tracking easy to find, and let a read-only assistant answer status questions from live order data, passing exceptions to a person.

Why WISMO is so common

Shoppers ask because they lack information, not because they want to talk. Confirmation emails get buried, tracking links are hard to find, and carriers update on their own schedule. Each ask costs a person a minute to open the order system, find the status and paste it back. The answer already exists, which is why this job automates well.

The four levers

1. Tell them before they ask

Send updates when status changes: order confirmed, shipped with tracking, out for delivery, delivered. On WhatsApp these are utility templates, and templates are the way to reach customers outside the 24-hour customer service window. Meta's pricing documentation explains that free-form messages can only be sent inside an open window, and that templates can be delivered at any time. Template categories are billed differently, so check the pricing page and the template guidance before building a notification flow.

2. Make tracking self-serve

Put the tracking link in the confirmation message, in the account page and in the footer help. Wherever the customer is, one tap should reach the carrier page.

3. Answer the question instantly

A read-only assistant on your website chat and WhatsApp can handle "where is my order" at any hour. It asks for the order number and a second detail, calls a lookup tool, and replies with status, carrier and tracking. The safe design is described in how an AI agent looks up order status safely.

4. Handle exceptions with people

A parcel stuck for days, a wrong address, a carrier scan that says delivered when it was not: these need judgment and sometimes money. Route them to your team with the conversation and order attached.

What to expect from each lever

LeverEffortReducesLimits
Proactive updatesMediumTickets from silenceDepends on carrier data quality
Self-serve trackingLowTickets from hunting for linksCustomers still need to read
AI assistant lookupsMediumTickets that remain after the first twoNeeds verification and a tool
Human exceptionsOngoingEscalated riskNeeds staffing

None of these has a guaranteed percentage. Measure the share of your tickets tagged as status questions before you start, then again a few weeks after each change.

Set up the assistant on a store

  1. Add the chat widget to the storefront. For Shopify, follow the setup guide.
  2. Expose a read-only order tool through MCP, using your platform's API credentials.
  3. Add the shipping policy as a knowledge source so questions about timelines are quoted from your words.
  4. Define the handoff rule: for example, no tracking movement after a set number of days.
  5. Test with real order numbers, wrong emails and vague wording.

The where-is-my-order solution page lists the steps and the flow templates include an order status flow.

Common mistakes

  • Estimating a date the carrier never gave. Say what the record says.
  • Skipping verification. An order number alone is not proof.
  • No handoff. A customer with a lost parcel needs a person quickly.
  • Over-notifying. Too many messages creates its own tickets, and on WhatsApp opt-out must be honored.

A rollout order that works

Start with the cheapest change and move on only when it is stable. First put the tracking link in the confirmation and shipping messages and tag your tickets so you have a baseline. Second, add the website widget with a knowledge source holding your shipping policy, so questions about timelines are answered immediately without any order data. Third, connect the read-only order tool and enable verification. Fourth, add proactive status templates on WhatsApp for customers who opted in. Keep a short weekly review of conversations that were handed to people, because they show you exactly which carrier events or policy gaps still produce tickets.

Sources

Explore the product: RoutMe for Shopify, solutions and the documentation.

Frequently asked questions

Is WISMO only an ecommerce problem?

It shows up wherever customers wait for something: deliveries, repairs, applications. The pattern is the same.

Do I need WhatsApp?

No. A website widget works alone. WhatsApp helps when customers already message you there.

Should the assistant ever promise a delivery date?

Only repeat a date from your carrier or order system.

Put these ideas to work