"Where is my order?" is probably the most common question in online retail. The answer is rarely a mystery. It's sitting in an order system, one lookup away. Yet in plenty of support queues a person still types it out by hand, in the same inbox as the refund dispute that needs real judgment.
That mismatch is the heart of e-commerce customer messaging. Volume isn't the problem. The problem is that easy and difficult conversations arrive in the same place, get handled by the same people, and run through tools that weren't designed for both.
This case study looks at where retail support conversations break down as a business scales, what a well-built chat architecture does about it, and how MINISO, the global lifestyle retailer, uses Nexconn's messaging products.
The market, and why support has to keep up
Online retail keeps taking share. eMarketer forecasts global retail e-commerce sales of about $6.9 trillion in 2026, roughly one in every five retail dollars. In Southeast Asia, the e-Conomy SEA 2025 report from Google, Temasek and Bain projected $185 billion in e-commerce GMV for 2025 and found that three in five people in the region now shop online.
Support has to follow that geography. A retailer selling into a dozen markets has shoppers asking questions in a dozen time zones, and their expectations come from the best service they've had anywhere. Zendesk's CX Trends 2026 research, which surveyed 6,182 consumers and 5,115 CX professionals across 22 countries, found that 88% of consumers expect faster responses than they did a year ago. In the same research, 85% of CX leaders said a single unresolved issue is enough to lose a customer.
Messaging suits that pressure. A shopper can ask a question in thirty seconds and come back to the answer later, and the retailer ends up with a persistent thread tied to an account instead of a scatter of calls and emails.
"Where is my order?", again and again
WISMO is the industry shorthand, and the sources that measure it agree it's the most common post-purchase contact. Industry benchmarks from providers like Gorgias and Zendesk show that order-status inquiries typically account for 20% to 35% of all post-purchase volume, while peak-season vendor blogs often claim numbers as high as 40% to 60%. Each contact is quick to answer, and nothing about it needs a human. The cost comes from thousands of them arriving in the same queue as conversations that do need judgment.
Context that disappears at every handoff
Zendesk found that 81% of consumers want an agent to pick up where the last conversation left off, and 74% get frustrated when they have to repeat themselves. Retail support makes that hard by design. A question starts with a bot, moves to an agent, turns into a delivery problem, and picks up a supervisor along the way. If every transfer means closing one ticket and opening another, the history gets left behind.
Devices multiply, messages don't follow
Agents work from a desktop, a tablet and a phone, and sometimes share an account across shifts. Customers change phones and reinstall apps. When messages and conversation lists live in a local database on the device, a fresh install starts out empty. It's the least glamorous problem on this list, and it's easy to miss until real users start switching devices.
Transactional messages need real control
Once a chat carries coupons, payment prompts or refund confirmations, free-form text stops being enough. The backend has to be able to check that a message is legitimate, block one that isn't, and adjust content before it reaches the customer. Moderation adds a cost of its own if every message goes through it, so it makes sense to review only the traffic that carries risk.
Supervisors need visibility without getting in the way
Quality assurance, escalation management, and compliance audits require supervisor observability: silently joining live sessions, tagging, pinning, and exporting transcripts on demand. Many brands also run fan groups and flash-sale communities alongside support, and those put thousands of people in one room, which is a different load on the same messaging layer.
What a well-built retail chat system does
The systems that hold up tend to converge on a handful of decisions, and most of them get made before anyone designs a screen.
The first is how to model a conversation. A ticket, with one owner and one status, suits email. Chat works better as a session with members: the customer, an agent, maybe a bot, and a supervisor who can join and leave. A transfer then becomes a change in membership rather than a new record, and the history belongs to the session instead of whoever touched it last.
Automation comes next, placed where the volume is. Bots are good at lookups such as order status, delivery windows and return policies, and people are good at exceptions. What separates a decent setup from a frustrating one is the exit: clear rules for when the bot steps aside, and a handoff that carries the whole conversation along. Zendesk found that 83% of CX leaders in Asia-Pacific see AI as critical to faster resolution, but speed only counts if escalation works.
Then there's proactive messaging. Much of the "where is my order" volume stems from the post-checkout communication gap between payment confirmation and final delivery, so updates at the right milestones go after the volume at its source. ShippyPro, a shipping software provider, reports that proactive notifications cut these contacts by up to 65%. While carrier performance varies, the mechanism is sound.
Anything transactional should stay under server control. Message callbacks let the backend inspect each message of a given type before delivery and approve, block, rewrite or route it. They also give you a cheap way to manage moderation spend: check the message types that carry risk and skip the rest.
State across devices deserves a decision before launch, not after. That means choosing what syncs, how far back an offline device catches up, and what happens to a conversation list across client environments.
Finally, supervisors need a view that doesn't disturb the customer: joining a live session, filtering by status, and exporting transcripts for review.
How Nexconn approaches it
Nexconn's messaging platform has a building block for each of those decisions. Here's how they fit together.
Sessions, handoff and the agent workbench
Nexconn models a customer conversation as a group session. The customer is paired with an agent through it, agents in different roles can be active at the same time, and a merchant or supervisor can join or leave at any point to watch service quality in real time (via silent monitoring). When a conversation moves between agent groups (from sales to after-sales, say), the incoming agent can read the full history. Agents can also send targeted messages inside a session that only chosen participants see.
The workbench covers the rest of a support team's day. One agent account can be shared by several staff members across shifts, with notifications when an account is active elsewhere. Conversations can be tagged, pinned to the cloud, and organized into custom operational queues. Important notices (such as payments or delivery updates) are clearly flagged, while AI bots triage routine lookups and escalate to human agents when edge cases arise.
The shopper's side of the chat
In the app, customers get the message types a shopping chat needs: text, images, voice, short video, location, and emoji, plus inline system notices. Custom message types cover retail-specific cases such as satisfaction ratings or coupon cards. Read receipts show whether a message has been seen, and the client can search conversations by keyword. Status prompts (welcome greetings, queue progress, and transaction alerts) keep shoppers informed while they wait.
Control over transactional messages
For anything involving sensitive data or financial transactions, synchronous message callbacks put your backend in the loop. Your server receives messages of chosen types before delivery and returns instructions: let it through, block it with a custom reason, or alter the content and metadata on the fly.
Callbacks also work alongside content moderation in flexible pipelines. Teams can choose to moderate first and callback afterward, or execute callbacks first and moderate later—allowing businesses to bypass moderation on trusted system alerts and optimize review spend.
Multi-device sync and operational resilience
To eliminate context loss when agents switch between desktop, tablet, and mobile, Nexconn provides cross-device state synchronization paired with server-side offline message compensation. When users or agents sign in on new devices, missed messages and events replay automatically within a configurable catch-up window. Conversation lists restore cleanly across web and mobile clients, while message revocations sync instantly to online sessions and apply upon next sign-in for offline devices.
For community-driven retail, group channels are built for scale. Apps can deploy large customer communities supporting thousands of members per group, complete with role permissions, broadcast announcements, read receipts, and targeted @mentions.
MINISO: messaging at retail scale
MINISO is a lifestyle retailer known for affordable, IP-driven products, listed in New York (NYSE: MNSO) and Hong Kong (HKEX: 9896). Scale is the point here. The company reported record revenue of RMB 21.44 billion (about US$3.07 billion) for 2025, up 26.2%, and ended the June 2026 quarter with 8,674 stores worldwide after entering Switzerland, its 113th country or region.
At that size, even routine questions add up, and they arrive around the clock.
MINISO implemented Nexconn's chat and messaging products for communication between shoppers and customer service, along with a notification solution that keeps shoppers updated on order status while a delivery is on its way.
The two pieces cover both directions of the conversation:
The messaging layer handles exchanges that need a person, in a persistent thread that keeps its history.
The status notifications bridge the post-checkout communication gap between payment and delivery, answering "where is my order" before anyone has to ask.
While MINISO's deployment focuses on high-volume customer support and automated order status notifications, the broader retail capabilities covered above—from agent workbenches and transactional callbacks to community channels—are part of Nexconn's modular architecture for global retail.
If you're building something similar
Whether you build or buy, a few decisions are much cheaper to make early:
Pick the session model before the UI: Retrofitting handoff onto a ticket-shaped data model is painful.
Choose your multi-device behavior on purpose: Test mobile conversation lists early to ensure sync logic fits your use case.
Put transactional message types behind server-side callbacks from day one: Adding verification after coupons or orders are live is a much harder conversation.
Meter your moderation: Run it where risk exists and skip trusted internal system traffic.
Let bots take the lookups: Write down clear human escalation rules before writing bot logic.
Top comments (0)