The WISMO reduction SOP: cut your biggest support ticket category

Pull up your support tickets and sort by reason. One category dwarfs the rest: where is my order. WISMO is the single biggest source of support volume in DTC, running 30 to 50 percent of all tickets and climbing past half in peak season. Most brands respond by hiring more agents to answer them faster, which is like bailing a boat instead of plugging the hole.

Here's the reframe that changes everything: WISMO is not a support problem, it's a communication problem. The customer isn't writing in because the package is slow; they're writing because they're anxious and they don't know what's happening. Research puts roughly 73 percent of WISMO tickets in the preventable column, the ones a well-timed message would have answered before the customer ever felt the need to ask. Every WISMO ticket is, in effect, a notification you didn't send.

So you don't out-staff WISMO, you deflect it. This is the SOP we use with DTC brands to do that: set the delivery expectation before the customer wonders, send proactive updates at the moments that matter, give them a self-serve place to check, and reach out first when something goes wrong. Done well, it cuts WISMO by more than half and frees your team for the tickets that actually need a human.

Why WISMO needs an SOP

WISMO gets treated as a fact of life, the cost of selling physical products, so it's nobody's project. Agents answer the tickets one by one, the volume never drops, and the lever that would actually reduce it, proactive communication, sits unowned between marketing, ops, and support. An SOP names the deflection system and makes reducing WISMO a target instead of a chore.

It also turns WISMO from an anecdote into a number. Documented, you can measure the share of tickets that are WISMO, attack the biggest preventable causes, and watch the rate fall. Without that, we get a lot of where-is-my-order emails stays a vague complaint nobody is accountable for, forever.

Set the expectation before they wonder

The first WISMO ticket is born at checkout, when the customer guesses how long delivery will take and guesses wrong. You prevent it by setting a clear, honest expectation before they have to form their own:

• Show a concrete delivery estimate at checkout, not a vague ships-in-a-few-days. A date range the customer can plan around is the single best anti-WISMO move, because most early tickets are just impatience against an unstated timeline.
• Repeat the timeline in the order confirmation. The confirmation email is the most-opened message you send; put the expected delivery window in it, prominently.
• Be honest about the slow parts. If a product is made to order or ships from a 3PL with a cutoff, say so up front. An expectation you set and meet beats a fast promise you miss every time.

Most of the WISMO that hits on day two isn't about a real problem; it's the gap between what the customer assumed and what you never told them. Close that gap at checkout and a chunk of the volume never forms.

Proactive notifications: the biggest lever

Once the order ships, silence is what generates tickets. Proactive notifications fill the silence, and they're the highest-impact thing you can do: brands that notify customers at each stage cut WISMO by 40 to 50 percent within the first month, and more once the timing is tuned. Send an update at each milestone that matters:

• Order confirmed. The reassurance that the order went through.
• Shipped, with the tracking link. The moment the customer most wants to know it's moving.
• Out for delivery. The highest-anticipation moment; a heads-up here prevents the day-of where-is-it ticket.
• Delivered. Closes the loop, and doubles as a prompt for a review or a flag if it didn't actually arrive.

Use both email and SMS, because they do different jobs. Email carries the detail; SMS gets seen, with open rates around 98 percent against 20 to 40 percent for email. The milestones that carry urgency, shipped and out for delivery, are the ones worth an SMS. And a notification only deflects a ticket if it actually lands, so the same deliverability discipline that protects your marketing protects your shipping alerts.

The branded tracking page

Even with proactive notifications, customers want to check on their own, and where they check matters. The default carrier tracking page is generic, ad-cluttered, and off-brand, and it sends the customer away from you at the peak of their attention. A branded tracking page keeps them in your world and answers the question in one place:

• Show the current status and a concrete expected delivery date, not just cryptic carrier scan codes the customer can't parse.
• Put it on your domain, branded, so the most-visited page in the post-purchase window builds your brand instead of the carrier's.
• Use it to deflect and even sell: a clear status answers the WISMO question, and product recommendations on the page turn a support moment into a second purchase.

The tracking page is the self-serve half of deflection: the customer who still wants to look gets a clean answer without opening a ticket. Set it up deliberately, because a tracking page that just mirrors the carrier's confusing status does not actually deflect anything.

Reach out first when something goes wrong

Notifications and a tracking page handle the orders that go smoothly. WISMO spikes on the orders that don't, the delayed, stuck, or lost packages, and those are exactly where most brands go quiet and let the customer discover the problem themselves. Flip that. Reach out first:

• Watch for stalled tracking. If a package hasn't moved in a day and a half, that's a ticket forming. An automatic message that acknowledges the delay, gives the reason from the carrier, and sets a new expectation prevents most of those tickets before they're sent.
• Own the delay, don't hide it. A proactive heads-up that the order is running late, with the reason and a new date, turns a frustrated customer into a reassured one. Silence turns the same delay into an angry ticket and a lost repeat purchase.
• Offer something on the worst cases. For a real delay, a small credit or an expedited reship alongside the heads-up costs little and saves the relationship.

This is the counterintuitive core of WISMO reduction: the way to get fewer where-is-my-order tickets is to be the one who brings up where the order is. The brand that tells you about the problem first is the brand you don't write an angry email to.

Deflect the rest, resolve what's left

Expectations, notifications, tracking, and proactive delay comms prevent most WISMO. For the tickets that still come, the goal is to deflect the easy ones to self-serve and route the real ones to a person with context:

• Answer the top questions where customers look. A short FAQ or an order-status accordion covering when tracking updates, what a stuck status means, and what to do if it's late deflects a meaningful slice of first-time askers.
• Give whoever answers live order data. The agent or AI handling a WISMO ticket should see the order's real status without leaving the help desk, so the answer takes seconds, not a back-and-forth.
• Automate the actions the status implies. A WISMO ticket is often really an address change or a reship request in disguise; let the customer trigger those directly instead of opening a conversation.

The tickets that survive all of that are the genuine exceptions, the lost package, the delivery to the wrong house, and those deserve a real person. A good WISMO system shrinks the volume so far that your team can actually give those cases the attention they need.

Measure your WISMO rate

A WISMO system is only as good as the number it moves, so measure it. The metric is your WISMO rate: the share of support tickets that are where-is-my-order. Track it and you can manage it:

• Tag WISMO tickets so the rate is visible. A healthy DTC brand gets WISMO under 5 percent of tickets; the best, with proactive multi-channel comms, push it under 2 percent. If yours is 30 percent or more, the deflection above is your biggest single CX win.
• Watch it by stage and by carrier. A spike tied to one carrier or one product's ship times tells you exactly where the expectation or the notification is breaking.
• Track deflection, not just volume. If proactive notifications are working, WISMO should fall as orders rise; flat WISMO against growth means a notification or the tracking page has quietly broken.

Give the WISMO rate an owner, usually CX or ops, who reviews it monthly and owns driving it down. WISMO is unusual among support metrics in that it's mostly within your control, so a falling WISMO rate is a clean scorecard for whether the system is working.

Keep the SOP current

A WISMO system drifts because the things it depends on keep changing. You switch carriers and the tracking integration or the stalled-package trigger breaks. You launch a product with a longer lead time and the delivery estimate you promise at checkout is suddenly wrong. Peak season stretches every timeline past what your notifications assume. Each one quietly reopens the silence the SOP was closing.

Review the SOP quarterly, and immediately after any carrier change, a new product with different ship times, or heading into peak season. Watch the WISMO rate as your tripwire: a rise with no change in volume means a notification, an estimate, or the tracking page has gone stale. This is the same documentation drift that degrades every operational doc, and here it shows up as tickets you used to prevent quietly coming back.

Where to start this week

Don't build the whole system at once. Do the two changes that deflect the most. First, turn on proactive shipped and out-for-delivery notifications if you don't have them, because that single layer cuts WISMO the most for the least effort. Second, put a concrete delivery estimate at checkout and in the order confirmation, so fewer tickets form in the first place.

Then tag your WISMO tickets so you have a baseline rate to drive down. You can't manage what you don't measure, and once you can see the number fall, the rest of the system is easy to justify.

ReccordSOP turns a process like this into a documented SOP with timestamped screenshots, and flags drift when your carriers, products, or notifications change underneath it. Generate your first SOP free at reccordsop.com.