The main recurring support issue identified is “Where is my order?”, with several participants saying it dominates Shopify merchant inboxes and can represent a large share of weekly tickets. Suggested first-line fixes include proactive shipping emails, tracking links, self-service tracking pages, Shopify notifications, and helpdesks such as Gorgias, Zendesk, or Tidio using saved macros.
The discussion shifted from reducing ticket volume to handling the remaining exceptions more efficiently. Common unresolved cases include “delivered but not received,” shipments stuck in transit, address changes, refund-related questions, and policy-specific requests that require order data or human judgment.
A recurring framework emerged: deflect simple repeat questions with tracking and FAQs, use order-aware draft replies for cases needing customer/order context, and keep refunds or policy exceptions fully human-approved. Recent comments emphasize that the next opportunity is reducing agent handling time by surfacing order, carrier, and policy context faster, rather than pursuing full automation. The discussion remains open, with questions about how remaining tickets split between automatable drafts and truly manual decisions.
Running support for a store, the same handful of questions come in on repeat. Where’s my order, when will it ship, what’s your return policy, can I change my address. You end up typing the same few answers all day long.
Curious what that looks like for everyone else:
1. What’s the one question you answer the most?
2. Roughly how many of those land in your inbox a week?
3. Have you found a good way to take it off your plate, or are you still doing it by hand?
I’ll share what’s actually worked for the brands I help in the replies, but I’m more interested in hearing what’s eating your time. In my experience the repetitive stuff is the easiest to fix once you know which question is the worst offender, so let’s see what the worst offenders are.
From what I’ve seen, the #1 question for most merchants is definitely “Where’s my order?”
Honestly, I’d say around 70% of support tickets are related to order tracking in some way. Customers just want to know where their package is.
The best way I’ve seen merchants reduce those tickets is by being proactive with tracking updates.
You can do it manually by sending email or SMS updates whenever there are major carrier status changes, or use a tracking app. One I can recommend is PluginHive Shipment Tracking & Notify. It pulls tracking updates directly from carrier APIs and automatically sends tracking notifications to customers by email, so they stay informed.
In many cases, just keeping customers updated on their shipment status can eliminate a huge chunk of those repetitive “Where’s my order?” tickets, regardless of how you choose to do it.
Good call abhishek, proactive tracking updates are probably the single biggest lever on the plain “where is it” tickets. Agreed that keeping people informed before they have to ask kills a big chunk of the volume.
What I have noticed is that the variations are what still leak through even after tracking notifications are set up. The “it says delivered but I never got it”, the “can I change my address before it ships”, and the return-policy and sizing questions. Those need an answer pulled from the actual order and your own policies, not just a carrier status.
The setup that has worked best for the brands I help is to let automation handle the answers it can read straight from your order data and policies and reply instantly, but keep anything that changes an order or touches a refund as a draft a human approves before it goes out. You get the speed on the repetitive stuff without a bot promising something it should not.
Still Curious from the merchants here: after the basic tracking updates, which question is still the most annoying one left in your inbox?
Hello, @Syed_Noor
Hope you are doing great!
For us, it’s definitely “Where is my order?” by a huge margin. Automated tracking emails and a self service order tracking page helped reduce those tickets significantly, but they still make up most of our support volume.
That tracks. Even with tracking emails and a self-serve page, “where’s my order” usually stays the biggest bucket because it is really a few different questions wearing the same costume. The ones that survive the automation are the cases a carrier status cannot answer on its own: “it says delivered but I never got it,” “it has been stuck in transit for days,” and “I changed my mind, can I still stop it.” None of those get resolved by a tracking link, so they fall back on a person.
What tends to move that leftover pile is answering from the order itself, not just the carrier. The reply pulls the real status, the expected window, and your own policy and goes out instantly for the clean cases, while the genuine exceptions like lost-in-transit or anything refund-related get handed to a person as a ready-to-send draft instead of auto-replying. Proactive updates cut the front end, order-aware answers cut the tail.
Curious for you: of the “where’s my order” ones still landing after your tracking emails, roughly what share are the “delivered but not received” or “stuck in transit” type versus the plain “just tell me where it is”? That split is usually the tell for what is actually worth automating next.
Hi @Syed_Noor .
Where is my order? It is the top repeat question for almost every store.
Automate it with the tracking page and shipping confirmation emails with a tracking link.
For everything else, Gorgias and Tidio handle repeat questions well and cut inbox volume by half.
Agreed on the front end. A tracking page plus a shipping confirmation with a live link is the first thing every store should turn on, and helpdesks like Gorgias and Tidio are genuinely good at cutting the generic FAQ volume.
The distinction I would add is between deflecting a question and answering it. A chatbot or macro is great when the answer is the same for everyone: your return window, your policy, here is your tracking link. Where it still falls back on a person is the order-specific tail: “it says delivered but I never got it,” “stuck in transit for a week,” “can I change the address before it ships,” anything refund related. Those need the actual order data and a judgment call, so the win there is less about volume and more about handing the agent a ready-to-send draft built from the order and your policy, with a human approving the ones that touch money or change an order.
So I think of it in two layers: deflect the repeatable stuff with tracking and a helpdesk, then answer the order-aware tail from your own data with a human gate on the exceptions. Curious what you have seen, after Gorgias or Tidio takes the easy half, what is the biggest chunk that still lands on a person?
Hello there @Syed_Noor
Most of the shops I work with have “where is my order” at the number one, typically followed by shipping timelines and changes of address. That’s 30 to 100+ tickets a week, easily, depending on volume.
The single biggest time saver has been implementing automated order tracking through Shopify notifications + a helpdesk like Gorgias or Zendesk with saved macros. Combine that with a simple tracking page and proactive shipping emails and you really reduce repeat tickets. After that it is mostly exceptions that are handled manually, rather than the whole flow.
Appreciate that, Roan — matches what I see too: tracking + macros clears the easy 70-80%, and then it’s the “exceptions handled manually” bucket that quietly eats the day.
What I find interesting is that bucket isn’t all one thing. Some of it is still answerable from data — you’re just not letting a macro near it because the stakes are higher. “Delivered but I never got it” or “stuck in transit for a week” is really a carrier-status + order lookup; the agent could draft the reply and a human just approves before it sends. The genuinely manual ones are the judgment calls: refunds, an address change after it’s packed, a goodwill exception. Those should stay with a person.
So I’ve started thinking of it as three buckets, not two: deflect (macros + tracking page), draft-then-approve (order-aware, but a human signs off), and fully human (money or policy judgment). Most stores lump the last two together and end up hand-typing answers that could’ve been a one-click approve.
Curious from your side — for the brands you help, once tracking + Gorgias take the easy half, roughly how does the rest split between “could be a draft” and “genuinely needs a person”? That ratio is the thing I’m trying to pin down.
Agree with this, I think the next frontier after tracking + macros is not full automation, but making exceptions faster. A lot of manual tickets are really just missing context, order data, carrier status, and policy rules. I think the real win is reducing handling time, not just ticket count.
@Syed_Noor Those questions are exactly why we built the CL Apps suite. Digital Unboxing & COA Kit gives the customer a considered confirmation email along with their product details, care information, maker’s note and return terms, and even an upsell item, so several answers are already in one clear place. If the order is bespoke or made to order, In the Making continues in the same branded customer home with production stages, expected dates and carrier details. We’re not trying to replace every support conversation; the aim is to stop customers having to ask for information the store already knows, while keeping the experience personal and cohesive.
The handling-time point is the one worth digging into more. A lot of the “genuinely needs a person” tickets aren’t slow because of the decision, they’re slow because someone has to go find the order, check the carrier status, and pull up the policy before they can even start typing. Cut that lookup time and even the fully-manual bucket gets faster, without touching what stays human.