AI Business

Where Is My Order? How AI Agents Handle WISMO Calls and Tickets

Written by
Dr. Anushtha Singh
Created On
November 5, 2026

Table of Contents

Don’t miss what’s next in AI.

Subscribe for product updates, experiments, & success stories from the NuPlay team.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

TL;DR

WISMO ("Where is my order?") is one of the largest categories of retail customer contacts, and it arrives everywhere: chat, email, the contact-center line, the store phone and the store counter. Most of it is a customer filling a silence the retailer could have filled first. AI agents reduce WISMO in three ways: they answer order-status questions from live order data in any channel, they send updates before customers ask, and they hand real problems to a person with the case already worked. The part most retailers miss is the store, because calls to stores create no ticket. Start with the highest-volume status questions, tell customers about delays first, and track repeat contacts per order.

Why do customers still ask "Where is my order?"

Every retailer already sends confirmation emails, links to a tracking page and runs a chat widget. Customers still ask. Industry estimates put WISMO at 10% to 25% of service contacts in a normal month, rising sharply at peak. Even that range, as one tracking provider points out, has no primary study behind it, so treat it as a direction, not a benchmark.

The reason self-service hasn't ended WISMO is simple. A tracking page answers "Where is the parcel?" It doesn't answer "What does this status mean for me?" A scan that hasn't moved in three days, a parcel marked delivered that isn't on the doorstep, or a pickup order marked ready that isn't bagged yet all send the customer to a person.

The cost goes beyond handling time. 43% of consumers say a poor customer experience deters them from shopping with a brand again, according to Salesforce's State of Service research. A WISMO contact is often the moment that experience is decided.

Where does WISMO show up?

WISMO isn't one queue. The same question arrives in five places, and each one reaches a person for a different reason.

Where it happens What the customer asks Why it reaches a person today What the agent does
Chat and email"My tracking hasn't updated since Monday."The tracking page shows a status, not an explanationReads carrier and order data, explains the status and gives a realistic date
Contact-center phone"It says delivered, but it isn't here."Callers who skipped self-service, or for whom it failedAnswers by voice from live data; opens a claim when the parcel is missing
Store phone"Is my pickup order ready?"No one routes these calls; an associate picks upAnswers the store line with pickup status, around the clock
Store counter"My online order is delayed. What's going on?"The associate has to check a separate systemGives the associate the status and next step in seconds
Every channel, againSame question by chat, then phone, then in personNo shared record of earlier contactsKeeps one record of the order and every contact about it

The same triggers drive all five: delayed or stalled scans, carrier exceptions, split shipments, vague delivery promises at checkout, and pickup orders that aren't ready when the status says they are. After delivery, the question changes to "Where is my refund?" (WISMR), and the cycle repeats.

Why is WISMO in stores the part most retailers miss?

Every WISMO figure counts tickets, and the store phone creates none. When a customer calls to ask if a pickup order is ready, an associate stops helping a shopper, checks the order and comes back. Three things make this version harder to fix.

The interruption costs a sale, not just a minute. A contact-center agent who takes a WISMO call was going to take some call. An associate who takes one walks away from a shopper who was ready to buy.

The answer depends on what's physically in the store. "Ready for pickup" in the system and "bagged and on the pickup shelf" are not always the same moment. An answer from the order record alone can be confidently wrong.

Nobody owns it. The contact center owns WISMO targets. Store teams own sales and tasks. Calls about online orders fall between the two, so they are rarely counted.

For what happens when the pickup order itself can't be filled, see our BOPIS guide.

How do AI agents reduce WISMO?

The agent has three jobs: answer the question, make the question unnecessary, and hand over the cases it shouldn't answer.

1. Answer order-status questions from live data, in every channel

The agent reads the order management system (OMS) and carrier feeds directly, not a cached tracking page. It answers in chat, email and by voice on the contact-center line or the store phone, after confirming the customer against the order. For pickup orders it also checks store-side status: picked, staged, or still waiting on an item.

The same agent works for associates. At the counter, the associate asks "Where's order 4471?" and gets the status and next step without opening a second system.

2. Tell the customer before they ask

Most WISMO contacts are a customer filling a silence. The agent closes it with messages tied to real order events:

  • Delay or exception alerts, sent as soon as the scan stalls or the carrier flags a problem, with a new date
  • Ready for pickup, sent only when the order is confirmed staged, not when it is first marked picked
  • Partial fill or substitution, sent before the customer travels, with options attached
  • Ship-to-store arrival, when the store receives the item, not when the carrier marks it delivered
  • Refund issued, so a return doesn't turn into a "Where is my refund?" contact

3. Escalate real problems with the case already worked

Some questions aren't status checks. The parcel is lost, the order is wrong, or the customer is on their third contact. The agent hands these to a person with the order history, every prior contact, and what the customer wants already attached. The person starts from the answer, not from "Can I get your order number?"

What should the agent do when the answer isn't clean?

Order status is easy when every system agrees. The test of a WISMO agent is the cases where they don't.

Hard case The wrong answer What the agent should do
Tracking says "delivered," but the customer doesn't have it"It shows as delivered"Check the delivery record and photo if available, apply the missing-parcel policy, and open a claim or escalate
The scan hasn't moved in days"It's in transit"Say the scan has stalled, give the carrier's typical recovery time, and alert the customer again if it doesn't move
The order shipped in two parcels and only one arrived"Your order was delivered"Explain the split shipment and give the second parcel's status
The OMS says "ready," but the order isn't on the pickup shelf"Yes, come in now"Trust the store-side scan over the order flag; tell the customer it's being prepared and alert an associate
The caller isn't the person on the orderReading out order detailsVerify against the order first; apply the alternate-collector policy for pickups
The customer has contacted twice alreadyStarting from scratchRecognize the repeat contact and route it to a person, with both prior conversations attached

The pattern: the agent states what it knows, says what it doesn't, and never promises a delivery or pickup the business can't keep. One wrong "it's on its way" undoes ten right ones.

Where should retailers start, and what should they measure?

Start with the status questions where the answer already sits in your OMS or carrier data: "Where is it?" and "When will it arrive?" in chat and on the contact-center line. Add proactive delay alerts next, because they remove contacts rather than answer them. Then bring in the store phone and pickup questions. Lost parcels and wrong orders stay with people from day one.

Measure WISMO per order, not just as a share of contacts. WISMO contacts per 100 orders adjusts for order volume. Track the rate alongside total WISMO contacts and orders to interpret changes correctly. And because calls to stores are rarely logged, tag a week of store calls by reason before the agent goes live.

Metric What it tells you
WISMO contacts per 100 orders, by channelThe true size of the problem, including the store
Share of WISMO contacts resolved without a personWhether the agent is taking work off your teams
Repeat contacts per orderWhether answers and proactive messages actually settle the question
Contacts that follow a proactive messageWhether your messages explain enough
Status messages that turned out wrong ("ready" but not staged, "delivered" but missing)Whether customers can trust what the agent says
First-contact resolution on escalated casesWhether handovers arrive with enough context
CSAT on WISMO contactsWhether the experience improved, not just the cost

Watch wrong status messages most closely. They are what decides whether customers, and associates, keep trusting the agent.

How do NuPlay agents handle WISMO?

NuPlay's retail agents handle where's-my-order end to end, across voice, chat, email, SMS and messaging, and cite the policy clause behind each decision. For WISMO, that means:

  • Order resolution: delivery status, pickup status, exchanges, refunds and loyalty points answered from live order data, with the policy applied stated in each answer
  • Proactive outreach: delay alerts, delivery updates and follow-ups sent before the customer asks
  • Intelligent escalation: cases that need a person arrive with history, intent and the customer's full picture in one handover

The agents connect to the systems that hold the answer: commerce platforms such as Shopify, Salesforce Commerce Cloud and Magento, and enterprise systems such as SAP, Oracle and ServiceNow. NuLoop, the platform's self-improvement layer, learns from every run, so the agent gets better at the questions your customers actually ask.

‍

Conversational AI for Sales and Support teams

Talk to our team to see how to see how Nuplay AI powers smarter engagement.

Let’s Talk

Ready to see what agentic AI can do for your business?

Book a quick demo with our team to explore how NuPlay AI can automate and scale your workflows

Let’s Talk
What does WISMO stand for?

WISMO stands for "Where is my order?" It covers any customer question about the status of an order they have already placed, by phone, chat, email or in person.

‍

What causes most WISMO contacts?

Most come from gaps in communication rather than failed deliveries: stalled tracking scans, carrier exceptions nobody explained, split shipments, vague delivery dates at checkout, and pickup orders that aren't ready when the status says they are.

‍

What share of customer contacts is WISMO?

Industry estimates put it at 10% to 25% of service contacts in a normal month, rising at peak. These figures lack a primary study and none count calls to stores, so measure your own baseline as contacts per 100 orders.

What is the difference between WISMO and WISMR?

WISMO is about outbound orders. WISMR ("Where is my refund?") is the same question after a return. Both are reduced the same way: answer from live data and send updates at each milestone.

‍

What is in-store WISMO?

In-store WISMO is order-status questions that reach a physical store instead of the contact center, such as calls asking if a pickup order is ready or counter questions about delayed online orders

Can an AI agent answer order-status calls?

Yes. A voice agent can answer the contact-center line or the store phone, verify the caller against the order, read live status from the OMS, and transfer to a person when the question goes beyond order status.

‍

What happens when the agent can't resolve the question?

It escalates to a person with the order history, prior contacts and the customer's request attached, so nobody starts over.

How can I reduce WISMO with AI agents?

Checklist: reducing WISMO with AI agents

  • Baseline WISMO as contacts per 100 orders, by channel, including a week of tagged store calls
  • Connect the agent to the OMS, carrier feeds and store-side pickup status, not just the tracking page
  • Send delay and exception alerts as soon as a scan stalls, with a new date
  • Fire "ready for pickup" only when the order is staged, and "delivered" for ship-to-store only when the store has the item
  • Define caller verification and the alternate-collector policy before the agent answers any phone line
  • Route missing parcels, wrong orders and repeat contacts to a person, with the full case attached
  • Track wrong status messages and repeat contacts per order from week one
  • Start with chat and contact-center status questions; add the store phone once accuracy holds

For pickup orders that can't be filled as placed, see our BOPIS guide.

‍

Related

Related Blogs

Explore All
<---NEW-FAQ--->