WISMO AI agent for Shopify that covers phone and website chat

Where-is-my-order (WISMO) is the repeatable intent that fills a Shopify inbox. Shoppers type it in website live chat from the order-status page. They also dial the number on the packing slip when the tracking page looks stale. A chat-only bot answers one of those. The other goes quiet.

Shopify already tries to answer WISMO before chat or phone. After you add a tracking number, customers can follow the shipment on the order status page, in shipping emails, and in the Shop app. That is the first surface. Chat and the store number exist because that surface is missing, stale, or conflicting.

Four common setups after that: a chat-only storefront bot; a phone-only answering service; helpdesk AI plus a bolt-on like Consio or Ringly (Gorgias Voice is still a human channel); or one agent on both surfaces. Ticket automation that closes WISMO inside Gorgias is a fifth job — Yuma AI vs a chat+phone AI agent.

Guzli is one published-plan version of the fourth setup. Keep Gorgias, Zendesk, or Salesforce for macros and leftover tickets. Guzli wrote this page. This is desk research of public product pages, read 19 September 2026 — not a timed WISMO bake-off.

Why shoppers still chat and call

Shopify’s own troubleshooting is the mechanism.

• No tracking number. Some cheap carrier services do not include one. If you fulfill without tracking, the order status page stays On its way until you mark the order delivered.
• Third-party logistics (3PL) or fulfillment-app lag. A fulfilled order with no carrier and no number, or a status of Requested, may still be sitting with a third-party fulfillment app.
• Carrier reuse. During peaks, USPS and Canada Post sometimes reuse tracking numbers, so the page can show an older shipment’s events.
• Wrong or blank carrier. Automatic number-format matching can pick the wrong carrier; the customer then opens a dead link.
• Split shipments. A packing slip is per shipment. One order can have two tracking stories.

The shopper who can type will use the widget. The shopper in a car, on a warehouse dock, or staring at a late carrier scan will call. If only the widget is live, the line is voicemail, a human who has never seen last Tuesday’s delay note, or a second vendor’s script.

Two knowledge bases is how you get two estimated arrival times. The widget learned a supplier slip. The phone agent still says “5–7 business days.”

What a useful WISMO agent actually does

The useful WISMO agent does both surfaces from the same source of truth:

• Live Shopify (or BigCommerce / WooCommerce / PrestaShop) order lookup when that tool is connected — not a canned window when a tracking number exists
• The difference between fulfilled in Shopify, a tracking number, and a carrier scan. Those are three facts. A 3PL portal or the carrier site may have a fourth.
• The exception you already closed in a ticket (“this product ships from the west coast warehouse”)
• A person when the request is a refund, a cancellation you have not approved, a “delivered but I don’t have it,” or a damaged-item claim that needs judgment

Shopify Inbox is not automatically that agent. Inbox is storefront chat. With new customer accounts, an unsigned conversation does not include order details (Managing customer conversations). The useful reply is “sign in or give the order email,” not an invented Tuesday.

Guzli’s Shopify support chatbot page documents order lookup on the storefront and says the connection is not an App Store app. The live /integrations/shopify/ page currently also claims App Store install and automated refunds. Those publisher pages disagree, so this article does not treat refund write-back as a WISMO given.

What “one knowledge base” means for an order

Train once. Do not write a chat FAQ and a separate phone script.

Load help articles, the site, files, and solved tickets plus articles from the desk you keep. Last month’s “carrier lost the first attempt, reshipped, here is the new tracking” should be available when someone types and when someone calls.

Then publish website live chat. Forward the existing support number — always, or only on no-answer, busy, or after hours — if callers exist. Voice starts on Standard on Guzli; Hobby is chat-only. How the call loop works: Can AI answer phone calls?. Customer-service scope (returns, refund status, after hours): Can AI do customer service calls?.

Handoff opens a ticket in Salesforce, Zendesk, or Guzli’s own help desk — with the order and what was already tried.

This is not after-hours coverage. Forwarding only at close is a when. WISMO is a what. You can run WISMO in daytime on both channels and still use the after-hours post for the overnight forward.

Worked path (desk research). Order #1042 shows “fulfilled” in Shopify and no carrier scan. Chat should say there is no scan yet and offer a person — not invent a Tuesday delivery. The same order, dialed from the packing slip, should say the same sentence. If the phone script still says “5–7 business days,” you have two products, not one agent. If Shopify is fulfilled because a 3PL accepted the order but has not scanned it, say that limit out loud.

What to leave off the WISMO agent

Do not let the agent invent a ship date. If Shopify has no scan, say that and offer a person.

Do not grant a wider refund or cancellation on the phone than you grant in chat.

Do not treat “delivered, customer says it is missing” as a tracking FAQ. That is a claims path.

Do not treat a helpdesk AI that closes WISMO tickets as proof the packing-slip number is covered. Yuma-class ticket automation inside Gorgias or Zendesk is a different buy: Yuma AI vs a chat+phone AI agent. Gorgias Voice still needs a human; phone AI next to that desk is usually a bolt-on: Gorgias alternative that answers the phone.

App Store “voice + chat” listings train on catalog and theme. They are a different shape: Shopify App Store AI chat + phone vs one agent.

Guzli limits. Hobby cannot cover the line. No HIPAA (US health-data rules). Guzli does not write refunds or cancellations the way a helpdesk automation layer documents on a ticket. Tickets stay in the desk you keep.

Decide the coverage, then pick the product

1. Write the rules. Shipping cutoffs, “order received vs fulfilled vs in transit vs delivered,” and what you say when a scan is late or a 3PL has the order. If it is not in a help article or a solved ticket, the agent should escalate.
2. Fix the first surface. Add tracking when you fulfill. Do not buy a WISMO agent to paper over a carrier that never scans.
3. Connect live lookup on the widget and the call if you are covering both. Stripe only if subscriptions are in the thread.
4. Pilot the same order in chat and on a call before you trust a weekend of volume — including an unsigned chat visitor and a “fulfilled, no scan” order.
5. Write leftover work back to the desk you keep.

Confirm bolt-on, Yuma, and answering-service prices with each vendor. Guzli (/pricing/, 19 September 2026): Hobby at $49/mo for chat-only. Standard at $149 + 16¢/min (talk 16¢/min, transfer 5¢/min, 3 concurrent). Pro at $499 + 14¢/min (talk 14¢/min, transfer 4¢/min, 8 concurrent).

WISMO is the intent. Website live chat plus inbound phone is the coverage. One knowledge base is the constraint. If any of those three is missing, you still have a hole — even if nights are already handled.

Sources (checked 19 September 2026)

• Order tracking at Shopify
• Managing customer conversations (unsigned Inbox visitors lack order details)
• Gorgias Voice
• Consio on the Shopify App Store; AI phone support by Ringly
• Yuma Support AI
• Guzli: /pricing/; Shopify support chatbot

Shopify support chatbot · AI voice agent · See pricing