How to Automate WISMO Tickets For Shopify Brands

Step-by-step guide to automating Where Is My Order tickets on Shopify. Most brands automate 80-90% of WISMO tickets within the first month, saving 15-25 hours per week.

Stella Garber
Updated 12 min read
Hoop
How to Automate WISMO Tickets For Shopify Brands
Stella Garber

How to Automate WISMO Tickets For Shopify Brands

To automate WISMO (Where Is My Order) tickets on Shopify, connect your helpdesk to Shopify, set up auto-tagging to flag order status questions, and use Hoop to pull tracking data and reply automatically. Most Shopify brands automate 80-90% of WISMO tickets within the first month, saving hours of support labor per week.

WISMO tickets are the low-hanging fruit of support automation. A customer asks where their order is. The answer lives in Shopify. Your system pulls the tracking number, checks the status, and sends it back. No human needed. The ticket closes in under 30 seconds, and the customer gets an instant answer instead of waiting hours for someone to look up the same information.

Here's how to set it up.

Why WISMO Automation Matters

WISMO makes up 30-50% of total support volume for most Shopify brands. If you're handling 200 tickets a day, that's 60-100 tickets asking the same basic question. Your team spends hours every day copying tracking numbers from Shopify and pasting them into replies. It's repetitive, it's boring, and it keeps your team from doing work that actually requires judgment.

Automating WISMO frees up that time. A skincare brand we work with automated their order status tickets and got back 15 hours per week. That's what one agent was spending just looking up tracking information. Now that agent handles complex problems. Returns that don't fit the policy. Upset customers who need someone to actually listen. Product questions that require understanding the customer's use case. The work that matters.

What You Need to Automate WISMO

You need three things: a helpdesk that connects to Shopify, a way to identify WISMO tickets automatically, and a system that can pull order data and send replies. Most Shopify brands use Gorgias or Zendesk as their helpdesk. Both integrate with Shopify. Both support automation. The setup process is similar for each.

Connect Your Helpdesk to Shopify

Your helpdesk needs access to Shopify order data. In Gorgias, this happens automatically when you install the Shopify integration. The system pulls order details, shipping status, and tracking information directly into the ticket view. In Zendesk, you install the Shopify app from the Zendesk Marketplace. Once connected, your agents can see customer order history without leaving Zendesk.

This connection is what makes WISMO automation possible. When a ticket comes in, your system can look up the customer's orders, check the shipping status, and grab the tracking link.

Set Up Auto-Tagging for WISMO Tickets

Auto-tagging identifies WISMO tickets as they arrive. Your helpdesk scans the message for phrases like "where is my order," "track my package," "when will it arrive," or "haven't received." When it spots these patterns, it applies a tag like "shipping" or "WISMO." This tag is what triggers your automation.

In Gorgias, you create rules under Settings → Rules. Set the condition to "Message contains" and add your WISMO phrases. Set the action to "Add tag: WISMO." In Zendesk, you build triggers under Admin → Business Rules → Triggers. Same logic: if the ticket text matches your WISMO keywords, apply the tag.

Start with obvious phrases. Add more as you review tickets and spot variations. The goal is to catch 90% of WISMO questions automatically. The remaining 10% will be edge cases where the customer phrases it unusually or combines it with another question.

Build Your Auto-Reply

Once a ticket is tagged as WISMO, your system needs to reply. You have two options: macros with placeholders or AI-generated replies.

Macros are pre-written templates with dynamic fields. You write the reply once and use placeholders for customer name, order number, tracking link, and estimated delivery date. When the macro fires, it fills in the real data from Shopify. The reply looks like this:

"Hi [Customer Name], your order [Order Number] shipped on [Ship Date] and should arrive by [Estimated Delivery]. Here's your tracking link: [Tracking URL]. Let us know if you have any questions!"

Gorgias and Zendesk both support macros. You set them to trigger automatically when a ticket gets the WISMO tag. The system matches the customer's email to their Shopify order, pulls the data, fills in the template, and sends the reply. No human involved.

AI-generated replies work similarly but write the message from scratch instead of using a template. Tools like Hoop sit on top of Gorgias or Zendesk, read the ticket, pull the order data from Shopify, and draft a reply in your brand's voice. Your team reviews the draft before it goes out, at least at first. Once you see the AI handling WISMO perfectly for a few weeks, you can turn on auto-send for that ticket type.

AI replies sound more natural than macros because they're not templated. They adapt to how the customer asked the question. If someone writes "I'm worried my order didn't ship," the AI might say "No need to worry! Your order shipped yesterday and should arrive by Friday." If someone just asks "where's my order," the reply is more straightforward. Same data, different tone.

Test Before You Automate Fully

Start in review mode. Let the system tag WISMO tickets and draft replies, but have your team approve each one before it goes out. Watch for mistakes. Does the automation pull the wrong order when a customer has multiple orders? Does it handle pre-shipment orders correctly, or does it send a tracking link that doesn't exist yet? Does it sound like your brand?

Fix what's broken. Adjust your auto-tagging rules if it's catching the wrong tickets. Rewrite your macro if the tone feels robotic. Train your AI with examples of how your best agents write. Run this review process for two weeks. By the end, you should see the same replies going out every time with no edits needed.

That's when you turn on auto-send. The system still tags the ticket, pulls the data, and sends the reply. But now it happens without a human in the loop. The ticket closes instantly. The customer gets their answer in under a minute.

Handling Edge Cases

Not every WISMO ticket can be automated. Some situations need a person. Your automation should escalate these cases instead of trying to handle them.

Pre-shipment orders. If the order hasn't shipped yet and the estimated ship date hasn't passed, your automation can still reply. "Your order is being prepared and should ship by [Date]. We'll send you a tracking number as soon as it ships." But if the ship date has passed and the order still hasn't shipped, escalate to a human. Something's wrong, and the customer deserves more than an automated reply.

Multiple orders. If the customer has multiple recent orders, your system needs to identify which one they're asking about. Some helpdesks can parse context clues like order numbers mentioned in the email. If it can't figure it out, escalate to a human instead of guessing.

Angry customers. If the message includes phrases like "this is ridiculous," "still haven't received," or "been two weeks," escalate immediately. These customers are frustrated. An automated reply will make it worse, even if the information is correct. They need someone to acknowledge the frustration and fix the problem.

Set these escalation rules in your helpdesk. In Gorgias, add conditions to your automation rule: "If message contains 'frustrated' OR 'ridiculous,' add tag: escalate and assign to human." In Zendesk, use triggers the same way. The system still tags the ticket as WISMO, but it routes to a person instead of auto-replying.

What Good WISMO Automation Looks Like

A well-automated WISMO flow feels invisible. The customer emails "where's my order?" At 2am, 10am, or 6pm, they get the same instant reply with their tracking link. They click it, see their package is out for delivery, and they're done. The ticket closes. No follow-up needed.

Your team sees the difference immediately. The WISMO queue that used to take an hour to clear every morning is empty. Your agents spend their first hour on returns, product questions, and complex issues instead. Ticket volume doesn't drop (customers still ask where their orders are), but the time spent per ticket does. First response time goes from 3 hours to under 5 minutes. Resolution time drops because there's no back-and-forth. One reply, ticket closed.

You'll also see CSAT stay steady or improve. Customers aren't mad about automation when the automation works. They're mad when they wait three hours for an answer they needed immediately. Instant, accurate replies make them happy, even when those replies come from a bot.

Common Mistakes

Automating too much, too fast. Don't turn on auto-send for all ticket types at once. Start with WISMO. Get that working perfectly. Then add returns. Then product FAQs. Each ticket type has different edge cases and different accuracy thresholds. WISMO is simple because the data is clean and the answer is always the same. Other ticket types aren't.

Forgetting to update order status in Shopify. Your automation is only as good as your Shopify data. If you're not marking orders as fulfilled or updating tracking numbers, your automation will send wrong information. Make sure your fulfillment process keeps Shopify up to date.

No way to reach a human. Always include an escape hatch in your automated reply. "If you have other questions, just reply and we'll connect you with someone on the team." Customers get frustrated when they're stuck talking to a bot with no way out, even if the bot gives the right answer.

Tools That Handle WISMO Automation

Most WISMO automation happens inside your helpdesk (Gorgias or Zendesk) using rules and macros. You don't need a separate tool if you're comfortable building those workflows yourself. But if you want AI-generated replies instead of templates, or if you want a system that handles escalations and edge cases automatically, you'll need an AI layer on top.

Hoop works inside Gorgias and Zendesk. It drafts replies, learns your brand voice, and handles WISMO along with other repetitive ticket types. UpdateMate and Yuma do similar things. Rep AI and Zipchat work as chatbots on your site, answering WISMO questions before they become tickets. Different entry points, same goal: instant answers without human labor.

Pick based on where you want the automation to live. If you'd rather deflect WISMO questions before they hit your inbox, go with a chatbot. If you want to automate inside your existing helpdesk workflow, go with an AI layer like Hoop or a macro-based setup you build yourself.

How This Fits Into Broader Automation

WISMO is the first step, not the last. Once it's working, you'll see other ticket types that follow the same pattern. "Can I change my shipping address?" "How do I return this?" "Is this product vegan?" These all have predictable answers. They all pull from structured data (your Shopify orders, your return policy, your product catalog). They're all candidates for automation.

The same setup you built for WISMO scales to those ticket types. Auto-tagging identifies the question. Your system pulls the relevant data. AI or macros draft the reply. Your team reviews until it's accurate, then you turn on auto-send. Over time, you're automating 60-80% of your total ticket volume. Your team shrinks relative to your sales, but the work they do gets more valuable.

WISMO is where you prove the concept. Get it working, show your team the time savings, and build from there. For more on scaling automation beyond WISMO, see How to Automate Shopify Customer Service.

FAQ

How long does it take to set up WISMO automation?

Most brands have basic WISMO automation running within a week. It takes another 2-3 weeks of testing and tuning to get it accurate enough to trust with auto-send. Budget a month from start to full automation.

What if my brand's voice is really specific? Will automation sound generic?

Macros will sound templated unless you spend time writing them to match your voice. AI-generated replies adapt better, but you need to train the AI with examples of how your team actually writes. Feed it 20-30 real WISMO replies from your best agents and it'll learn the tone.

Can this work if we have custom shipping workflows or use third-party fulfillment?

Yes, as long as the shipping data ends up in Shopify. If you're using ShipStation, ShipBob, or another 3PL, make sure they're syncing tracking numbers back to Shopify. Your automation pulls from Shopify, so the data needs to live there.

Will customers know they're talking to a bot?

Only if you tell them. Most brands don't label automated replies as bot-generated. The reply includes the tracking link and reads like a normal support message. Customers care about getting the answer, not who sent it. If you want to be transparent, you can add a signature like "Sent automatically via Hoop" at the bottom.

What happens if the tracking link is wrong or the package is lost?

Your automation should only reply when the order status is clear (label created, in transit, out for delivery, delivered). If the status is "exception" or "returned to sender," escalate to a human. Don't auto-reply to situations that need investigation.


Hoop works inside Gorgias and Zendesk to automate WISMO and other repetitive tickets. It learns your brand voice and handles replies so your team can focus on conversations that actually need a human. Learn more

Reply like an expert. Every time.

Zero setup. Zero training. Just connect and let Hoop learn.