A large share of the questions reaching an online store’s support team start the same way: “Where is my order?” The industry calls them WISMO calls. They are repetitive, they peak exactly when your team is busiest, and each one takes an agent away from problems that genuinely need a person.

The good news: most of these questions can be prevented, and most of the rest can be answered without a person. Below are six ways to reduce order status calls, ordered from cheapest to most comprehensive.

First, measure the problem

Before reducing anything, know where you stand. For one month, answer these questions:

  • How many contacts arrive across phone, email and chat in total?
  • How many of them are about order status or tracking?
  • How many come from a real problem with the order (delay, damage, wrong address), and how many from missing information?
  • How many times does the same customer contact you about the same order?

The last two questions matter most. Contacts caused by missing information are solved with communication; contacts caused by real problems are solved with operations. Mix them up and you’ll try to fix a warehouse delay with a notification text.

1. Set the right expectation at checkout

Many “where is my order?” questions are really “why hasn’t it arrived yet?”, and the cause is often an expectation that was set wrong.

  • State delivery times in business days, clearly. Not “fast shipping” but “ships within 1–3 business days”. Say whether weekends and public holidays count.
  • Repeat it on the confirmation page and email. Customers don’t remember the product page; they remember the date in the confirmation email.
  • Separate pre-orders and backordered items. If an item ships later, show that in the cart and in the confirmation.

2. Tell customers when things change

The most effective measure is telling customers before they ask. Send a short update at the key moments in an order’s life:

  1. Order received (with an estimated dispatch date).
  2. Dispatched (with carrier and tracking number).
  3. Out for delivery.
  4. Delivered.
  5. Delayed (the most important one; more below).

Keep these messages about the order. Adding promotions to transactional updates can change how they are treated under marketing consent rules in many countries, and it erodes the trust that makes customers read them.

Plenty of stores send a tracking number, only for the customer to get “no record found” on the carrier’s site. That guarantees the next call.

  • Attach the tracking number to the order at dispatch. Numbers entered by hand or uploaded in an end-of-day batch arrive late.
  • Link straight to the tracking page. Don’t expect customers to copy a number and paste it elsewhere.
  • Explain the lag. If tracking appears on the carrier’s system a few hours after handover, say so in the message.
  • List every parcel. Sending one tracking number and forgetting the second parcel creates a “half my order is missing” call.

4. Make self-service order lookup easy

If checking an order means logging in, remembering a password and hunting through menus, customers will call instead. Check that:

  • Order status can be looked up without an account, with an order number plus phone or email.
  • The page works well on mobile.
  • Statuses are written in customer language: “Being prepared”, “Dispatched”, “Out for delivery”. Don’t expose internal status codes.
  • The page states the next step. “Estimated dispatch: 14 October” prevents far more questions than “Processing”.

5. Announce delays before customers notice

The most expensive WISMO call is the one where the customer discovered the delay before you told them. These calls start frustrated and run long. Tell them first and the same conversation is short and calm.

To do that:

  • Run a simple daily rule that lists orders that have passed, or are about to pass, the promised time.
  • Tell those customers why and give a new estimate; offer options if you can (wait, alternative item, cancel).
  • For high-value or sensitive orders, consider a short service call instead of a message. Keep it about the order, with no promotion.

Consumer rules in many markets also set deadlines for delivery and for telling customers when an order can’t be fulfilled. Check what applies in your markets.

6. Answer the remaining calls with a voice agent

After the first five steps, call volume drops but doesn’t reach zero. Some customers will always prefer the phone: older customers, people unsure about online tools, or those who simply want to hear a voice. Most of these calls still come down to the same few questions: what’s the status, which carrier, what’s the tracking number, when will it arrive?

Handing these repetitive calls to a voice agent frees your team for real problems such as damage, loss and wrong items. What to expect from a good agent:

  • It recognises the caller by phone number and asks for the order number when there’s no match.
  • It clarifies which order the caller means when there are several.
  • It reads tracking numbers clearly, in groups.
  • It doesn’t invent answers when something is really wrong; it opens a request or transfers to the right person.
  • It answers outside working hours too, and books a callback for the next day when needed.

Remember: the agent reads whatever the order record says. The tracking discipline from step 3 matters here as well.

When the carrier has a bad week

Sometimes the problem isn’t yours but the carrier’s: peak season, weather, a delayed hub. WISMO calls can multiply overnight. To be ready:

  • Agree one status message. The team, the site and notifications should all say the same honest thing, such as “Deliveries may be one or two days late due to high volume at the carrier.”
  • List the affected orders. If you know which regions or dispatch days are affected, tell those customers before they ask.
  • Add a short banner to your site. Customers check the site before calling.
  • Know your escalation path with the carrier. For lost or damaged parcels, be clear on who responds, through which channel and how fast.

Measure again

After making changes, repeat the measurement:

  • Has the share of order status contacts dropped?
  • Are fewer customers contacting you repeatedly about the same order?
  • Do customers who got a delay notice contact you less?
  • How many voice-agent shipping calls were resolved without a transfer?

Tracking these month by month shows which step made the difference.

How Zitena handles it

Zitena’s order status calls match the caller by phone number and ask for the order number when there’s no match. If a number has several orders, the agent confirms which one, then reads the status, carrier and tracking number in groups. When the agent can’t resolve something, a request lands in your team’s inbox or the call is transferred by topic and working hours; if nobody answers, a callback is booked.

On WooCommerce, order status is read directly from your store; on other platforms, orders are sent through the Data API with status, carrier, tracking number and customer phone. For a delayed order you can call before the customer does, with a service call in which sales tools are disabled in code. SMS tracking links are optional and off by default. Every call is tagged by topic, so you can follow the share of shipping questions and how many the agent resolved in the console. Curious what happens behind the scenes on such a call? Read how an AI voice agent works.

The agent is live in Turkish today; other languages are adapted on request. To hear a shipping call with your own orders, book a demo.