Where-is-my-order is a lookup problem, not a conversation
Most where-is-my-order tickets ask for a fact that already exists in a system. That makes them the best first job for an AI assistant, if the lookup is safe.
RoutMe team
Product and engineering
Look at a week of your support inbox and sort the tickets by what the customer actually wanted. For many stores the largest pile is some version of where is my order. The customer is not asking for judgment or empathy. They are asking for a fact that already sits in your order system and your carrier's tracking page.
Why that matters for automation
A job that is mostly a lookup is a job a machine can do, provided it reads the real record. The hard part is never the sentence the assistant writes. It is making sure the lookup returns the right order for the right person, and nothing else.
The three decisions
- 1How the customer proves the order is theirs. An order number alone is a key, not proof. Ask for a second detail and check both in your own code.
- 2What the tool returns. Status, carrier, tracking link and estimate. Not the full address, not payment details.
- 3What happens when the lookup fails or the parcel is stuck. A person takes over, with the conversation and the order attached.
Where proactive messages fit
The cheapest ticket is the one that never gets sent. A message when the order ships, with the tracking link, removes the question for many customers. On WhatsApp that is a utility template, since templates are the way to reach someone outside the 24-hour customer service window. Check the rates for your markets on the pricing page before you design the notification flow.
Where to go next
The full playbook is in our guide on how to reduce WISMO tickets, and the safe lookup design is in how an AI agent looks up order status safely. The where-is-my-order solution page lists the steps in RoutMe.
- WISMO
- Ecommerce
- Order status
RoutMe team
Product and engineering
Practical guides from the people who build RoutMe, with every product claim checked against what is live today.
Keep reading
- Playbooks
Replace the Zap: a where-is-my-order automation, no glue code
Build a where-is-my-order WhatsApp flow without Zapier or glue code. Trigger, order lookup tool, reply, and a fallback to a person, step by step in RoutMe Flows.
- Playbooks
How to move a customer support workflow from n8n to RoutMe
A step-by-step migration of a WhatsApp support workflow from n8n to RoutMe Flows: node mapping, the agent step, connectors and a checklist to cut over safely.
See it on your own data
Connect a system, drop an agent node into a flow, and watch it answer from what is actually true in your systems right now.