AI Chatbot Order Tracking: Connecting Orders and Shipping
"Where is my order?" is the most common question an online shop receives, and the one an AI chatbot should answer completely on its own. Doing that well takes three connections: finding the right order, reading the shipment status, and knowing what to hand over when the answer needs a person. This is how the chat in our case study does it across 15,445 conversations in the last 30 days, with agents stepping into the chat window zero times.
Find the right order
The chatbot asks for the order number or the email used at checkout and looks the order up in the shop system. The extraction step that picks the order number out of free text is where most errors start:
- Other numbers look like order numbers. A customer once included a police report reference, and an early pattern took its first part as an order number and linked the case to someone else's order. Test any extraction pattern against a large sample of real messages before release.
- Punctuation differs by language. A full-width colon in Asian-language text once caused a whole message to be dropped. Accept both forms.
- Confirm before you reveal. Match the order to the email or name the customer gives before showing any details.
Read shipping status, never write it
Shipment status comes from the carrier-tracking service and the carriers' public tracking pages. The chatbot only reads. It never pushes tracking numbers into a tracking platform or a carrier system, not even to start tracking a shipment. A chatbot that can write into logistics systems can create shipments, duplicates and alerts that someone has to clean up.
The answer to the customer is the status in plain words: where the parcel is, when it last moved, and what happens next. Internal status codes are rewritten for the customer, never passed through.
Answer with tools, or not at all
A fast answer without a lookup is worse than a slower correct one. Our chat does not answer order questions from memory or from the conversation alone. When the lookup is slow, the customer waits; the system allows up to 45 seconds before treating a turn as failed. The team's rule: better a timeout than a wrong status.
Hand over what needs a person
Some tracking questions turn into requests: the parcel is lost, the address must change, the order should be cancelled, a refund is wanted. Chat replies cannot be taken back, so the chatbot does not agree to any of these. It creates a ticket with the facts it has already collected, gives the customer the ticket number and the email address for follow-up, and the email team handles the rest with a person approving each action.
Write the status the way a customer reads it
Carrier statuses are written for logistics staff: "arrived at hub", "exception", "returned to sender initiated". Passed through as they are, they create a second question for every answer. The chatbot turns each status into what it means for the customer: whether the parcel is moving, whether anything is needed from them, and what the next step is. An "exception" with no movement for several days is different from a delivery attempt that failed because nobody was home, and the reply says which one it is.
Statuses that need a person to look into them, such as a parcel that has stopped moving, become a logistics check ticket so the email team can contact the carrier. Normal transit statuses are answered in chat and the conversation ends there.
Questions the chatbot answers on its own
- Has my order shipped, and with which carrier?
- Where is my parcel now, and when did it last move?
- What does this tracking status mean?
- What is the shipping policy for my country?
Questions it turns into tickets
- My parcel is lost or damaged.
- Please change my address or cancel my order.
- I want a refund, a replacement or compensation.
For how those tickets are sorted and approved, see AI ticket triage and AI refund request handling. The free plan maps your order and shipping systems in two working days.