Skip to main content
This blueprint shows how to design a Duckie system for WISMO (“Where Is My Order?”) operations in e-commerce. The example is a retailer that sells high-value computer parts, but the same pattern works for any order-status operation with OMS, warehouse, supplier, carrier, and support-history data. The recommended design uses deterministic workflows for the repeatable control points and autonomous specialist agents for ambiguous investigation, customer-safe explanation, and internal decision support.

​
Start With the MVP

You do not need to launch the full WISMO system at once. Start with a narrow loop that identifies the customer and order, pulls live order context, detects the most common WISMO condition, answers allowed status questions, and schedules a proactive follow-up when the status may change. Then add supplier backorders, warehouse exceptions, carrier investigations, delivered-not-received review, replacement/refund approval, and broader proactive event handling after the first loop is trusted.
Use the MVP as the starting point if you are building this blueprint for the first time.

​
What This System Does

The system helps a CX and operations team:
  • Receive WISMO questions from chat, email, ticketing, or backend events
  • Identify the customer, order, shipment, and active support case
  • Pull live OMS, WMS, supplier, inventory, carrier, and support-history context
  • Route the same customer intent to the right specialist handler based on actual order state
  • Send factual customer replies without generic status copy or unsupported ETA promises
  • Proactively update customers when backend tracking, fulfillment, or supplier status changes
  • Escalate high-value, repeated-contact, fraud/address-hold, or ambiguous cases to the right internal team
  • Gate replacement, refund, cancellation, and address-change actions behind policy and approval
  • Track conditions, outcomes, follow-up commitments, and automation quality
WISMO is not primarily an order lookup problem. The hard part is deciding what to say and do when the order state is stale, blocked, split across systems, or operationally ambiguous.

​
Design at a Glance

FunctionDuckie componentWhy
Customer and event intakeDeployments plus WISMO intake workflow or triage agentWISMO can start from tickets, chat, email replies, carrier events, supplier updates, or scheduled checks.
Order contextOrder context workflowCanonical OMS, WMS, supplier, inventory, carrier, hold, and support-history fields should be pulled in a repeatable order.
Ambiguous investigationOrder investigation agentConflicting or incomplete system data needs flexible tool choice and summarization.
Condition routingCondition routing workflowClear status rules, approval thresholds, and follow-up commitments should be auditable.
Specialist handlingStandard status, supplier, warehouse, split shipment, carrier, and delivered-not-received agentsThe expensive variation belongs in agent instructions, runbooks, knowledge, and guardrails.
Proactive follow-upProactive monitor workflow plus customer communications agentBackend changes should trigger customer updates before another ticket is opened.
Resolution and approvalResolution eligibility workflow plus Slack escalation agentReplacement, refund, cancellation, and address-change decisions need controlled gates.
AnalyticsCategories, attributes, resolution rules, and run reviewTeams need to see which WISMO conditions are resolved, monitored, escalated, or blocked.

​
Blueprint Pages

MVP

Start with the smallest useful WISMO loop before adding all exception handling.

System Map

See the workflow backbone, specialist agents, proactive follow-up, and human review path.

Intake and Order Context

Normalize customer requests and backend events into a consistent WISMO case.

Condition Routing and Agents

Route order states to the right specialist agent or controlled workflow.

Proactive Follow-Up

Send updates when backend tracking, supplier, warehouse, or shipment status changes.

Escalation and Resolution

Route human decisions and approval-gated actions through a structured internal loop.

Rollout Plan

Move from shadow-mode WISMO handling to broader live proactive operations.
  1. Start with the MVP to understand the smallest useful version.
  2. Read the system map to see how the components connect.
  3. Read intake and order context to understand the data contract.
  4. Read condition routing and agents to map order states to handlers.
  5. Add proactive follow-up once backend events are reliable.
  6. Add escalation and resolution before enabling high-impact actions.
  7. Follow the rollout plan before expanding live traffic.

Designing Agent Systems

Learn the general workflow-plus-agent design pattern.

Choosing an Agent Architecture

Decide when to use workflows, agents, runbooks, and human review.

Deployments

Connect Duckie to ticketing, messaging, webhook, and scheduled triggers.

Replay Testing

Test historical WISMO tickets before live customer replies.