Outsourcing eCommerce Customer Support: What to Hand Over, and the Rules It Is Measured By

Customer support is usually the first job a growing marketplace business hands to an outside team, and the right one to start with, because most of it is routine and all of it is measured. The measuring is the part to get right. Each marketplace sets a response time and scores the account on it, so an outsourced team is not judged on whether it is pleasant but on whether it meets those clocks, every day of the week.

So the contract starts from the marketplaces' rules rather than from the team's office hours. Hand over the routine questions with a written set of answers, keep the decisions that cost money or touch account health, give every person their own access, and read the same metrics the marketplace reads.

Amazon measures contact response time: the share of buyer messages answered within 24 hours, counting messages before and after an order. The clock runs through weekends and holidays, an automatic acknowledgement does not count as a reply, and messages marked as needing no response are left out. A team that works Monday to Friday misses the clock every weekend by design.

Walmart's window is 48 hours, for messages from customers and from Walmart's own customer care team, and it holds sellers to a response rate above 95%. Weekends and holidays count there too, and an automatic reply is not a response. Walmart's policy lists what can follow from missing it, up to cancelled orders and a suspended account, and the same measure sits inside its seller tiers, as set out in Walmart's Pro Seller tiers.

TikTok Shop asks for a reply within 24 hours of the buyer starting a chat, with a response rate of 90% or more, reviewed every week over the previous seven days. Small talk and automated replies do not count. Return requests have their own deadline of four business days, and both feed the shop score that decides what the shop may use, covered in the TikTok Shop account health rating.

The practical rule follows from all three: the team's service level is set by the strictest channel it serves, and it covers seven days, not five.

Because every clock above runs through the weekend, coverage is the first design question, not an afterthought. Twenty-four hours is the tightest window, so a message arriving on Friday evening has to be answered by Saturday evening, and a team that starts again on Monday has already missed it. The usual answer is a light weekend shift that clears the inbox once or twice a day, with the fuller team in the week.

Time zones help rather than hurt. A team several hours ahead of the brand's customers can clear the overnight inbox before those customers wake, which is one of the best uses of an outside team for a US or European store. What matters is that somebody owns each window, on a written roster, holidays included, because holidays are when brands most often discover that nobody was covering.

Volume is not even across the year either. The weeks around Black Friday and the January returns season can bring several times the usual messages, so the contract should say how the team scales for them, and from which date, rather than leaving it to be negotiated in the week it is needed.

Hand over the questions with known answers. Where is my order, what is the tracking, how do I return this, does it fit, what is it made of, when will it be back in stock. Together they are most of the volume in most catalogues, and an outside team answers them well once the answers are written down.

Keep the decisions that cost money or carry risk, or give the team a written limit for them. Refunds and replacements above a set value, anything that mentions a safety issue, a complaint threatening a claim or a review, a message about intellectual property or authenticity, and anything from the marketplace itself about the account. Those go back to a named person inside the business the same day, with the team's notes attached.

The line between the two should be written, not felt. A team guessing where its authority ends either escalates everything, which defeats the purpose, or decides things it should not, which is worse. Which jobs to hand over first across a whole business, not only support, is the subject of what to outsource first and what to keep.

An outside team is only as good as the answers it is given. Before the first shift, write the ten or twenty questions that make up most of the inbox and the answer to each, in the brand's own words, with the facts a reply needs: the returns window per channel, the delivery promise, sizing, care, the warranty. Add the tone, and two or three examples of a reply done well.

Write the marketplace rules into it as well, because they differ from a brand's own store. Amazon's messaging rules, for example, restrict what a reply to a buyer may contain, links to other sites and marketing among them, and a team used to answering for a direct store will break them without knowing. One page per channel on what may not be said saves a policy warning.

Include how to escalate: a named person, the channel to reach them, and what to tell the buyer while waiting, so an escalation never leaves a buyer without a reply inside the marketplace's clock.

Then keep it current. Every new question the team cannot answer is a gap in the document, and the fix is to add the answer, not to keep escalating the same question.

Each person on the team gets a login of their own, with only the permissions the work needs: messages, orders and returns, not pricing, payments or account settings. Shared logins break the platforms' rules and leave no record of who did what. How to set this up on Amazon specifically, the way Amazon says to, is in giving an outsourced team access to Seller Central.

On Amazon there is also the question of whether a team should answer at all for orders you ship yourself, since Amazon offers to take those messages on. The trade-offs are in Customer Service by Amazon or your own team.

Read what the marketplaces read, weekly: Amazon's response time, Walmart's response rate, TikTok Shop's 24-hour rate, and the return-request deadline. Then the outcomes behind them: negative feedback and its reasons, claims opened against orders, and the share of messages that needed escalating. A team meeting every clock while claims rise is answering quickly and badly.

Sample the replies themselves, a handful a week, against the knowledge base and the tone. It is the only way to catch a reply that is fast, polite and wrong.

Once a month, review with the team: the new questions that appeared, the replies that went wrong, and what changed in the knowledge base as a result. A team that improves the document every month is the one worth keeping, whatever its response times.

Running marketplace support to those clocks, seven days a week, alongside the rest of the back office, is what our BPO services do.