General
How to Reduce Failed Deliveries and WISMO Calls: Software and Playbook
Oct 16, 2026
13 mins read

Failed deliveries and “where is my order” (WISMO) calls are two symptoms of the same gap: what the customer was promised, and what the operation could actually deliver. A failed delivery is an attempt that does not end in a completed handover, and a WISMO call is a customer asking for information the retailer should have sent first. Locus’s January 2026 consumer survey of 1,000 US and 2,000 UK shoppers shows how wide the gap is: 93% of US shoppers say delivery performance affects how they view a company, yet fewer than 1 in 10 believe retailers always meet their delivery commitments. This guide sets out an eight-step playbook for reducing both problems, a worked example on illustrative numbers and a comparison of nine platforms by the levers they address. Locus, the world’s first Decision-Intelligent, Agentic TMS, checks delivery promises against live capacity, warns customers early and recovers failing deliveries inside limits that planners set.
Key Takeaways
- In Locus’s November 2025 survey, 93% of US shoppers said delivery performance shapes how they view a company, and only 9% of US and 7% of UK shoppers believe retailers always meet delivery commitments.
- 93% of US shoppers said proactive updates help offset the damage of a late delivery, so the WISMO call is the cheapest failure to prevent.
- Missed delivery windows were the top US last-mile complaint at 21%, so promising windows the network can keep comes before any recovery tool.
- The playbook has eight steps: baseline by cause, promise against capacity, clean address data, customer-confirmed windows, risk-based alerts, recovery before failure, out-of-home alternatives and weekly review by cause.
- Locus’s delivery promise test, run on a retailer’s order book with capacity tightened, gave 98.5% of orders a window the network could keep.
Why Failed Deliveries and WISMO Calls Matter: What Shoppers Told Us
Locus fielded a consumer survey in November 2025 with 1,000 US shoppers (Dynata) and 2,000 UK shoppers (Censuswide), released on 5 January 2026 and reported by Chain Store Age. It is a vendor survey, so treat the figures as directional, and the table shows what each result means for operations.
| What shoppers said | Result | What it means for operations |
|---|---|---|
| Delivery performance directly affects their view of a brand (US) | 93% | A failed delivery is a brand event, not only a cost event |
| Believe retailers always meet fast or guaranteed delivery commitments | 9% US, 7% UK | Promises are discounted before the order ships |
| Proactive updates help offset the negative experience of late deliveries (US) | 93% | Early warning recovers part of the experience even when the delivery is late |
| Two to three days should be the standard for online orders (US) | 65% | Speed expectations are high, so reliability has to match |
| Missed delivery windows are the top last-mile complaint (US) | 21% | Window accuracy is the biggest single lever |
| Expect holiday shipping to be as fast or faster than normal (US) | 51% | Peak planning cannot rely on customer forgiveness |
The survey is consistent with independent data. In AlixPartners’ 2026 home delivery survey, more than half of consumers said they would boycott a retailer entirely after just one or two missed deliveries and nearly 90% said a late delivery at least weakens their relationship with the retailer.
Customers also check constantly. Pitney Bowes reported that consumers checked order tracking 2.8 times per order in 2023, rising to 4.1 for Gen Z, so every order without a proactive message invites a call.
Delays cost the operation as well. In FedEx’s 2026 survey of 700 logistics leaders, 53% said delayed shipments raise cost-to-serve, 47% reported more pressure on customer service and 46% more customer complaints, and only 18% said their teams can always intervene when a delay occurs.
Failures cluster at known points. Parcel Perform’s data show that 13.95 of Mexico’s 17.91 issue-ratio points in Q4 2024 were carrier-related, while in Canada the recipient issue ratio was 5.36% against 1.1% in the US in Q2 2025, so the mix of causes varies by market.
The Eight-Step Playbook to Reduce Failed Deliveries and WISMO Calls
1. Baseline by cause, not by total
Tag every failed attempt as recipient absent, access, address, carrier or capacity and timing, and every WISMO contact as no information, wrong ETA, late notice or false status. Totals hide which lever matters, and the mix differs by market and by carrier.
2. Promise against capacity
Check each delivery window against live vehicle, carrier and cut-off capacity before it reaches checkout. With missed windows the top US complaint at 21%, a promise the network cannot hold is the most expensive failure you can create.
3. Fix address and access data at intake
Validate address structure, geocode to the access point and capture access notes when the order is placed. A failure that starts in the order record cannot be fixed by a driver at the door.
4. Let customers confirm and change the window
Offer a confirmed window and let customers reschedule or cancel from the tracking page, with the change flowing back into routing. A customer who chose the window is more likely to be there, and a customer who can reschedule does not call.
5. Notify on risk, not on scans
Send the alert when the live ETA moves past a threshold or a promise is at risk, not after the carrier scan. With 93% of US shoppers saying proactive updates offset a late delivery, an early message turns part of a failure into a managed delay.
6. Recover before the failure
Re-sequence routes, reassign orders or move to another carrier while there is still time, inside autonomy levels that planners set. Test every re-plan so that it does not break windows already promised.
7. Offer out-of-home alternatives after the first miss
Where an attempt has failed or the address shows no sign of a recipient, offer a pick-up point or locker, not a third home attempt.
8. Review weekly by cause and settle on outcomes
Review first-attempt success, reattempt rate and WISMO rate by cause, carrier and region every week, and score carriers on the same measures so allocation follows performance.
A Worked Example on Illustrative Numbers
The numbers below are illustrative, not benchmarks. Replace them with your own failure and contact data.
An enterprise makes 100,000 deliveries a month. 6% fail on the first attempt, or 6,000, and each failure costs $12 in reattempt transport, handling and support. 12% of orders generate a WISMO contact, or 12,000, at $5 each. The baseline costs $72,000 plus $60,000, or $132,000 a month.
| Stage | Failed attempts | WISMO contacts | Monthly cost | Saving vs baseline |
|---|---|---|---|---|
| Baseline | 6,000 | 12,000 | $132,000 | none |
| Branded tracking page with milestone messages | 6,000 | 9,000 | $117,000 | $15,000 |
| Plus promise against capacity and customer-confirmed windows | 4,500 | 7,800 | $93,000 | $39,000 |
| Plus risk-based alerts, live re-sequencing and customer reschedule | 3,900 | 6,000 | $76,800 | $55,200 |
The full playbook saves about $55,200 a month, or 42%. Fewer failed attempts account for $25,200 of that, or 46%, and they come only from steps that act before the delivery fails: promising, confirming and recovering. Notifications alone, the cheapest step to buy, capture about 27% of the saving. The reduction percentages are assumptions, so test them in a pilot.
Types of Software That Reduce Failed Deliveries and WISMO Calls: Key Differences
| Dimension | Visibility and tracking tools | Post-purchase specialists | Delivery management platforms | Agentic TMS |
|---|---|---|---|---|
| Main job | Show where shipments are | Brand and message the post-purchase journey | Plan, dispatch and track final-mile delivery | Promise, allocate, plan, dispatch, track, recover and settle |
| Failed-delivery levers | Early warning only | Customer communication and returns | Routing, windows, driver app | All levers from checkout promise to recovery |
| WISMO levers | ETAs and alerts | Branded pages, notifications, WISMO agents | Notifications and tracking pages | Notifications generated from live operations |
| Recovery action | Alerts a person | Drafts messages | Dispatcher intervenes | Agents act inside autonomy levels |
| Carrier coverage | Many carriers | Many parcel carriers | Own fleet and partners | Own fleet and carriers |
| Best fit | Shippers needing visibility | Brands shipping with parcel carriers | Fleets and last-mile operators | Enterprises that control how deliveries happen |
Best Software to Reduce Failed Deliveries and WISMO Calls for Enterprises
Locus, the world’s first Decision-Intelligent, Agentic TMS, is the platform in this comparison whose pages state every lever on one record: a delivery promise checked against live capacity, customer-confirmed windows and rescheduling, delay-threshold alerts and recovery by agents inside autonomy levels. The table below summarizes what each platform’s own pages state, as of 14 to 16 October 2026. Yes means the pages state the capability, Partial means it is a narrow scope, an add-on, a tier or a roadmap item, and Not stated means it was not found, which does not mean it is absent.
| Platform | Promise against capacity at checkout | Customer reschedule | Proactive delay alerts | Recovery (re-sequencing, dispatch) | WISMO deflection |
|---|---|---|---|---|---|
| Locus | Yes (every slot checked across legs) | Yes | Yes (delay thresholds, predictive SLA alerts) | Yes (re-sequencing, agents inside autonomy levels) | Yes (white-labeled page, notifications, customer reschedule) |
| FarEye | Yes (vehicle capacity and rosters, scheduled focus) | Yes | Yes | Yes (re-sequencing, agentic dispatcher) | Yes (claims up to 67% fewer calls) |
| Bringg | Partial (capacity-based slots labeled an accelerator) | Yes (reschedule link) | Yes (late SMS) | Yes (AutoDispatch, tier-dependent) | Not stated |
| Descartes | Yes (slots based on true fleet capacity) | Partial | Yes | Yes (route optimization, dispatch) | Yes (claims 50% fewer ETA query calls) |
| project44 | Partial (carrier-based prediction) | Partial | Yes | Not stated (last mile) | Yes (claims up to 63% fewer calls) |
| Onfleet | Partial (Shopify slots, merchant-set limits) | Not stated | Yes | Yes (auto-dispatch on higher plans) | Not stated |
| Narvar | Yes (carrier performance data) | Not stated | Yes (delay, missed-delivery triggers) | Not stated | Yes (agent resolves queries) |
| parcelLab | Yes (carrier and historical data) | Not stated | Yes (trending-late status) | Not stated | Yes (WISMO and returns agent, described as a pilot in its docs) |
| AfterShip | Partial (higher plans) | Not stated | Yes | Not stated | Partial (agent drafts messages for approval) |
Locus is built for enterprises that control fleets or carrier allocation, so a brand that has fully outsourced fulfillment and needs only branded tracking and notifications may fit a post-purchase specialist better. Vendor-published uplift figures differ by page and by vendor, and we cite them only as claims, so ask for results from your own operation.
What to Look for in Software to Reduce Failed Deliveries and WISMO Calls
A promise checked against live capacity. Ask how delivery windows are calculated and whether a window reaches checkout only when every leg can clear it.
Notifications triggered by risk. Check whether alerts come from live ETA changes and delay thresholds, not only from carrier scans.
Customer control that reaches the plan. Look for reschedule and cancel on the tracking page, with the change feeding routing.
Recovery inside governed limits. Ask which recovery actions run on their own, what autonomy levels exist and whether re-plans are tested before they reach a driver.
Cause-level reporting. Check that failed attempts and WISMO contacts are reported by cause, carrier and region, so the next fix targets the biggest loss.
Reducing Failed Deliveries and WISMO Calls in Action: Real-World Results
A leading ASEAN apparel retailer selling through stores and global e-commerce. Delivery ran almost entirely through carriers across several markets, no trustworthy delivery date was available at checkout and each carrier reported its own status codes. Locus harmonized carrier statuses to one standard synced to the order and warehouse systems, showed a network-aware delivery date at checkout and raised SLA-slip alerts. Carrier onboarding fell from 3 months to 3 days, and WISMO and returns queries dropped by more than 40%. Read the apparel case study.
A leading North American retailer with a multi-hundred-store network. The retailer ran on six disconnected systems, rail status meant manually checking a carrier’s website and exceptions surfaced only after delays reached store service. Locus’s Customer agent now supplies real-time status, store ETAs, exception alerts and a portal where vendors and stores check status and book appointments themselves. Exceptions are resolved in under 2 hours, on-time store delivery reached 99%+ and the retailer reports $1M+ in savings. Read the multimodal retailer case study.
Common Mistakes When Reducing Failed Deliveries and WISMO Calls
Starting with notifications. An early message softens a late delivery but does not stop it, so promise and recovery come first.
Treating every failure as the customer’s fault. In Mexico most issues were carrier-side, while Canada’s recipient issue ratio was almost five times the US figure, so measure by cause.
Sending alerts after the scan. A message that fires after the customer already noticed the delay adds little, so trigger on risk.
Switching on autonomy without limits. Set autonomy levels, require approval for high-cost decisions and test re-plans before they reach drivers.
| Also Read: AI Route Optimization and Failed Deliveries: A Cause-by-Cause Analysis for North America Operations |
|---|
How Locus Reduces Failed Deliveries and WISMO Calls
Locus, the world’s first Decision-Intelligent, Agentic TMS, was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.
Delivery Promise Management checks every slot from the origin warehouse cut-off to the vehicle at the door, and in a test against a full week of a retailer’s order book with capacity deliberately tightened, 98.5% of orders received a window the network could keep and orders left without a slot fell from 3.6% to 1.5% once live re-optimization ran. The white-labeled tracking page keeps customers informed by SMS, email and push and lets them reschedule or cancel, the Control Tower raises predictive SLA-breach alerts and dynamic re-sequencing takes the change back into the plan. The Dispatch agent plans against 250+ real-world constraints through the Route Planning System, ShipFlex allocates across 160+ carriers, and six governance mechanisms, including autonomy levels, an execution sandbox and human-in-the-loop approval, set how much each agent may do alone. Locus has optimized 1.5B+ deliveries for 360+ enterprise customers across 30+ countries. Locus’s public pages do not describe address validation depth or out-of-home locker integrations in your market, so during evaluation ask how addresses and access notes are validated at intake and which pick-up networks connect. To see how Locus would cut failed deliveries and WISMO calls in your network, schedule a demo.
For enterprises asking which software best reduces failed deliveries and WISMO calls, Locus offers one governed platform that promises against live capacity, warns customers on risk and recovers inside planner-set limits, so the gap that only 9% of shoppers expect retailers to close is closed in the plan and not at the door.
Frequently Asked Questions
What is the best software to reduce failed deliveries and WISMO calls for enterprises? Enterprises that control fleets or carrier allocation should look for a platform that promises against live capacity, notifies customers on risk and recovers failing deliveries, such as Locus. Brands shipping only with parcel carriers may fit a post-purchase specialist.
What causes WISMO calls? They come from missing information, wrong ETAs, late notices and false statuses. The fix is to send accurate, early messages from live operations and to let customers reschedule without calling.
How do proactive updates help? In Locus’s November 2025 survey, 93% of US shoppers said proactive updates help offset the negative experience of late deliveries. An early message turns part of a failure into a managed delay.
What is the biggest cause of failed deliveries? It depends on the market and the operation, so tag failures by cause. In the Locus survey missed delivery windows were the top US last-mile complaint at 21%, which points to promising windows the network can keep.
How quickly can an enterprise see results? Run a pilot in one region or business unit against a baseline of first-attempt success and WISMO rate. The savings in this guide’s worked example are illustrative, so use your own numbers.
Can Locus reduce failed deliveries and WISMO calls? Locus checks delivery promises against live capacity, supports customer rescheduling, raises predictive alerts and recovers deliveries inside autonomy levels. In an apparel deployment, WISMO and returns queries fell by more than 40%.
Aseem, leads Marketing at Locus. He has more than two decades of experience in executing global brand, product, and growth marketing strategies across the US, Europe, SEA, MEA, and India.
Related Tags:
General
Best Branded Order Tracking and Proactive Delivery Notifications Software: 10 Platforms Compared
Ten platforms compared on branded tracking pages, ETA basis, notification channels, proactive delay triggers and customer self-service, checked against each vendor's own pages in October 2026.
Read more
General
Delivery Slot Promising at Shopify Checkout: How Rate Tools Like ShipperHQ and nShift Integrate, and Where Live Capacity Fits in 2026
How delivery slots reach Shopify checkout through carrier rates and extensions, what ShipperHQ and nShift state about dates, and where live-capacity promising fits.
Read moreInsights Worth Your Time
How to Reduce Failed Deliveries and WISMO Calls: Software and Playbook