Search for how much of retail support volume is WISMO and you will find the same range everywhere: 40 to 60% of all contacts. Sometimes 30 to 50%. Sometimes 70 to 80% at peak. It appears in vendor blogs, agency decks and conference slides, usually with no citation at all.

We went looking for the study behind it. There isn’t one. Every trail ends at an uncited blog post or a vendor’s self-attributed internal data with no methodology, no sample size and no published report. Shopify’s article on the subject gives no share figure. Gartner’s published customer service research covers self-service resolution rates and proactive outreach, not order-status contact share. One helpdesk vendor confirmed its cross-tenant data is contractually unpublishable.

This matters more than a pedantic point about citations. If you are building a business case for a returns portal, a tracking page or a deflection programme on a number nobody measured, the case rests on nothing, and the first person in the room who checks will say so.

What this post does instead

It gives you a method to measure your own WISMO share in about a week, a framework for deciding which of those contacts are removable, and an honest account of what deflection does and does not achieve. Your own number is both more accurate and more persuasive than a borrowed one.

How to measure your WISMO share in a week

You do not need a project. You need one disposition change and seven days of data.

1. Add four dispositions, not one. ‘Order status, pre-dispatch’, ‘order status, in transit’, ‘delivery exception’, and ‘delivery failed’. A single WISMO bucket tells you the total and nothing you can act on.
2. Run it for a full week, including a weekend. Order-status volume has a strong day-of-week shape tied to dispatch and delivery schedules.
3. Count contacts, not customers, and count every channel. Email, chat, social and phone have very different order-status shares. A voice-only measurement will understate it substantially.
4. Divide by orders dispatched in the same window, not by total contacts. Order-status contacts per hundred dispatches is a stable, comparable operating metric. Share of total contacts moves whenever anything else in the queue moves.

That last point is the one worth keeping. ‘WISMO is 45% of our queue’ tells you nothing about whether it improved, because the denominator moves. ‘We take 6.2 order-status contacts per hundred dispatches, down from 9.1’ is a number you can manage and defend.

The five things that actually generate order-status contacts

Once the four dispositions are running, the cause usually becomes obvious. In most retail operations it is one or two of these, not all five.

Remove WISMO contacts before you deflect them

Deflection moves a contact from an agent to a self-service channel. Removal means the customer never needed to ask. Removal is cheaper, better for the customer, and permanent. Deflection is what you do with what is left.

The clearest illustration of removal beating deflection is what happens when you do neither. Fulfilment delays at The Pampered Chef drove wait times past eight hours, and the wait then produced its own contacts, customers asking again about orders nobody had been able to answer for the first time. That case study is worth reading alongside this one, because the volume was not created by a shortage of self-service.

Removal, in rough order of impact

• Fix the delivery promise. An accurate date that is two days later generates far fewer contacts than an optimistic one that slips.
• Notify proactively at the moments customers ask. Dispatch, out for delivery, delivered, and any exception. Exception notifications are the highest-value and the most often missing.
• Explain silence. A tracking page that says ‘in transit, next scan expected within 48 hours’ removes contacts that a blank page creates.
• Announce split shipments at dispatch, not when the customer notices.
• Put order status in the order confirmation email as a link, not only in an account area that requires a login the customer does not have.

Then deflect what remains

Self-service order lookup, an order-status intent in your chat layer, and a tracking page that answers the follow-up question rather than restating the carrier feed. All three work well for the pre-dispatch and in-transit dispositions.

The order-status contacts you should never automate

• Delivery failure with a deadline attached. A birthday, a wedding, a flight. The customer is not asking where the parcel is. They are asking what you are going to do about it.
• Any second contact on the same order. The first attempt failed. Sending them back through the same self-service flow is how a minor problem becomes a public one.
• High-value orders. Set a threshold and route above it to an agent regardless of the question.
• Anything where the tracking data contradicts the customer. ‘Delivered’ when the customer says it was not is a judgement call, and automation handles it badly every time.

Zendesk’s 2026 retail research found 85% of retail leaders say customers will drop brands that miss first contact resolution, and 83% agree that resolution is the new currency. Both figures argue for the same thing: deflect the simple volume hard, and put the exceptions in front of someone who can actually fix them.

What a realistic programme achieves

Be sceptical of any published reduction percentage, including a vendor’s. The honest answer is that it depends almost entirely on which of the five causes you have, and a business with a delivery estimate problem will see a very different result from one with a tracking integration problem.

What is reliable is the sequence. Measure with four dispositions. Identify the dominant cause. Fix the cause. Deflect the residual. Route the exceptions to tenured agents. Re-measure against contacts per hundred dispatches, and you will have your own number, which is the only one you can defend in a budget meeting anyway.

WISMO in short

The industry statistic everyone quotes about order-status volume does not exist. Measure your own in a week with four dispositions and a per-hundred-dispatches denominator. Most of that volume is created upstream by delivery promises, tracking gaps and split shipments rather than by a shortage of self-service. Fix those first, deflect what is left, and keep delivery failures and repeat contacts in front of a person.

Sources

• Zendesk, CX Trends 2026, Retail. 85% first contact resolution figure and 83% resolution figure. https://cxtrends.zendesk.com/reports/retail/
• Descartes Systems Group, Annual Ecommerce Study, 8,000+ consumers across 10 European and North American countries. Delivery problem incidence. https://www.descartes.com/resources/news/descartes-annual-ecommerce-study-shows-younger-consumers-driving-online-buying
• Gartner, survey on self-service issue resolution, August 2024. Checked and found not to cover order-status contact share. https://www.gartner.com/en/newsroom/press-releases/2024-08-19-gartner-survey-finds-only-14-percent-of-customer-service-issues-are-fully-resolved-in-self-service
• Shopify, WISMO article. Checked and found to contain no contact-share figure. https://www.shopify.com/blog/wismo-ecommerce