You list your first product on Amazon UK on a Tuesday afternoon. The orders come in that week. Then a message arrives: a customer asking whether their order will arrive before the weekend. You answer it from your phone in about forty seconds.
This is the before.
TL;DR
- Most growing ecommerce sellers build their support operation by accident: one inbox per channel, one person per inbox, no shared view of anything.
- The breaking point usually comes at peak season, when a customer has been waiting eleven days and nobody noticed.
- The fix is simpler than the problem: one inbox for every channel, full order history visible before every response.
- This is the story of how it happens, and what the other side looks like.
Six months in, you have twelve products. Messages are more frequent, which you expected. What you didn’t expect is what happens when you add eBay, because someone told you there’s more margin there. Now you have two inboxes. Amazon messages come to Amazon Seller Central. eBay messages come to eBay Seller Hub. Same customer, same question, different system.
You manage it. You’re organised. Two tabs open, you check both.
Then you build a Shopify store because your accountant is right that the marketplace fees are eating 15% of every sale. Three inboxes now. Three different platforms with three different rules about what you can and can’t say in a reply. (Amazon has quite specific rules about this. You learn them the hard way.)
You’re still managing it. Barely.
The moment you know you can’t manage it alone is the moment you hire someone. Call her Maya. She’s quick, thorough, and good with customers. The problem: she has three tabs open too, and no way to see whether you’ve already replied to a message before she does. She answers one. You answer the same one two hours later. The customer is confused.
You explain the system. Maya gets it. She builds her own workaround. Which works fine, until you hire someone else.
You hire Tom six months later because the volume is real now. Tom handles eBay because that’s where the queue is longest. Maya handles Amazon because she knows the rules. You handle Shopify because you know the products. Three people, three inboxes, three separate mental maps of what’s happening.
Here is the problem nobody tells you about. Customers don’t divide themselves by channel the way your team does. A buyer who purchased on Amazon last month just emailed your Shopify support address about a different product. Tom doesn’t know she exists. Maya doesn’t know she exists. You don’t know, because nobody is looking at the Shopify inbox right now.
She’s been waiting four days.
You hire two more people because it’s September and November is coming. Five people, three inboxes across four channels (you added Walmart somewhere in there), running on goodwill and good intentions.
Then the message arrives.
It’s from a buyer who ordered twelve days ago. Asking where his order is. He says it’s the third time he’s written. He’s not angry yet, which in some ways is worse, because you can hear that he’s stopped being angry and started drafting a return instead.
You go and look. The first message is in the eBay inbox, arrived during a week when the person covering eBay was at a trade event for two days. They came back to 200 messages. This one, about a product you don’t stock in larger sizes, got sorted to the bottom. The second message is in the same inbox. The third is a direct email to your general enquiries address that nobody checks, because you all assumed it forwarded somewhere.
Twelve days. Three messages. Nobody replied because nobody could see that nobody had replied.
You spend that Sunday thinking about what you actually built.
You built a support team. Five people who work hard and care about doing it properly. But you also built a system that makes doing it properly nearly impossible. No single place to see all open tickets. No alert when something is approaching Amazon’s 24-hour response window. (Amazon requires you to reply within 24 hours, every day. Miss it and it affects your account standing. This is not a soft rule.) No way to see, before you open a message, what the customer ordered, what they’ve ordered before, or whether they’ve already been in touch on a different channel.
You built five people and five inboxes. That’s not a support operation. It’s five people trying to be one.
Good news: this is a solvable problem. And the solution is simpler than what you’ve been managing.
You look for a helpdesk. The first ones that come up are built for software companies. One is built for large retail chains. Then you find eDesk, built specifically for ecommerce sellers. Amazon, eBay, Shopify, Walmart, and the channels you’re quietly planning to add next: all in one inbox, with every customer’s full order history visible before anyone types a word in reply.
The AI layer (Ava) handles the “where’s my order?” messages automatically, at any hour, on any channel. Which is quite something when those messages make up more than half your queue. Your team handles everything else. From one interface. With full context on every customer before they respond.
The twelve-day reply doesn’t happen again. Not because the team got better (they were already good), but because everything is visible. Tickets get flagged before they breach a window. The channel falling behind shows on a shared view. A customer who contacted you on Amazon and then on Shopify appears as the same person with the same history, not two strangers with similar names.
Book a Free Demo. Not a pitch. A look at your actual setup: the channels you’re managing, the team size, the gaps. It takes thirty minutes.
Your business doesn’t need to get smaller to fix this. You just need one place to see all of it.
For the full picture on what good multichannel support looks like, the ecommerce customer service guide covers channels, metrics, and tools. For where AI fits into this setup, the AI capabilities and limitations guide is direct about what it does and doesn’t do well.
