E-commerce
June 28, 2026
"Where is my order?" The customer opens the chat at 11 p.m. No one answers. They open a ticket. The next morning, the agent copies and pastes the Colissimo link. Three minutes for a question that could be resolved in ten seconds.
Claro estimates that WISMO tickets represent 30 to 50% of e-commerce support volume, with the same pattern every time: look up order, paste status, send (Claro, WISMO Shopify 2026). Shopify points out that 69% of consumers expect real-time tracking post-purchase (Shopify, WISMO e-commerce).
This guide #184 covers the AI order tracking chatbot: helpful tracking responses without a support ticket. Distinct from post-purchase support (#9) and tracking journey clarity (#181): here, WISMO conversational automation connected to Shopify and the carrier.
Summary
Why automate order tracking in chat first?
The order tracking chatbot offers the fastest ROI in AI support: clear intent, structured data, minimal financial decision-making.
Measurable WISMO volume
ShippyPro places WISMO queries between 40% and 60% of tickets depending on the vertical (ShippyPro, WISMO 2026). Zipchat observes 35% to 50% fewer tickets in the first month with a connected tracking bot (Zipchat, automate WISMO).
Agent vs bot cost
A manual WISMO ticket: 3 to 5 min lookup + response. 100 orders/day = 20 to 35 hours/week of pure status search. Connected bot: response within 30 seconds, 24/7.
Instant customer expectation
Fin.ai cites 96% of buyers who actively track their package until delivery. Chat is the channel where they look for an immediate answer, not a ticket replied to within 24 hours.
How does this guide differ from #9 and #181?
Three neighboring contents, three complementary levers.
Post-purchase support (#9)
Post-purchase automation (#9) covers returns, invoices, refunds. The #184 zooms in on intent tracking only.
Clarity in the tracking journey (#181)
Guide #181: branded page, proactive notifications. The #184 responds when the customer still writes to the chat.
General AI ticket reduction
Reduce AI tickets lists the use cases. Here: complete WISMO playbook with status branches and handoff.
Promise #184
Shopify lookup + carrier, plain language response, tracking page link, escalation if exception. Zero tickets if resolved in chat.
Which WISMO intents should the bot recognize?
Map out the chatbot order tracking intents before NLP configuration.
Main intents (8)
wismo_status: where is my order / package
wismo_not_shipped: not shipped yet, is this normal?
wismo_tracking_link: resend tracking number
wismo_eta: estimated delivery date
wismo_delay: delay vs promise
wismo_stuck: no scan for X days
wismo_delivered_not_received: delivered but missing
wismo_wrong_address: change address (handoff to #183)
Natural phrasing
Train on variations: my package, my order #4521, gift for Saturday, still received nothing. Heeya recommends 15 to 20 phrasings per intent (Heeya, tracking bot 2026).
Which Shopify and carrier data should be connected?
A useful WISMO bot requires real-time order lookup, not a generic response.
Shopify Layer (read-only)
Order status: unfulfilled, partial, fulfilled
Fulfillment events: shipping date, tracking number, carrier
Line items + shipping address
Customer email / phone match
Carrier Layer
AfterShip, ShippyPro, Malomo or Colissimo/Chronopost API: scan status, ETA, delay exceptions. Heeya: 80% automation rate with carrier API vs 40% with Shopify alone.
Content Layer
Delivery time policy, shipping hub, section 6 status mapping. Aligned dynamic ETA and tracking page #181.
Aggregator Apps
AfterShip and ShippyPro centralize 1000+ carriers. Malomo and Wonderment add branded pages that the bot can link. Test consistency between bot ETA vs Klaviyo email on 5 orders before going live.
How to authenticate the customer without friction or security flaws?
The WISMO chatbot authentication protects order data without blocking 80% of cases.
Methods by channel
Shopify logged-in session: automatic lookup via customer account
Email + order #: standard anonymous widget
Email only: latest order within 48 hours if only one matches
Email OTP: if order > €150 or third-party address
Security rules
Never display full address without verification. Mask last digits of credit card. Clarification: read-only API permissions, no write fulfillment from bot.
Authentication failure
"I cannot find an order for this email. Please confirm the checkout email or order #." See customer authentication.
Which responses should be linked by fulfillment status?
The WISMO bot workflow follows five status branches, not a single response.
Branch 1: unshipped
"Order #[X] confirmed on [date]. Warehouse preparation in progress. Estimated shipping [date]. We will notify you by email as soon as it is sent." + policy delay if > checkout promise.
Branch 2: shipped, in transit
"Shipped [date] via [carrier] [tracking]. Estimated delivery [ETA]. Tracking: [branded link]. Next scan expected within 24 hours."
Branch 3: out for delivery
"Out for delivery today. Presence recommended or leave with neighbor. Tracking: [link]."
Branch 4: delivered
"Delivered on [date] [time] according to carrier. Check mailbox, building manager, parcel pickup point. If not there, reply NOT RECEIVED."
Branch 5: exception / delay
"Delay reported by carrier. New date [ETA]. No action required. We are monitoring." Aligned with support by status.
How to handle delays, scan blocks, and delivered but not received parcels?
The tracking chatbot exceptions separate resolved bot from mandatory handoff.
Delay vs checkout promise
If ETA > promised date + 24 h: empathy message + new date + contact option if urgent gift. Tag wismo_delay. No auto compensation without a defined threshold.
Scan silence 48 h+
"Parcel in transit, last scan [date]. No carrier alert. Next check within 24 h. If nothing by [date], we launch an investigation." If 72 h: handoff ops + carrier ticket opening.
Delivered not received (DNR)
Bot: neighbor, mailbox, building manager, 24 h
Client replies NOT RECEIVED: handoff with tracking + address
Agent: carrier investigation within 48 h, reshipment or refund according to policy
Macro MANO #178 on handoff.
Alleged damage upon receipt
Intent outside pure WISMO: handoff to breakage workflow fragile products (#182) with photo collection, no bot refund promise.
When is human handoff mandatory?
Set WISMO escalation thresholds before go-live, not case-by-case.
Immediate handoff
Lost package confirmed by carrier
Order > € threshold + DNA (Did Not Arrived) or alleged damage
Customer's 3rd message with same intent within 48h
Refund / compensation request
Tracking data missing in database
Gorgias handoff brief
Transfer: order #, bot status, tracking, verbatims, photos if DNA. See bot-human handoff.
Shadow mode
Claro recommends 1 week of shadow mode: bot replies in draft, agent validates. Test branches before customer activation.
How to set up bot instructions and your brand tone?
The WISMO bot instructions set the tone, limits, and response format.
System prompt rules
Always: order #, plain language status, ETA if available, tracking link
Never: invent data/dates, promise refunds, modify addresses
If unknown: honest delay + 4 business hours human SLA
Target response example
"Hello Marie, order #8842 shipped Tuesday via Colissimo 3S1234567890. On its way to Lyon, delivery estimated Thursday before 6 PM. Tracking: [link]. Question about the content? I'm here to help."
Multichannel consistency
Same wording for Klaviyo email, Wonderment page, and bot. See bot instructions and #181.
Which KPIs prove that the bot is preventing tickets?
Measure chatbot tracking performance by chat resolution, not by message volume.
Leading KPIs
WISMO bot resolution rate: target 70-85% with carrier API
WISMO tickets / total support: 35-50% decrease in month 1
48-hour recontact on WISMO intent: < 12%
Bot response time: < 30 s
Lagging KPIs
Agent hours saved/week. Post-bot interaction CSAT. FCR intent tracking. Cost per ticket avoided (~$5 Claimlane). See chatbot KPIs and FCR.
25-min weekly review
10 bot WISMO conversations: 3 perfect, 3 handoffs, 2 recontacts, 2 auth failures. 1 fix for instruction or branch.
Month 1 Benchmark
Claro: brands that automate WISMO first reach 40-50% overall AI resolution before other intents. Compare your WISMO ticket baseline week -4 vs week +4 post-deployment.
How does Qstomy automate order tracking?
Qstomy connects Shopify, carrier, and your policies to answer WISMO without tickets.
Tracking features
Multi-order lookup: email, #, customer session
5 status branches: automated section 6
ETA carrier sync: AfterShip, ShippyPro
Branded tracking page link in every response
DNR / 72h delay handoff: complete agent brief
Quantified DTC scenario
Nutrition brand, 6,500 orders/month, WISMO 44% of tickets (380/month), generic bot without lookup, 4 min/ticket. Deployment of Qstomy WISMO + email auth + 5 status branches + Malomo sync. After 8 weeks: bot resolution 79%, WISMO tickets -41%, 48h recontact -36%, response time 22 s, 12 hours/week of agent time recovered.
Explore AI support, Shopify, request a demo.
Which operational playbooks should be launched this week?
Playbook 1: intent mapping (1 hr)
List 8 intents in section 3. 15 utterances each. Prioritize wismo_status and wismo_delay.
Playbook 2: data connection (2 hrs)
Shopify read-only API + carrier. Test 10 real orders of all statuses. Verify ETA vs tracking page.
Playbook 3: 5-status branches (2 hrs)
Draft templates in section 6. Variables #, date, carrier, link. Validate brand voice.
Playbook 4: handoff rules (45 min)
Document thresholds in section 8. Gorgias assignment flow to ops.
Playbook 5: shadow mode 7 days
Bot responds, agent compares. Correct before activating PDP widget and order page.
Useful links
The best WISMO ticket is the one that doesn't exist: the customer asks their question in the chat and leaves with a complete answer in less than a minute.
Enzo
June 28, 2026
