WISMO KPIs: 8 Metrics to Measure Post-Purchase Success

TL;DR Summary

WISMO queries eat 30 to 50% of ecommerce support queues, and in the US each live-channel contact runs about $9 to $16, with phone climbing past $20. That spend only pays off if you can measure it. Track eight role-specific KPIs across your CS, Ops, and CX teams and post-purchase platform spend turns into ROI you can actually put in front of leadership.

• Run a baseline audit first. It is the only way to prove ROI once the platform changes anything.

• WISMO rate is the headline deflection number your CS manager owns.

• Delivery exception rate is the leading indicator that predicts ticket volume days ahead.

• EDD accuracy is the Ops metric that closes the expectation gap at checkout.

• First contact resolution shows whether your tracking page actually answers the question.

• CSAT and repeat purchase rate connect delivery trust to revenue.

• A 30/60/90-day roadmap tells you when each KPI should start moving.

Introduction

WISMO queries account for 30 to 50% of all customer support tickets at ecommerce brands, and they push past half the queue during the holiday peak. Gorgias ecommerce CX data and Zendesk's CX Trends research both point to the same thing: order status is the top reason customers contact support.

US brands feel this at scale. A single phone or live-chat contact costs roughly $9 to $16 to resolve, and phone runs higher still. Gartner puts the median assisted-channel contact at $13.50. WISMO KPIs are the measurement layer that tells you whether a post-purchase platform is earning that money back.

Here is where a lot of brands come up short. They roll out a platform for branded tracking and proactive notifications, then never build the measurement framework around it. Without clear benchmarks, they cannot prove ROI to leadership, and they cannot see where the platform needs work.

Two definitions matter before anything else. Use orders shipped as the denominator, not total support tickets. Salesforce's WISMO guide divides by total tickets, which dilutes the signal by mixing delivery contacts in with unrelated support volume.

The rest of this article covers a baseline audit, eight role-labeled KPIs, the US-specific metrics that global benchmarks tend to miss, and a 30/60/90-day roadmap.

Why WISMO is an Ops, finance, and CX problem at once

WISMO is not really a support category. It is a cross-functional signal that shows up differently depending on which dashboard you own. Picking WISMO KPIs without mapping them to the right owner is why so many measurement efforts stall out.

The CS manager sees ticket volume and agent burnout

When WISMO volume is high, agents spend 40 to 60% of a shift copy-pasting tracking numbers instead of handling work that moves revenue. Salesforce makes the point that every status-check ticket pulls the team away from closing sales or resolving harder issues, which is the real cost hiding behind a cheap-looking ticket.

The Ops manager sees exceptions and undeliverable shipments

Every delivery exception that you do not communicate proactively generates roughly 2 to 3 downstream WISMO tickets. That makes exception rate a leading indicator of WISMO volume, a causal chain almost no competitor article draws out. Customers who hear about a delay before they go looking are far less likely to open a ticket than those who discover it on their own.

The Head of CX sees CSAT erosion and churn

WISMO queries carry a heavier negative CSAT weight than the average ticket because they signal broken trust, not a simple missing answer. Zendesk Benchmark data shows that more than half of customers will switch to a competitor after a single bad experience, and 73% will after repeated ones. That is why repeat purchase rate is the downstream revenue consequence of WISMO you let get out of hand. The KPIs you track, and who owns them, should map to this three-team reality.

Capture these 6 baseline numbers before go-live

This is the most common gap in published guides. Almost none of them tell brands to measure before deploying. Without a documented baseline, any improvement claim is anecdotal, and you cannot hand it to leadership as ROI. The platform pays for itself, but only if you can show the before. Record these six numbers across a 30-day window at minimum, ideally 60 days to smooth out weekly seasonality.

• Current WISMO rate. WISMO tickets divided by orders shipped, times 100.

• Current CSAT, taken from the post-delivery survey average.

• Current first contact resolution (FCR) rate.

• Current average cost per ticket in USD.

• Current WISMO ticket volume as a share of total support volume.

• Current delivery exception rate for your top three carriers.

The 8 WISMO KPIs to track after your platform goes live

Track these eight KPIs after implementation, each owned by a specific role with a defined review cadence. For every one, you get how to calculate it, what good looks like in the US, the trade-offs, and when it is worth watching closely.

1. WISMO rate, best for CS managers proving deflection

This is the headline number, and the one leadership asks about first. It measures how many of your shipped orders trigger a status query, so it isolates delivery-related contact rate from general support noise.

Because proactive notifications cut inbound contacts right away, it is also the fastest-moving KPI you own. It usually shifts inside the first two weeks. Watch it weekly, not monthly, during go-live. A rate that refuses to budge points to notification coverage gaps, not a broken platform.

Formula: (WISMO tickets / orders shipped) x 100

Benchmark: below 3% is world-class, 3 to 5% is strong, 5 to 8% is normal but removable, above 8% points to something structural. Expect a 40 to 50% reduction within 30 days of go-live.

2. Ticket deflection and AI resolution rate, best for measuring self-service

Deflection and resolution are not the same thing, and blurring them hides where the platform is working. Deflection means the customer never contacts support because the tracking page or notification answered the question first.

Resolution means they did contact you but got a fast, one-touch answer. Vendors report AI resolution rates for order-status tickets running as high as 64 to 95% when a bot is wired into live order data from Shopify and the helpdesk. Treat those figures as vendor-reported ceilings, not typical results.

Formula: (tickets resolved without agent contact / total WISMO contacts) x 100

Benchmark: 60 to 70% deflection is achievable with a branded tracking page plus SMS and email notifications.

Verdict. Track deflection and resolution as two separate lines, or you will overstate how well the tracking page alone is doing.

3. Cost per WISMO ticket, best for the finance conversation

This KPI turns WISMO from a support headache into a measurable business cost. Combine agent salaries, support tools, and channel costs, then divide by your WISMO ticket volume. The gap between channels is large.

US benchmarks from Gartner and SQM put live channels like phone and chat at $9 to $16 per contact, with phone reaching $17 to $25 at the high end. Automated self-service resolves the same query for under $2. Moving customers to self-service and SMS is where the savings come from.

Formula: total WISMO support cost / WISMO ticket volume

Benchmark: $9 to $16 per ticket via phone or chat, under $2 via automated self-service, target below $6 blended after the platform is live.

Verdict. Break the number down by channel. The blended average hides your most expensive queue.

4. First contact resolution, best for judging tracking quality

FCR measures how well your tracking updates and notifications answer the question on the first contact. A low WISMO FCR means your updates are missing information customers need, so they come back.

Every repeat inquiry adds cost, because one shipment-status question turns into several follow-ups. In the US, each repeat live-channel contact adds another $9 to $16, which makes thin shipment communication an expensive problem.

Formula: (tickets resolved on first contact / total WISMO tickets) x 100

Benchmark: above 75% is strong, below 60% means the tracking page or notification is too thin.

Verdict. Treat a sub-60% WISMO FCR as a content problem on the tracking page, not an agent problem.

5. CSAT (post-delivery), best for the Head of CX

Measure CSAT through post-delivery surveys rather than your overall CSAT score. It gives you a cleaner read on the post-purchase platform. This KPI reflects the customer experience, so it usually improves after operational metrics start moving.

Do not panic if CSAT stays flat for the first few weeks. It often takes 30 to 45 days to climb, as your team spends less time on repetitive WISMO queries and more time on the issues that actually move satisfaction.

Formula: (positive ratings / total delivery-experience survey responses) x 100

Benchmark: above 82% is strong, 75 to 82% is average, below 75% needs intervention.

Verdict. Report it monthly, not weekly, and always scoped to the post-delivery survey alone.

6. EDD accuracy rate, best for the Ops early-warning system

Estimated delivery date accuracy is the Ops-layer metric that almost no competitor lists as a WISMO KPI, and it is one of the most predictive. When EDD accuracy drops, WISMO volume rises within about 48 hours, so it works as an early warning gauge. Shopify's own guidance is that realistic delivery promises prevent WISMO by setting the right expectation at checkout.

Formula: (orders delivered on or before EDD / total orders) x 100

Benchmark: above 85% is strong, below 75% is a primary WISMO driver.

Verdict. Watch this daily for the first 30 days. It moves before WISMO rate does.

7. Repeat purchase rate, best for the long-term ROI story

This is the revenue-layer payoff, and the slowest to move. Improvement shows up 60 to 180 days after launch, not in the first month, because it depends on whole cohorts of customers finishing a post-purchase experience and coming back.

It is also the number that turns a support-cost story into a growth story when you present to leadership. Track it by cohort, comparing pre-platform and post-platform buyers over matched windows.

Formula: (customers with 2+ orders / total customers in cohort) x 100

Benchmark: above 30% is strong for DTC, above 40% is excellent. Expect directional 6 to 12% lift post-platform.

Verdict. This is the KPI you present at day 90, not day 30. Hold your ROI claim until the cohort matures.

8. WISMR rate (where is my return or refund), best for returns-heavy categories

WISMR is the post-return twin of WISMO, and almost no benchmark treats it as a standalone KPI. It spikes when return visibility is missing from your platform. Automated return-status alerts cut reverse-WISMO contacts by 40 to 60%, so instrumenting this early pays off fast.

Formula: (WISMR tickets / total returns initiated) x 100

Benchmark: not yet standardized. Target below 15% for returns-heavy categories.

Verdict. Instrument it now if returns run more than 10% of orders. You cannot fix a cost you never counted.

The complete WISMO KPI benchmark matrix

This master table covers all eight core KPIs plus delivery exception rate and return-to-sender rate, with role ownership and review cadence. US ranges are drawn from published benchmark data.

US ranges derived from published Gorgias, Zendesk, Shopify, and Gartner benchmark data. Treat as directional, not audited.

4 post-purchase KPIs US ecommerce brands should also track

Global frameworks stop at the eight KPIs above. US ecommerce needs four more, shaped by unattended porch delivery, package theft, and SMS-first messaging.

1. Delivery exception rate, the leading indicator your Ops team needs

Delivery exception rate equals shipments flagged with a carrier exception divided by total shipments, times 100. Exceptions cover failed attempts, address issues, weather holds, and misroutes. Benchmark: below 3% is strong, 3 to 6% is average, above 10% points to a carrier or address-quality problem. Track it weekly and watch WISMO volume respond within 24 to 72 hours of any spike.

2. "Delivered but not received" claim rate, the US porch-piracy signal

Package theft is a US-specific cost pool. When a carrier marks an order delivered and the customer never sees it, you get a WISMO ticket that turns into a claim or a reship. Claim rate equals delivered-not-received tickets divided by total delivered orders, times 100. Photo-on-delivery proof and delivery confirmation notifications cut these contacts, and they give your team evidence when a claim is disputed.

3. SMS notification opt-in and engagement rate, your deflection proof point

In the US, SMS outperforms email for post-purchase updates by a wide margin. SMS open rates are commonly cited near 98%, usually within minutes, against roughly 20% for email. Track opt-in rate alongside open and click-through, since TCPA consent gates how many customers you can even reach. If opt-in is low, deflection stalls no matter how good the notifications are.

4. Return-to-sender rate, the quiet revenue leak

Return-to-sender rate equals undeliverable shipments sent back to you divided by total shipments, times 100. Most of this leakage comes from bad addresses and failed final attempts. Benchmark: below 1.5% is strong for prepaid orders. Address verification at checkout plus proactive exception alerts is the fastest way to bring it down.

The 30-60-90 day WISMO KPI roadmap

Operational KPIs move first, experience KPIs follow, and revenue KPIs confirm the long-term value.

If WISMO rate has not moved by day 30, the problem is almost always notification coverage. Check carrier integration completeness and SMS opt-in rates before you decide the platform failed.

Pre-go-live WISMO KPI checklist

Work through these eight tasks in your first week after go-live to build a clean performance baseline.

• Export the last 30 days of support tickets and separate WISMO tickets from non-WISMO tickets.

• Calculate your current WISMO rate using orders shipped as the denominator, not total support tickets.

• Record your current post-delivery CSAT instead of your overall satisfaction score.

• Pull your current first contact resolution rate from your helpdesk, whether that is Gorgias, Zendesk, or Kustomer.

• Calculate average cost per ticket as agent costs plus tool costs, divided by total ticket volume.

• Review your delivery exception rate by carrier (UPS, FedEx, USPS) for the same 30-day period.

• Find your top three WISMO triggers, such as processing delays, carrier handoffs, out-for-delivery stalls, or missed EDDs.

• Schedule KPI reviews for day 30, day 60, and day 90 to measure progress.

Conclusion

A post-purchase platform is only as valuable as the measurement layer around it. Operational KPIs move first, experience KPIs follow, and revenue KPIs confirm the long-term value across 90 to 180 days. The single most important action is the baseline audit, and it has to happen before go-live, not after. Without a documented before, there is nothing to prove ROI against. Capture your six baseline numbers this week, then set your day 30, 60, and 90 reviews.

FAQ

What is a good WISMO rate for ecommerce?

A WISMO rate below 3% is world-class, and below 5% is a strong benchmark for US DTC brands. If your rate climbs above 8%, it usually means gaps in notifications or carrier integrations that produce avoidable order-status queries.

How do you calculate WISMO rate?

WISMO rate equals WISMO tickets divided by total orders shipped, times 100. Use orders shipped as the denominator, not total support tickets. That gives a clearer read on how many customers are contacting you about delivery, independent of unrelated support issues.

What KPIs should I track for post-purchase customer experience?

Start with eight core KPIs: WISMO rate, ticket deflection rate, cost per ticket, FCR, CSAT, EDD accuracy, repeat purchase rate, and WISMR rate. For US brands, add four more: delivery exception rate, delivered-not-received claim rate, SMS notification engagement rate, and return-to-sender rate.

How much does a WISMO ticket cost to resolve in the US?

A WISMO ticket runs about $9 to $16 through phone or chat, and phone can reach $25. Automated self-service brings that down to under $2. After a post-purchase platform is live, aim for a blended cost below $6 by moving more customers to self-service and SMS.

What is the difference between WISMO and WISMR?

WISMO stands for where is my order and covers questions about deliveries before the order arrives. WISMR stands for where is my return or refund and covers questions after a return has started. Tracking them separately shows whether delivery or returns are creating the friction.

How quickly can a post-purchase platform reduce WISMO ticket volume?

With full carrier integrations and strong SMS opt-in, brands typically see a 40 to 50% reduction in WISMO tickets within 30 days and 60 to 70% within 60 days. If the numbers do not improve after the first month, check notification coverage before you evaluate the platform's impact.

What is first contact resolution and why does it matter for WISMO?

First contact resolution measures the share of queries resolved in the first interaction without follow-ups. For WISMO, a low FCR usually means customers are not getting enough information from tracking pages or notifications, so they contact support more than once.

How do I reduce WISMO queries in the US specifically?

Focus on proactive SMS and email notifications, accurate EDDs at checkout, address verification, and exception-triggered alerts. Photo-on-delivery proof also helps with package-theft disputes. These touchpoints get updates to customers before they need to ask.