How to Reduce WISMO Tickets with Gorgias
WISMO (where is my order) tickets make up roughly 30-50% of an ecommerce support queue depending on season. You cut them with three Gorgias changes: a proactive tracking notification triggered from Shopify fulfillment, an AI agent scoped to order status, and a self-serve order lookup on your site. Each removes a slice; together they typically cut WISMO volume by half.
The fourth thing everybody tries — a better FAQ page — barely moves the number. People do not read the FAQ when they are worried about a package.
Why do WISMO tickets happen at all?
Three root causes, and only one is a support problem.
| Cause | Share of volume | Real fix |
|---|---|---|
| No tracking info sent | About 40% | Trigger notification on fulfillment |
| Tracking shows no movement | About 35% | Carrier exception handling |
| Customer cannot find the link | About 25% | Self-serve lookup page |
Notice that the biggest cause is silence. The customer has not heard anything since the order confirmation, so they ask. That is preventable with a rule, not a chatbot.
How do you set up the proactive notification?
In Shopify, use an order fulfillment webhook or a flow that fires when an order is marked fulfilled. Push the tracking number and a branded tracking link into Gorgias’s automation, which sends an email or SMS automatically.
Details that decide whether this works:
- Send on fulfillment, not on shipment. Carriers routinely take 12-36 hours to show the first scan. Sending tracking at fulfillment sets expectations before silence begins.
- Include an expected delivery window, not a single date. A single date that slips generates a new ticket. A window absorbs normal carrier variance.
- Add a second message on carrier exception. If tracking has not updated in 72 hours, send a proactive “we’re looking into it” note. This single message removes a large share of “is my order lost” tickets.
How do you scope the AI agent for order status?
The AI agent needs these three data points to answer well: order lookup by email, live tracking status, and your stated handling time for delays.
Configure it to answer only four intent types:
- Where is my order
- Has it shipped
- Can I change the address (before fulfillment only)
- What is your return window for this item
Everything else escalates. This narrow scope is what makes the bot reliable, and it covers most of the WISMO queue anyway.
One rule worth adding: never let the bot estimate a delivery date not present in the tracking data. Customers compare the bot’s promise to the carrier’s page, and any mismatch becomes a complaint.
What does the self-serve lookup look like?
A form on your site: email address plus order number, returns the current status. Most helpdesk platforms offer a widget for this; Gorgias has a customer portal option on higher plans.
Placement matters more than design. Put the lookup link in the order confirmation email and in the header of your help center, not buried at the bottom. Every additional click to find it adds tickets.
Expect this to handle 15-25% of WISMO volume on its own, mostly from customers who would rather self-serve than wait for a reply.
What results are realistic?
Stores that implement all three report WISMO volume dropping 40-60% within two months. Peak season is the test — November and December volumes are 2-3x baseline, and that is when a working setup pays for itself.
Two caveats. First, some of that reduction is shift: customers who would have emailed now click the tracking link, and you never see the ticket at all. It is real savings but it will not show in helpdesk reports. Second, the AI-resolved portion still costs money under Gorgias’s automation billing, so model the net cost, not just ticket reduction.
What still goes wrong
Multi-package orders. A three-item order shipping in two boxes confuses customers and bots alike. Show per-package status, or at minimum state that the order ships in multiple parts.
Address changes after fulfillment. No bot can fix this. Route it to a human immediately with a template that explains carrier intercept.
Carrier tracking API outages. On the rare days a carrier API is down, the bot should say “tracking is temporarily unavailable” rather than inventing a status. Test this by faking an API failure in staging.
Key Takeaways
- WISMO is 30-50% of ecommerce support volume, and silence after fulfillment is the largest single cause.
- Send tracking at fulfillment with a delivery window, then follow up proactively at 72 hours without a scan.
- Scope the Gorgias AI agent to four order-status intents; escalate everything else.
- A self-serve lookup page handles another 15-25% of volume.
- Expect 40-60% WISMO reduction in two months; peak season is the real test.
See the Gorgias profile at iAIFeed for platform details and pricing structure.
