E-commerce
June 26, 2026
A customer who has just ordered does not ask the same question as a customer whose package has been stuck for four days. Yet, many stores still respond with the same macro to all statuses.
The tension is there: your data already exists in Shopify, the carrier, the return portal, or the helpdesk, but it does not always make its way into the customer response.
This article does not repeat WISMO guides or transactional messages. It shows how to personalize support according to the actual order context: paid, in preparation, shipped, delivered, returning, refunded, or in exception.
Summary
Why does the order status change the whole response?
The order status indicates what the customer can reasonably expect and what your team can still do. Before shipping, you can sometimes modify an address. After shipping, you must work with the carrier.
Shopify explains that the order status page updates in real-time depending on progress: confirmed, on its way, out for delivery, delivered, or attempted (Shopify, order status page).
Contextual support therefore addresses the actual situation, not a vague category like "order tracking". This is what reduces follow-ups and restores trust.
trust.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
Which statuses should be standardized first?
Confirmed: order received, payment validated, not yet prepared
In preparation: warehouse or fulfillment team is processing the order
Partially shipped: multiple packages or products sent separately
Shipped: tracking created, package handed over or awaiting first scan
In transit: carrier has taken over, latest scan available
Out for delivery: delivery scheduled for today or attempt in progress
Delivered: package marked as delivered, return or product support possible
Return or refund: request initiated, return package received or refund processed
Map these statuses into simple customer vocabulary. "Fulfilled" or "arrival scan" speak to teams, not necessarily to the buyer. Translate to "your package is on its way" or "it has arrived in your region."
How to map status, question, and action?
Create a matrix with four columns: real status, likely question, expected response, available action.
List Shopify, carrier, and return portal statuses.
Associate the most frequent question with each status.
Write the ideal response with delay, link, and next step.
Define the possible action: modify, track, return, refund, or escalate.
Document the channel: proactive email, chat, portal, human agent.
Example: status "shipped without scan for 72 hours". Likely question: "why is it not moving?". Response: last known event, investigation threshold, follow-up date. Action: open a carrier investigation if the threshold is reached.
Which scripts should be sent before shipping?
Order confirmed
“Hello [First Name], your order #[number] is confirmed. It is now being prepared. The usual time before shipping is [timeframe]. You will automatically receive a tracking link as soon as the package is handed over to the carrier.”
In preparation
“Your order is being prepared in our warehouse. At this stage, tracking is not yet available. Shipping expected [date or window]. If you need to correct an address, please reply quickly to this message before final validation.”
Pre-order or backorder
“Your order contains a pre-ordered product: [product]. Shipping is scheduled around [date]. The other items [will ship together / can ship separately] depending on your option.”
The promise must be precise without overpromising. If you do not yet know the exact date, provide the rule that triggers the next update.
Which scripts to send after shipping?
Tracking created
“Your order #[numéro] has been shipped with [transporteur]. The tracking link is here: [lien]. The first scan can take up to [délai] after creation of the label.”
In transit
“I checked the tracking: the last event indicates [statut traduit] on [date]. Delivery is estimated for [date]. If no new scan appears by [date], we will launch an investigation.”
Out for delivery today
“Your package is scheduled for delivery today. Keep an eye on the tracking link, as the carrier may specify the delivery window. In case of absence, here are the options: [lien ou consigne].”
See also reducing Shopify WISMO questions to build the most recurring tracking answers.
How to manage delivery, returns, and refunds?
Parcel delivered
"The carrier indicates a delivery on [date] at [location if available]. If you cannot find the parcel, please first check with [neighbor, collection point, caretaker]. If nothing appears within 24 hours, reply here and we will open an inquiry."
Return initiated
"Your return has been successfully initiated for order #[number]. You can follow the steps here: [portal link]. The refund will be processed after the returned parcel has been received and inspected."
Refund processed
"The refund of [amount] was processed on [date] via your original payment method. Depending on the bank, it may take [delay] to appear."
Shopify allows you to manage returns and refunds directly from the order, which makes the response clearer if your helpdesk correctly displays the history.
How to connect helpdesk, Shopify, and carrier?
Personalization depends on the freshness of the data. An agent should not have to open Shopify, the OMS, the carrier, and the return portal for every ticket.
Shopify: order status, financial status, fulfillment status, line items
Carrier: last scan, tracking URL, ETA, incident, or attempt
Helpdesk: conversation history, macros, tags, priorities
Returns: request, label, receipt, refund
Customer: first order, VIP, LTV, country, preferred channel
Gorgias and Zendesk display Shopify data in the ticket, complete with history, fulfillment, tracking, and sometimes refund or cancellation actions (Gorgias, Shopify variables, Zendesk, Shopify integration).
The primary goal is not AI. It is the elimination of manual copy-pasting between tools.
How to automate without sending a cold response?
A useful bot must retrieve the order before responding. Otherwise, it merely redirects the customer to a page they have often already visited.
Identify the customer by account, email, or order number.
Read the Shopify status and fulfillment information.
Read the carrier tracking if available.
Translate the status into customer-friendly language.
Offer the available action or escalate if there is an exception.
eesel AI emphasizes the need to connect the agent to Shopify with access to orders and fulfillments to retrieve status, tracking, carrier, and links in real time (eesel AI, order status bots 2026).
Simple rule: if the bot cannot display the relevant order number in its response, it should not claim to personalize the tracking.
Which exceptions should be excluded from the standard flow?
No scan: label created but no movement after the expected threshold
Incorrect address: correction possible only before certain statuses
Split shipment: multiple parcels, different statuses, line by line
Pre-order: normal wait but causes anxiety if poorly explained
Delivered not received: carrier investigation, proof, response time
VIP Customer: faster escalation in case of delay or high cart value
Chargeback or bad review threat: human intervention mandatory with full context
These exceptions must have written thresholds. Example: if no scan after 72 business hours, investigation message. If parcel delivered not received, ask for local verification then open a case. If split shipment, always display each parcel separately.
See e-commerce customer service scripts to turn these rules into usable macros.
How to prevent tickets with proactive messages?
The best WISMO ticket is the one that never happens because the customer received the right information before they started worrying.
Confirmation: order summary, preparation time, next step
Shipping: branded tracking, carrier, first estimation
Delay: alert before the customer contacts you, new realistic window
Out for delivery: D-day reminder, options in case of absence
Delivered: confirmation, return link, product help
Return: receipt status, refund time, next step
Alhena believes that proactive updates at key moments can reduce a significant share of WISMOs, as they provide answers before anxiety builds up (Alhena, post-purchase AI 2026).
Do not notify for every single micro-scan. Select the moments that truly change the customer's waiting experience.
Which KPIs should be monitored to manage contextual support?
Volume by status: how many tickets arrive at each stage
WISMO rate: share of "where is my order" requests
First contact resolution: resolution without follow-up on the same subject
Repeat contact 48 hrs: same order, same question, sign of an incomplete response
Resolution time: by status and by exception
CSAT: segmented by simple status vs. exception status
Bot escalation rate: where automation fails or must remain cautious
Use the dashboard to talk with operations. If the "shipped without scan" status skyrockets, support should not just respond better: it must alert fulfillment or the carrier.
See E-commerce chatbot KPIs and post-purchase support automation.
How does Qstomy personalize support by order status?
Qstomy can connect the conversation to the Shopify context: order, fulfillment status, tracking, return and customer history. The customer gets an answer tailored to their file, not a generic FAQ.
DTC Scenario
A brand processes 3,000 orders per month and receives 650 support tickets, 42% of which are related to tracking, returns and refunds. By connecting Qstomy to Shopify and covering eight priority statuses, the pilot objective is to resolve 55% of status inquiries without an agent and reduce 48-hour follow-ups by 25%.
Example: a customer asks "where is my order?". Qstomy identifies order #5912, sees that it is in transit with the last scan yesterday, translates the status, provides the ETA, offers the tracking link, and only escalates if the scan exceeds the exception threshold.
Discover AI customer support, Shopify integration and request a demo.
.
Enzo
June 26, 2026
