AWS Glossary
WISMO (Where Is My Order)
WISMO is the order-status enquiry — typically the single highest-volume contact type in eCommerce support, and the most common first workload for a customer-facing AI agent.
Definition
WISMO — “where is my order” — is the order-status enquiry. It covers the whole family of post-purchase questions: has it shipped, where is it now, why is it late, it says delivered and I do not have it, can I change the address.
In most eCommerce support operations it is the highest-volume contact type by a wide margin, and it is almost entirely a data-retrieval problem wearing a conversation as a costume.
Why it is usually the right first agent
When ranking candidate agent workloads on volume, data readiness, blast radius and effort, WISMO tends to win on all four:
- Volume. It is the biggest single bucket, so even modest deflection is material.
- Data readiness. The answer lives in your order and carrier data, which you already have — unlike margin work, where cost data is usually nowhere near the storefront.
- Blast radius. The dominant action is a read. Nothing moves money.
- Existing escalation path. Support already knows what to do when it gets hard, so the human gate is a workflow that exists rather than one you must invent.
Where it stops being simple
The easy 70% is a lookup. The remainder is where the design work is:
- Split shipments. One order, three parcels, two carriers, one of which shows delivered.
- Delivered-not-received. The highest-emotion case, frequently a fraud vector, and never a good candidate for autonomous resolution.
- Address changes mid-transit. A write, often with a carrier-side cost, and a natural approval gate.
- Carrier data that is stale or wrong. The agent must be able to say “the carrier has not scanned this since Tuesday” rather than inventing a status.
An agent that handles the lookup and escalates the rest cleanly is a success. An agent that improvises on delivered-not-received is a liability.
The measurement trap
Deflection rate alone is a misleading metric. An agent that closes conversations without resolving them will show excellent deflection and produce a second contact two days later, plus a worse outcome. Pair deflection with repeat-contact rate on the same order within seven days.
Related terms
AI agent · Human in the loop · Agentic commerce · Tool catalog
Related Services
eCommerce AI Agents on AWS
Production AI agents for eCommerce on Amazon Bedrock AgentCore — support and WISMO, inventory, merchandising, margin, returns and B2B. Tool boundaries, evals before launch, and a human on anything that moves money.
Amazon Connect Consulting
Amazon Connect consulting — contact center on AWS with voice, chat, Cases, flows, and Q in Connect. Designed and hardened by an AWS Select Tier Partner.
Related Articles
WISMO Automation with AI Agents: Order Lookup, Tracking, and Escalation (2026)
Monday again: where is my order. That pile is about 18% of helpdesk volume. Look up the scan. Do not invent a 2pm window. We are not publishing a tickets-down number.
AI Customer Support Agent for eCommerce: Tool Access, Escalation, and Audit (2026)
Monday, the same order and policy tickets. An agent looks them up. Where-is-my-order is about 18% of the pile. Refunds stay with a person. We are not publishing a tickets-down number.
AI Order Exception Management for eCommerce: Investigate First, Automate Only What Policy Allows (2026)
Checkout worked, then payments, stock, or fraud said no. An agent investigates; refunds and cancels wait for a person. Planning silhouette ~$791/mo at 50K sessions — not a client refund KPI.
AI Agent ROI for eCommerce: How to Decide What to Automate First (2026)
Rank automations by volume and feasibility — not promised payback. WISMO is about 18% of tickets. Start reads before inventory writes or POs.
Need help with this topic?
Our AWS-certified team implements, audits, and optimizes these services in production — from Bedrock RAG pipelines to multi-account landing zones.