Automate “where is my order?” tickets

“Where is my order?” is one of ecommerce's most tempting automation targets because the question repeats. It is also easy to answer badly. A dispatched parcel with no carrier scan, a split shipment and a delivered-but-missing package should never receive the same canned response. The useful goal is to give customers the correct next step sooner, not to make a dashboard show fewer tickets.

For Shopify merchants, the order status page is the natural first destination. Shopify says tracking can appear there, in shipping emails and in the Shop app after a tracking number is added. If the fulfilment system does not pass accurate tracking through to the store, a help desk cannot rescue the experience by wrapping stale data in a nicer message.

1. Map the real order states

Write down the statuses customers actually encounter: payment confirmed but not fulfilled; packed but not handed to the carrier; dispatched with a tracking link; carrier movement normal; carrier movement overdue; delivered; and exceptional states such as returned to sender or split delivery. For each, specify what the customer can see, what support can verify, the next expected event and when a person must investigate.

Do not equate “label created” with “parcel collected”. If the tracking link has no carrier scan, say that tracking is available but may not show movement yet. If the fulfilment estimate has passed, give the customer an investigation route rather than repeating the original estimate. Where there are multiple fulfilments, state which items are in which parcel. A tidy taxonomy helps agents, bots and reporting use the same language.

2. Repair the self-service path

Test the order status page on a phone and in a signed-out browser. Can a customer find it from their confirmation email? Does the link point to the right order? Is the carrier link live? Do delivery notifications distinguish the merchant's internal processing from the carrier's actual movement? Shopify explains that a tracking number can be inserted automatically when buying a Shopify shipping label or manually when using another carrier. Third-party fulfilment flows vary, so audit those separately.

Put a plain “Track your order” link in the help centre and contact form. Do not require a customer to install an app to learn where their package is. Explain what to do if there is no tracking yet and when to contact support. A good self-service answer contains an exception path, particularly for high-value or time-sensitive orders.

3. Verify the order before a personalised answer

An email address may match several orders, or a gift recipient may contact support from another address. The automated lookup must identify the correct order and apply the business's identity checks before exposing order details. Avoid asking customers to post full addresses or payment data in an open chat. If the match is ambiguous, request limited additional information and hand the case to an agent.

Set a freshness threshold. If the carrier and store disagree or the last event is old, do not display the newest-looking field as truth without context. Log which system supplied the status and when it was observed. A bot that cannot access a current event should say so. It can still link to the official tracking page and create an investigation ticket.

4. Write one response per meaningful state

For an unfulfilled order, explain the store's processing stage and where the published dispatch expectation can be found. For a dispatched order, link to the official tracking view and identify the carrier event. For a delayed shipment, acknowledge the delay and state the next action the retailer will take. For delivered-but-missing, open a human-led investigation with the details needed by the carrier. Avoid speculative delivery promises.

Draft these as macros or saved replies before turning on automatic sending. Test them with split orders, guest checkout, changed addresses, cancelled items and carrier outages. Review customer-facing placeholders: an internal ticket URL or the wrong order number can cause confusion or expose private data. Suppress duplicate messages when the store already sent a shipping notification.

5. Route exceptions and stop loops

Use rules to tag and route WISMO contacts, but reserve automatic resolution for unambiguous, verified cases. A customer who replies “that is not my order” or “the parcel is not here” must exit the automated path immediately. Give an agent a view of the last status, data timestamp, messages already sent and what the customer disputed. Never make them ask the customer to repeat it all.

Create an owner and deadline for carrier investigations, lost parcels and repeat contacts. A “delivered” scan does not settle the customer's issue. The next action may be checking proof of delivery, neighbour or safe-place information, fulfilment records and the carrier's process. Record the decision and communicate it in plain language.

6. Evaluate after launch

Compare WISMO contacts per hundred orders before and after the change, separated by fulfilment stage and carrier. Track repeat contacts within seven days, escalation rate, time to resolve exceptions and customer feedback. A decrease in contacts is useful only if unresolved orders are not increasing. Sample conversations to check that automated language matches real shipment events.

If most questions arrive before dispatch, improve the store's processing-time message. If most arrive after dispatch with no scans, investigate the fulfilment or carrier feed. If delivered-but-missing dominates, build an exception workflow. The help desk can reveal the pattern, but the fix may sit outside support software.

Sources

• Shopify order tracking guidance
• Shopify order status page guidance
• Shopify guidance on tracking in the Shop app

Platform behaviour comes from Shopify's documentation. The automation thresholds and workflow advice are Support Sorted's editorial judgement.