How to reduce WISMO: from tracking data to automated support
WISMO ("Where is my order?") tickets make up 25–40% of e-commerce support volume, and each contact an agent handles costs about €12. A three-layer approach reduces them: deflect with precise delivery promises and proactive tracking, triage with automation and routing, and resolve with delivery data inside the help desk. With Ingrid in Dixa, that data now also powers automated replies, delay routing and Mim, Dixa's AI agent, which answers "Where is my order?" without a human agent.
If you are an e-commerce leader across operations, logistics and CX seeing high volumes of delivery-related customer support tickets that cost you a share of margin per order, this article sets out a three-layer framework for reducing the cost of WISMO. It runs from deflection to triage to agent-side resolution, including the most persistent bottleneck: context switching inside the agent workspace. It also shows how the same delivery data now powers automated replies, delay routing and AI agent answers in Dixa.
WISMO stands for "Where is my order?", the most common type of e-commerce support inquiry. A WISMO ticket is any call, email or chat message asking about an order's status, location or delivery date. Its counterpart for returns is WISMR, "Where is my return?"
WISMO tickets as a margin problem
Every e-commerce support team knows the pattern. Order volumes climb, and delivery-related tickets climb with them. Industry estimates put WISMO tickets at 25–40% of e-commerce support volume, depending on season and how mature a retailer's delivery operations are. During peak periods like Black Friday and Christmas, that share can rise to 50% or more.
The direct costs add up fast. Agents typically spend several minutes on each ticket as they move between carrier portals and tracking systems. Gartner puts the median cost of an assisted contact (phone, chat or email) at about €12, compared with about €1.60 for self-service. For a mid-market retailer shipping 50,000 orders a month, a 5% WISMO rate means 2,500 tickets a month, or about €30,000 in assisted-contact cost at that median, and the cost grows in step with order volume. To find your own WISMO rate, divide the number of WISMO tickets by the number of orders shipped in the same period.
WISMO tickets as an experience problem
While 90% of shoppers want to track their orders for peace of mind and a sense of control, the reality falls short: one in three online shoppers couldn’t track their most recent order. Many are flooded with generic carrier notifications or asked to enter order numbers and PIN codes. All they really need to know is when their parcel will arrive.
Returns can be just as frustrating. 'Where's my return?’ (WISMR) inquiries tend to arrive with higher emotional stakes, as the customer has already parted with the product and is waiting on money back. Tolerance for delay is lower, and data fragmentation increases. For agents, resolving a return status inquiry typically means navigating even more systems than an outbound shipping question.
Where the market stands
The retail tech industry has made meaningful progress on the customer-facing side, like branded tracking pages, proactive post-purchase notifications, AI chatbots. These tools catch many delivery status questions before support requests reach a human agent. Proactive, automated delivery status communication keeps customers informed every step of the way, because they can see the shipping progress without asking.
On the agent side, the gap remains. When a customer does contact support about delivery delays or split shipment, the workflow in most e-commerce teams hasn't changed in years and looks something like this:
- Open the help desk;
- Find the order status;
- Switch to a carrier portal;
- Cross-reference the OMS;
- Piece together a response.
That's several minutes per ticket, repeated hundreds of times a day, at a time when integrations, automation and AI are widely available. Most retailers have invested in deflection and triage. Far fewer have tackled resolution by giving agents the delivery data they need, in the workspace where they already operate, without switching systems. That's where the efficiency gains are still waiting.
A 3-layer framework to reduce WISMO tickets
Reducing WISMO and WISMR works best as a layered approach across deflection, triage and resolution. Here's what each layer looks like in practice.
1. Deflection
Stop tickets before they start with your brand's post-purchase experience. The highest-impact move is eliminating the need for customers to ask in the first place. That means setting accurate customer expectations before purchase, as early as marketing ads and product pages, and maintaining proactive communication after checkout.
Set precise delivery promises
Generic '3–5 business days' estimates create ambiguity, and ambiguity creates tickets. Precise ETAs, calculated from zip code, stock location and carrier capacity, give shoppers a specific delivery window before they buy. When shoppers know exactly when to expect their order, they have less reason to follow up with customer support agents. Surface your delivery promises and potential delivery delays on product pages and checkout.
Communicate proactively
Most delivery anxiety builds in the gap between order confirmed and out for delivery. Automated, branded notifications at each milestone (dispatched, in transit, out for delivery, delivered) keep shoppers informed and engaged. Post-purchase tracking works best across several channels, such as a branded tracking page, proactive notifications via email and SMS, as well as an integration with marketing and CX platforms like Voyado and Klaviyo for on-brand messaging and personalized experiences.
IDEAL OF SWEDEN, a lifestyle brand for mobile accessories and bags, cut WISMO tickets from 37% to 4% of support volume with proactive tracking, which reduced the load on its support team and improved the customer experience.
2. Triage
Even the best deflection strategy won't intercept every inquiry. Customers will still reach out about edge cases or simply because they prefer human contact. The goal at this layer is to resolve simple delivery questions instantly through automation, and route complex ones to the right agent fast.
AI chatbots handle the repetitive volume
A well-configured chatbot can pull real-time order and tracking data to answer 'Where is my order?’ without human involvement. AI chatbot platforms like Kindly integrate with delivery and CX systems to provide instant, accurate responses that deflect routine tickets and escalate genuine issues to human teams. AI agents inside the help desk now work the same way: Mim, Dixa's AI agent, uses Ingrid tracking data to answer WISMO questions with the current status and estimated delivery date.
Smart routing gets the rest to the right place
Tickets that need a human can be resolved best when classified by intent and urgency, then routed to the agent best equipped to resolve them. Help desks such as Dixa offer AI-powered classification and routing that keeps delivery inquiries from clogging general queues. When the help desk can read shipment status, routing can act on delivery data too, for example by sending delayed-delivery conversations straight to the team that handles carrier exceptions.
Layer 2 handles much of the remaining volume, but it still depends on the agent having the right data when a ticket lands on their screen.
3. Resolution
That's the layer most retailers have not addressed. When a customer reaches a human agent about a delivery issue, the resolution speed comes down to one thing: how fast the agent can access accurate shipment data.
In most setups, that means switching between the help desk, one or more carrier tracking portals, and the order management system (OMS). Each platform has its own login, its own data format, its own gaps. Multiply that by hundreds of tickets a day, across multiple carriers and markets, and the inefficiency becomes structural.
The fix is embedding carrier-agnostic delivery data directly inside the agent workspace, so the agent sees real-time shipment status, tracking timeline, carrier details, and order items without leaving the conversation to check multiple tabs and copy-paste tracking numbers.
That's what the integration between Dixa and Ingrid addresses, and where the next section picks up.
How Dixa and Ingrid resolve WISMO on a single screen
The integration between Dixa and Ingrid embeds unified delivery data directly inside the agent workspace as a conversation card. When a customer contacts support, the integration automatically looks up their orders by email and surfaces shipment information alongside the conversation, no manual search required.
What agents see without leaving the help desk:
- Order details including items, quantities, and order value;
- Real-time parcel status across 350+ carriers in a single, unified format;
- Estimated delivery timelines with specific date and time range;
- Delivery type and pickup location for locker or service point deliveries;
- Carrier tracking ID with a direct link to the carrier's tracking page;
- Split-shipment visibility when an order ships in multiple parcels.
The operational difference is simple. Instead of opening carrier portals, cross-referencing order management systems and piecing together a response across multiple tabs, the agent has everything on one screen. A delivery inquiry that used to take several minutes can be answered in seconds.
Retailers working with multiple carriers across different markets face the worst version of the context-switching problem, where each carrier has its own portal, its own status terminology, its own data format. The integration normalizes this into a single, carrier-agnostic view. Whether a parcel ships with PostNord, Royal Mail, DHL or any other carrier integrated with Ingrid, the agent sees the same structured data in the same place.
Paul Smith, Get Inspired and Widforss already use the integration to reduce WISMO ticket volume and to personalize conversations based on customer and order data.
From delivery data on screen to automated delivery support
Until now, the integration helped human agents answer faster. Ingrid tracking data appeared in Dixa's conversation card, so the agent could check shipment status without switching tools and then reply to the customer.
Dixa can now use the same data to act on its own. Ingrid powers automated delivery replies and delay-routing workflows in Dixa, and Mim, Dixa's AI agent, uses Ingrid tracking data to answer WISMO without a human agent stepping in.
Automated delivery replies and delay routing
In Dixa Automations, an Ingrid platform action retrieves tracking for a full order or for a single parcel. The returned tracking status, carrier, tracking link and estimated delivery date become flow variables that teams can use in conditions, messages and custom attributes. Common workflows include:
- Automated WISMO replies with the current shipment status and estimated delivery date;
- Sharing the carrier tracking link directly in the conversation;
- Routing delayed-delivery conversations to the right queue or team, based on shipment status and delivery alerts;
- Saving delivery data to the conversation as custom attributes, so teams can report on what drives delivery contacts.
Mim answers WISMO questions on its own
Mim retrieves Ingrid tracking data during a conversation and answers the customer directly, including shipment status and estimated delivery date. Because Ingrid normalizes tracking data across 350+ carriers, Mim gives the same kind of answer whichever carrier delivers the parcel. When a question goes beyond order status, the conversation can move to a human agent, who still sees the full delivery context in the conversation card.
The tracking data is the same as before. What has changed is how many ways Dixa can use it without manual agent work: agents read it in the conversation card, automations act on it in workflows, and Mim uses it to answer customers in real time.
What it means for your teams and operations
Operational efficiency
Proactive tracking and self-service reduce inbound delivery tickets. Automations and Mim resolve routine WISMO conversations without an agent, handle time drops on the conversations that remain, and support costs grow more slowly than order volume.
Customer experience
Customers get faster answers to delivery and WISMO questions backed by accurate, real-time data from Ingrid's carrier network, consistent across every carrier and delivery method. Proactive communication throughout the journey reduces the need to reach out in the first place.
Strategic benefits
The integration creates a unified delivery data layer across the CX stack, which gives teams better visibility into what drives delivery-related support volume. It also gives retailers a consistent setup to build on as they expand into new markets.
Where to start
If your operations and CX teams are evaluating your delivery and support stack, the three-layer framework offers a practical way to audit it: map your current WISMO and WISMR volume against deflection, triage and resolution capabilities.
Most retailers will find the first two layers partially covered, and the third barely addressed. The cost of delivery and return status tickets doesn't have to grow with order volume, and the integrations to change that already exist.
Set up the integration in minutes
If you are a retailer already using Dixa and/or Ingrid, follow this step-by-step setup guide to connect the integration and start optimizing your team's operational efficiency from a single screen. To use Ingrid data in automated workflows, add an Ingrid platform action to your flow, as described in Dixa's guide to Ingrid in Automations.
FAQs
What does WISMO mean?
WISMO stands for "Where is my order?". It describes any customer contact about an order's status, location or expected delivery date, whether it arrives by phone, email, chat or social media. In e-commerce, it is usually the largest single category of support inquiries.
What is a WISMO ticket?
A WISMO ticket is a support request in which a customer asks where their order is or when it will arrive. Most WISMO tickets can be answered with the same few data points: shipment status, carrier, tracking link and estimated delivery date.
How do you reduce WISMO calls and tickets?
Retailers reduce WISMO in three layers. Deflection prevents tickets with precise delivery promises and proactive tracking notifications. Triage answers routine questions automatically and routes the rest to the right team. Resolution gives agents delivery data inside the help desk, so the remaining tickets take seconds instead of minutes.
Can AI agents handle WISMO tickets?
Yes, when they have access to accurate tracking data. In Dixa, the AI agent Mim retrieves Ingrid tracking data during a conversation and answers with the shipment status and estimated delivery date. Questions that go beyond order status can move to a human agent, who sees the same delivery context.
What is the difference between WISMO and WISMR?
WISMO covers outbound orders on their way to the customer. WISMR, "Where is my return?", covers return shipments and refunds. WISMR inquiries often carry higher stakes, because the customer has already sent the product back and is waiting for their money.
About Dixa
Dixa is the AI-powered customer service platform for e-commerce brands. We unify all channels, automate routine inquiries with agentic AI, and give agents the context they need to deliver exceptional experiences. E-commerce brands using Dixa see 20%+ efficiency gains. Trusted by 500+ brands including Rapha, GANT, and Hobbii, Dixa is headquartered in Copenhagen with teams across Europe and the US.
About Ingrid
Delivery is the last untapped commercial lever in retail. Ingrid's Agentic DeliveryOS runs delivery end to end, from the promise to the return. Built on shopper, retailer, and carrier intelligence, it replaces static rules with delivery decisions that drive revenue, margin, and trust with every order. The system decides what to promise, which delivery options to show, and how each order ships, and every order makes the next decision smarter. API-first and ready for agentic commerce, it connects delivery to the rest of the commerce stack and to the AI agents starting to shop on consumers' behalf. Trusted by 250+ leading retailers, including Paul Smith, ME+EM, Nordic Nest, NA-KD and Adlibris, across 170+ markets.
FAQs
What does Ingrid Platform do?
Ingrid is the leading delivery intelligence platform that helps retailers turn delivery from a cost into a commercial advantage. Its modular platform connects retailers, carriers and shoppers across the whole shopping journey — discovery, checkout, tracking, transport, in-store and returns — so every delivery decision drives conversion, margin and loyalty on top of fulfillment and logistics.
How is Ingrid different from other delivery and shipping tools?
Most tools own a single touchpoint: logistics-led platforms stop at booking and labels, and post-purchase tools only start after the sale. Ingrid connects carrier choice to conversion and margin, with built-in A/B testing to prove what works. It gives retailers flexibility, choice and control instead of a fixed, one-size-fits-all setup.
Who is Ingrid for?
Ingrid is built for mid-market and enterprise e-commerce and omnichannel retailers shipping across multiple carriers, markets or delivery methods. Typically heads of e-commerce, logistics and operations leaders who want to turn delivery into a measurable revenue and margin lever. Retailers like Paul Smith, NA-KD, Apoteket, Nordic Nest and Mint Velvet use it to raise AOV, lift conversion, cut delivery-related support, implement direct exchanges, and increase delivery profitability.
Why does delivery intelligence matter?
Product and price used to decide the sale; now delivery does, too. Shoppers increasingly choose by delivery availability — same-day, next-day, pickup or in-store — while AI shopping agents rank retailers on delivery signals rather than branding. Ingrid helps retailers adapt with personalized delivery experience from checkout to returns. Back-end delivery intelligence contains cost and increases revenue, so delivery becomes a competitive advantage.






