If you run a Shopify store and you read your own support inbox, you already know the punchline. Most of it is the same question, over and over: where's my order?
It is the most common question most stores get. It is also the most tempting one to hand to a bot, because the answer is not a judgment call. It is already sitting in the order and the tracking link. Nobody has to decide anything. The customer just wants the facts, fast.
So, this should be the easiest thing to automate in your whole inbox. And it is, right up until the bot starts making things up.
Why this is the right thing to automate first
Every other kind of support question carries some judgment. Refunds involve money. Returns involve policy. Complaints involve tone. "Where's my order" involves none of that. The right answer is just four facts:
- What did they buy, and when?
- Has it shipped, and with which courier?
- What does the latest tracking update say?
- When is it actually expected to arrive?
All four already live in your order and the courier's tracking. That is what makes this the highest-value thing to automate: huge volume, no judgment, and an answer you can check. Clear these questions and you have often cleared most of your inbox in one move.
Where it goes wrong: a bot that guesses
Here is how stores get burned. They switch on an AI tool, it starts answering the "where's my order" questions, and for a while it looks great. Then a customer asks, and the bot replies with something like "It should arrive soon!" except it got that from nowhere. The parcel is stuck at a depot. The last update was four days ago. There is no "soon."
That one reply does more harm than the fifty it handled. The customer now has a promise from your brand in writing, and it is wrong. Their next message is not a question, it is a complaint. You did not save a ticket. You created a worse one with your name on it.
The reason is simple. The bot answered without checking the real record. It wrote a sentence that sounded right instead of reading what was actually there. For small talk that is harmless. For a delivery promise it is the whole problem.
How to do it right: answer only what the data shows
The fix is not less automation. It is automation that is only allowed to say what the real data backs up. Three rules keep it safe:
1. Every reply comes from the real order and tracking. The bot does not guess a delivery date. It reads the order and the latest courier update and reports exactly that: shipped or not, which courier, the last update, and the date the courier itself gave. If there is a tracking link, it shares it.
2. If the data is not there, it says so and passes it to a person. No update in days? The honest reply is "your order is on its way and the courier has not posted a new update recently," plus an easy way to reach a human, not a made-up arrival date. The urge to never leave a blank is exactly what gets bots in trouble. A good setup treats "I don't have that yet" as a perfectly fine answer.
3. It keeps answering and acting separate. Telling a customer their order shipped Tuesday is answering, and that is safe to automate all day. Sending a replacement or a refund is acting, and that moves money. Those are two different things and should be treated differently (more on that next).
Do those three and automating this stops being risky. The customer gets an instant, correct answer. You get your inbox back. And nobody gets a promise your shipping cannot keep.
The one version that still needs a person
There is one type you should never fully automate: the tracking says delivered, but the customer says it never showed up.
This looks like the same question, but it is not. The data and the customer disagree, and sorting it out means choosing to resend, refund, file a claim with the courier, or push back. All of those cost money or carry risk. That is acting, not answering.
The right setup here is simple: the bot does the legwork and a person makes the call. It pulls the order, the tracking history, the delivery scan, and the customer's message, and writes a suggested reply. Then it stops and waits for you to approve. You get everything gathered in one place, fast, without ever letting the bot spend your money. The same goes for any "where's my order" that turns into "I want a refund because it's late." Answer the status automatically. Hold the money for a person.
What good looks like
Put together, it works like this:
- Normal status questions: answered instantly from the real order and tracking, no invented dates, tracking link included.
- Missing or old data: handled honestly, with a clear path to a human instead of a guess.
- Delivered but not received, or anything that moves money: prepared by the bot, decided by you.
That is not a chatbot. It is an assistant that knows the difference between reading your own data back to a customer and making a decision you never approved. Your ticket count drops because the questions were actually answered, not because the customer gave up trying to reach you. And you never wake up to a refund the bot promised or a delivery date it invented.
This is the easiest place to get it right, because the line between answering and acting is so clear. Get it right here, and the same habit carries into every harder part of your inbox.
