WISMO automation that answers from live tracking
Where-is-my-order (WISMO) questions are usually the biggest single category in an online store's inbox, and most need nothing more than the latest tracking event. We build a workflow that matches each ticket to its order, reads carrier tracking, sends an accurate reply when the parcel is moving normally, warns customers before a delay becomes a complaint, and hands lost, stuck or failed deliveries to an agent with the facts gathered. A typical build costs $1,000 to $2,500 and goes live in about three to four weeks.
The problem
Why WISMO tickets swamp ecommerce support
Every WISMO ticket costs the same steps: find the order, open the carrier site, read the scans, write a reply. On a normal day that is tedious; during a peak sale or a carrier backlog it buries the agents who should be handling damaged goods and refunds.
Silence makes it worse. When a parcel stops scanning, the customer usually notices before the store does. And in the US the FTC Mail, Internet, or Telephone Order Merchandise Rule expects sellers who cannot ship on time to offer the buyer a choice to accept the delay or cancel for a full refund, no later than the original shipping deadline.
What we build
What our WISMO automation includes
Ticket-to-order matching
Incoming emails, chats and contact forms matched to the order by email address or order number.
Live tracking replies
A reply with the latest scan, the carrier link and the expected delivery date when the parcel is moving normally.
Proactive delay notices
Orders that miss their ship-by date or stop scanning trigger a notice before the customer writes in.
Stuck parcel routing
No scan for an unusual period, failed delivery or returned-to-sender cases go to an agent with the tracking history attached.
Branded tracking page link
Replies point to your own tracking page so customers stay on your site.
WISMO dashboard
Daily counts of WISMO tickets, auto-answered share, delayed orders and carriers causing the most exceptions.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Ticket arrives
A where-is-my-order email or chat lands in the help desk.
-
02
Automated
Order and tracking read
The workflow finds the order and pulls the latest carrier events.
-
03
Automated
Reply or route
Normal transit gets an automatic reply; anything abnormal goes to the agent queue.
-
04
Team review
Agent resolves
Agents handle delays, lost parcels, reships and refunds with the facts already on the ticket.
-
05
Founder or ops lead decides
Compensation decisions
Refunds, reships beyond policy and carrier claims are decided by the ops lead.
How it behaves
How Shopify order tracking replies behave
What the customer sees
- A fast reply with the latest scan and expected delivery date
- A delay notice before they need to chase
- A person, not a template, when something has gone wrong
What agents see
- Fewer routine tickets in the queue
- Exception tickets with order and tracking history attached
- A daily dashboard of delays by carrier
What the automation does
- Matches tickets to orders and reads tracking
- Applies transit rules per carrier
- Sends approved replies and logs every action on the ticket
Edge cases and fallbacks
- No order number and an unknown email
- The workflow asks once for the order number, then routes to an agent.
- Split shipment with two tracking numbers
- Both parcels are reported in one reply.
- Tracking shows delivered but customer says not received
- Always routed to an agent; never answered automatically.
- Carrier or tracking API outage
- Tickets fall back to the normal agent queue and the ops lead gets an alert.
- Customer is clearly upset
- Detected tone sends the ticket to a person whatever the tracking says.
Architecture
WISMO automation for an online store at a glance.
- Input
- Logic and services
- Data
- AI step
- Output
- People
How it flows
- 1 A customer asks where their order is by email, chat or contact form.
- 2 n8n matches the ticket to the order in your store and reads the carrier tracking events.
- 3 Rules you approve decide whether the parcel is in normal transit or needs attention.
- 4 Normal transit gets an accurate automatic reply; exceptions go to an agent with the history attached.
Project planner
How the project runs, phase by phase.
WISMO automation & order tracking replies project plan
Typical time to launch: about 3 weeks, then support
-
01
Discovery
2 to 3 days
Help desk, carriers, tracking source, ship-by promises and the replies agents send today.
-
02
Design
2 to 3 days
Transit rules per carrier, reply templates, delay notice wording and routing.
-
03
Build
About 1 week
Help desk integration, order lookup, tracking reads, replies and the dashboard.
-
04
Shadow run
About 1 week
Replies are drafted as internal notes while agents compare with what they would have sent.
-
05
Launch
1 to 2 days
Turn on automatic sending for normal transit only, then widen.
-
06
Support
Ongoing
New carriers, peak-season rules and monitoring.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Carriers, transit rules, templates and routing.
$200 – $400
-
Build
Order lookup, tracking logic, intent detection and replies.
$500 – $1,300
-
Integrations
Help desk, store, tracking and shipping platforms.
$150 – $400
-
Testing and shadow run
Draft-only run against real tickets.
$100 – $250
-
Launch and training
Staged switch-on and agent walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Help desk, tracking platform and n8n plans are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Help desk: Your Gorgias, Zendesk or other help desk plan.
- Tracking platform: AfterShip or your shipping platform's own plan, if used.
- n8n and AI usage: n8n Cloud from about €20 a month (Starter, billed annually) or self-hosted; AI intent detection billed per use by the provider.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: FTC Mail Order Rule
With no shipping time stated you must expect to ship within 30 days; if you cannot ship on time you must offer the buyer the choice to accept the delay or cancel for a full refund before the deadline.
Source: www.ftc.govUS: refund timing after cancellation
Under the same rule, cancelled orders paid by card through a third-party creditor must be refunded within seven working days, and store credit cannot replace the refund.
Source: www.ftc.govEU and UK: personal data in tickets
Order and address data in tickets is personal data under GDPR and UK GDPR, so the workflow reads only the fields it needs and processors are under contract.
Source: gdpr-info.euFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
WISMO automation & order tracking replies questions, answered.
WISMO stands for "where is my order?", the most common customer service question in ecommerce. WISMO automation answers those questions from real order and tracking data so agents can focus on real problems.
Yes. We read orders and fulfillments with tracking numbers from the Shopify Admin API, then pull carrier events from AfterShip, ShipStation or the carrier directly where an API is available.
Only the ones that match rules you approve, typically parcels in normal transit. Delays, failed deliveries, lost parcels and angry customers always go to a person.
Yes. Orders that pass their ship-by date unfulfilled or stop scanning trigger a notice. In the US, where the FTC Mail Order Rule applies, we include the option to cancel in the wording your team approves.
Gorgias and Zendesk most often, both with documented APIs, plus others such as Freshdesk or Help Scout where the API allows, confirmed per project.
Share of WISMO tickets answered without an agent, first response time, tickets reopened after an automatic reply, and how many delay notices went out before a customer complained.
Free 20-minute call
Want this for your e-commerce brand?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for e-commerce brands
All servicesEcommerce CRM & customer lifecycle automation
Bring orders, browsing and support history into one ecommerce CRM, then run welcome, post-purchase, replenishment and win-back flows that stop the moment a shopper buys or opts out.
From $1,000 · About 4 weeks Details
Returns management & refund automation
Check every return request against the right policy for the customer's market, issue labels for eligible items, route faulty goods to an agent and prepare refunds when the warehouse confirms receipt.
From $1,000 · About 4 weeks Details
AI customer service agent for your store
An AI support and shopping assistant on your site, chat and email that answers from your policies and live order data, drafts replies for agents and hands refunds, complaints and anything unclear to a person.
From $2,500 · About 5 to 8 weeks Details