Where is my order? (WISMO)
Customer asks, order and carrier events join instantly; on delay a new ETA is given and a trace opened.
Where is my order? (WISMO) is an agent scenario in the Retail & E-commerce sector running on the whatsapp, web, app, voice channels. Trigger: "Where is my order?" message on WhatsApp, web or app. The Order Supervisor coordinates 3 specialist agents (Intent Agent, Tracking Agent, Reply Agent) across 4 systems (Shopify / OMS, Carrier API (Yurtiçi, DHL), WhatsApp Business API, Zendesk); of 9 steps, 1 write to systems and 1 are checks or approvals. Outcome: Customer knows the status and new ETA, carrier trace opened, re-check scheduled.
Where is my order? (WISMO)
- WhatsApp: "my order hasn't arrived in 5 days, number 100482"
- Intent: WISMO · order #100482 · phone matched → verified
- Order has 3 items, shipped 2 Sep, tracking YK-7731 8820
- Carrier events: held at the transfer hub since 4 Sep, no movement for 2 days
- Plan: delay class → revised ETA → policy → carrier trace → reply
- Delay is carrier-side; revised ETA 10 Sep, confidence 82%
- Policy: delay > 7 days → 100 voucher; this case 5 days → information only
- Zendesk ticket #ZD-51937 opened, trace request sent to the carrier
- WhatsApp: status, revised ETA and live tracking link; automatic re-check on 10 Sep
- ■completed
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
"Where is my order?" message on WhatsApp, web or app
Customer knows the status and new ETA, carrier trace opened, re-check scheduled
Agents
Order Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Intent Agent
Understands the request, verifies order number and customer
detect_intentextract_order_refverify_customerTracking Agent
Joins order and carrier events, estimates the revised ETA
get_orderget_shipmentget_carrier_eventsestimate_etaReply Agent
Applies policy, composes the reply, opens a ticket when needed
check_delay_policycompose_replysend_whatsappcreate_ticketSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Order Supervisor | WhatsApp: "my order hasn't arrived in 5 days, number 100482" | — | 180 | — |
| 02 | reason | Intent Agent | Intent: WISMO · order #100482 · phone matched → verified | — | 420 | 260 |
| 03 | tool | Tracking Agent | Order has 3 items, shipped 2 Sep, tracking YK-7731 8820 | Shopify / OMS | 340 | — |
| 04 | tool | Tracking Agent | Carrier events: held at the transfer hub since 4 Sep, no movement for 2 days | Carrier API (Yurtiçi, DHL) | 460 | — |
| 05 | plan | Order Supervisor | Plan: delay class → revised ETA → policy → carrier trace → reply | — | 240 | 170 |
| 06 | reason | Tracking Agent | Delay is carrier-side; revised ETA 10 Sep, confidence 82% | — | 520 | 430 |
| 07 | verify | Reply Agent | Policy: delay > 7 days → 100 voucher; this case 5 days → information only | — | 380 | 290 |
| 08 | write | Reply Agent | Zendesk ticket #ZD-51937 opened, trace request sent to the carrier | Zendesk | 400 | — |
| 09 | notify | Reply Agent | WhatsApp: status, revised ETA and live tracking link; automatic re-check on 10 Sep | WhatsApp Business API | 300 | 240 |
Outfit stylist: a complete look by size, stock, budget and style
The customer sends a photo and a sentence; the agent builds three looks that are in stock, fit and within budget, and adds the chosen one to the cart.
Returns and refunds
Policy and history checked in seconds, label issued; the refund executes when the carrier scans the parcel.
Product Q&A assistant
Size, compatibility and spec questions answered from catalogue and return data; stock and price verified.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis