How does InboxPilot automate WISMO replies?

Connect the inbox where the questions land, give it your order information and shipping policies, and it drafts a specific reply to each status question as it arrives. Drafts wait for approval by default. Once you trust the pattern on routine lookups you can let those send automatically and keep approval for anything sensitive.

What stops it from telling a customer something wrong?

Two things. Drafts are grounded in the order information and policies you connect rather than generated from guesswork, so a draft commits only to what your policy allows. And nothing sends without approval until you turn that on yourself, per category, which means you see how it handles delays and lost packages before it ever handles one alone.

Is this the same as Shopify or carrier notification emails?

No, and they work together. Notifications are outbound: you tell the customer what happened. This is the inbound side: the customers who write back anyway, very often by replying directly to one of those notifications. For the Shopify-specific setup, see our Shopify order status guide.

What happens to angry customers and genuinely lost packages?

They reach a person, and sooner than they do today. Routine lookups stop burying the urgent threads, and anything sensitive is drafted with the context summarized and held for human review rather than sent.

Do I need to leave my helpdesk?

No. InboxPilot works inside Gmail and Outlook, so teams running a helpdesk for chat or social keep it and automate the email channel where the volume actually lands.

WISMO Emails in 2026: Automate Order Replies

Why WISMO & order status emails deserve automation

WISMO stands for where is my order, and it covers every inbound message asking what happened to a purchase: has it shipped, why has tracking not moved, will it arrive before the weekend. It is the highest-volume and lowest-value mail an ecommerce or logistics inbox receives, and the standard advice for 2026 is to prevent it. That advice is right. Branded tracking pages, proactive shipping updates, honest delivery windows at checkout, and a self-service portal all cut the volume, and you should do them before you automate anything. What none of them do is answer the mail that still arrives, because a customer who is already worried will email you regardless of how good your notifications are. That remainder is what InboxPilot handles: it recognizes a status inquiry as it lands in Gmail or Outlook, drafts a specific reply from your order information and shipping policies, and holds it for one-click approval. Your team stops being a tracking-number lookup service without anyone losing control of what gets said.

What makes this workflow painful

Pure repetition, real volume

Status questions are nearly identical, arrive constantly, and spike exactly when your team is busiest: launches, sales, and carrier delays.

Slow answers create tickets

A status question ignored for a day becomes a refund demand, a chargeback threat, or a public review. Speed is the whole game.

The answer lives in another tab

Replying means finding the order, checking the carrier page, then writing the same three sentences again. Context switching eats the day.

How teams handle it today

None of these are wrong. They just spend skilled people on assembly work, and they all get slower exactly when volume spikes.

Answer each one by hand

An agent looks up the order, copies the tracking link, and writes the reply, reaching for a saved macro on the generic ones. Repeat forty times a day.

Hours of skilled time on lookups, and a macro with no order details just earns a second email asking which one.

Prevent it: tracking page, notifications, portal

Branded tracking, proactive shipping updates and a self-service portal genuinely cut how many people ask in the first place.

It lowers the volume and never reaches zero. Worried customers email anyway, and those are the ones who matter.

Deflect it with a bot on the storefront

A chat agent answers status questions on the site by querying the order system, so fewer people open their email client at all.

It only covers people who came back to your site. Nothing there sees the reply sent straight to your support address.

How InboxPilot automates it

Step 1

Connect the inbox where status questions arrive

Your support address in Gmail or Outlook. Works alongside a helpdesk if you run one for other channels.

Step 2

Give it your shipping knowledge

Connect your policies, carrier practices, and store or order information so drafts contain specifics, not boilerplate.

Step 3

Status inquiries get spotted and drafted

Incoming where-is-my-order emails are labeled and answered with the order's actual state, expected timing, and next steps for delays.

Step 4

Approve, or let routine ones send

Drafts wait for review by default. Once you trust the pattern, you can allow auto-send for the routine cases and keep approval for the angry ones.

A real example, before and after

The incoming email on the left, the InboxPilot draft waiting for approval on the right.

Customer, six days after orderingIncoming email

Where is order #4821??

I ordered last Tuesday and the tracking page has said 'label created' for four days. Is my order lost? I need this before the weekend.

AI draft by InboxPilotWaiting for your approval

Hi, sorry for the worry. Your order #4821 shipped and is with the carrier; 'label created' hanging for a few days usually means the first scan was missed, not that the package is lost. It is due to arrive Thursday, ahead of your weekend.

Here is the direct tracking link. If it does not show movement by tomorrow morning, reply here and we will open a trace with the carrier and make it right either way.

The draft pulls the order state and the missed-scan explanation from your shipping knowledge, and commits only to what your policy allows.

The WISMO emails that quietly get missed

Plenty of where-is-my-order questions never arrive as a fresh email. They are typed onto the bottom of an automated one, which is where most automation stops looking. InboxPilot reads the newest human message in a thread rather than the message that started it.

Customers reply to the notification

The order confirmation and the shipping update are already in their inbox, so hitting reply is the obvious move. Their question arrives inside a thread that opens with a machine-written message.

Filters judge the thread, not the question

Anything that classifies on the originating message files the whole thread as a system notification and skips it. Nobody sees an error; the customer just gets silence and follows up less politely.

Short questions look like noise

A five-word question, often in the customer's own language, appended under a long English shipping notice is the easiest kind of real message to mistake for automated noise.

Turn a sentence into automated actions

Describe what should happen in plain English and InboxPilot builds the workflow: a trigger, an AI decision, and the actions that run on their own.

Describe your workflowPlain English

“When someone asks where their order is, look up the order, draft a reply with status and tracking, and label it WISMO.”

Build workflow

InboxPilot builds

TriggerIncoming email recognized as an order status question

AI DecisionAI matches the message to the order and checks its state

Actions

Draft a reply with current status, timing, and the tracking link
Apply the WISMO label for reporting
Escalate to a person when the order is genuinely stuck or the customer is angry

Related guides and pages

Automate WISMO emails on Shopify

AI support for e-commerce and retail

Shopify customer support automation

Returns and refund email automation

WISMO & order status: frequently asked questions

WISMO stands for where is my order. It is shorthand for any inbound customer message about the status of a purchase: has it shipped, why has tracking not updated, when will it arrive, was it lost. In most commerce and logistics inboxes it is the single largest category of mail by volume and the least valuable per message.

Prevention first, and it works: a branded tracking page, proactive shipping and exception notifications, a specific delivery date at checkout rather than a five-to-ten-day range, and a self-service order lookup will each cut the volume. None of them take it to zero, because a customer who is already anxious will email you rather than go looking. InboxPilot is for that remainder, so reducing and automating are not competing choices.

Stop answering WISMO emails one at a time